Grc code generation issues with name confliction

GNU Radio
1

If I have two packages ‘packa’ and ‘packb’, each of them has a module
‘modc’.
This is not a problem since they belong to different packages.
But if I use these two modules in GRC at the same time, the following
python codes are generated:

from packa import modc
from packb import modc

Thereafter, name confliction happens. Only packb.modc is accessible.

2

On 09/09/2011 09:36 PM, Kyle Z. wrote:

If I have two packages ‘packa’ and ‘packb’, each of them has a module ‘modc’.
This is not a problem since they belong to different packages.
But if I use these two modules in GRC at the same time, the following python
codes are generated:

from packa import modc
from packb import modc

Thereafter, name confliction happens. Only packb.modc is accessible.

If you wrote the xml files, you need to change them in such a way so
that they dont conflict.

Ex:
from packa import modc as packa_modc
packa_modc.my_block(…)

I bet there are many other ways to do this. Its just python :slight_smile:

-josh

3

On 10/09/2011, at 3:13 PM, Josh B. wrote:

-josh

Great! I did not realize the codes generated are controlled by .xml
file, in particular the tag.
Thanks Josh
Kyle