Handling import conflicts when module has the same name as a library module that it needs to import?
I am struggling with an import problem...
In my package, myapp, there is a module called logging. This module,
naturally, imports the standard library module logging. However, when
I try 'import myapp.logging', the 'import logging' statement appears to
be finding the myapp.logging module instead of the one in the standard
How can I ensure that my logging module doesn't try to import itself?
|All times are GMT. The time now is 01:28 AM.|
Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.