[issue4212] email.LazyImporter does not use absolute imports

R. David Murray added the comment: LazyImporter isn't used in Python3. Without someone motivated to propose a patch this isn't going to be changed, so I'm closing the issue. -- resolution: -> wont fix stage: -> committed/rejected status: open -> closed _

[issue4212] email.LazyImporter does not use absolute imports

Changes by Barry A. Warsaw : -- assignee: barry -> r.david.murray nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mai

[issue4212] email.LazyImporter does not use absolute imports

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: No patch has been proposed, so the issue is not eligible for 2.5.3. -- nosy: +loewis versions: +Python 2.6 -Python 2.5.3 ___ Python tracker <[EMAIL PROTECTED]> _

[issue4212] email.LazyImporter does not use absolute imports

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- assignee: -> barry nosy: +barry ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Pyt

[issue4212] email.LazyImporter does not use absolute imports

New submission from Brandon Bloom <[EMAIL PROTECTED]>: I have a package with a module called "email". If I try to use the standard email package, it fails to load email.Utils because email.LazyImporter is looking in my email module instead of the top- level email package. -- components