Re: glib-mkenums in glib 2

On 30 Dec 2012, at 16:36, John Ralls wrote:

> Hmm. Your python doesn't seem to agree that codegen is a package, in spite of being imported into gdbus-codegen.

On 30 Dec 2012, at 16:40, jose aliste gmail com wrote:

> I don't know if this is related, but It seems you are missing the empty in the codegen/ directory. This is a requirement for a directory so python may consider it as a package.

Hi guys,

Maybe you'll remember that I eventually bought a Python programming book and ran some examples which also used the 'from / import' construct.  The textbook examples worked but building this gdbus stuff still wouldn't work.  Well, eventually I spotted a difference which I think might be important....

Each sample package from my textbook does have that file  But when I run the actual sample, a second file gets generated, called '__init__.pyc'.  If I delete that file and then run the sample again, it gets regenerated each time.  This isn't happening with the gdbus code.  Although the codegen package does have a file called, I never see a file called __init__.pyc getting generated.

Could that be significant?  I think perhaps that explains why codegen isn't getting recognised as a package.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]