This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lregebro
Recipients eric.araujo, lregebro
Date 2013-03-11.06:08:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362982083.62.0.107221313887.issue17393@psf.upfronthosting.co.za>
In-reply-to
Content
Not really, but they are related. The fixer looks for a local module, and if it finds it it will assume the import is local. 

#13317 is caused by it not finding the module, since it's not built and hence assuming it's a global import.

This bug, contrariwise, is cause by the fixer finding a folder, and therefore assuming it is a local import when it's not.

The fix for this is to check that the folder has an __init__.py. The fix for #13317 is to build extensions before running 2to3.

Neither of them are huge problems since you can avoid both bugs but not using relative imports. :-)
History
Date User Action Args
2013-03-11 06:08:03lregebrosetrecipients: + lregebro, eric.araujo
2013-03-11 06:08:03lregebrosetmessageid: <1362982083.62.0.107221313887.issue17393@psf.upfronthosting.co.za>
2013-03-11 06:08:03lregebrolinkissue17393 messages
2013-03-11 06:08:03lregebrocreate