Re: [Discuss-gnuradio] grc code generation issues with name confliction
On 10/09/2011, at 3:13 PM, Josh Blum wrote: 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 :-) -josh Great! I did not realize the codes generated are controlled by .xml file, in particular the make tag. Thanks Josh Kyle ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] grc code generation issues with name confliction
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. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] grc code generation issues with name confliction
On 09/09/2011 09:36 PM, Kyle Zhou 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 :-) -josh ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
