[Python-Dev] Bug in 2to3 concerning import statements? (original) (raw)
Guido van Rossum guido at python.org
Sun May 1 20:41:19 EDT 2016
- Previous message (by thread): [Python-Dev] Bug in 2to3 concerning import statements?
- Next message (by thread): [Python-Dev] Looking for a Python programming mentor
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I agree it's a bug. May I encourage you to file it as such on bugs.python.org? 2to3 is part of the stdlib.
On Sun, May 1, 2016 at 4:42 PM, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
Brett Cannon wrote:
There's all sorts of weird stuff going on in that import, like having a dot in the
from
part of the import instead of doingfrom .py2exe import_ _mf as modulefinder
.If I did that, it would try to import mf from the py2exe submodule rather than the global one. In hindsight it was probably a bad idea to name the submodule py2exe, but the code worked as intended. My point is that, regardless of anything else, 2to3 shouldn't be generating syntactically incorrect code. I can understand if it's not considered worth fixing, but it's still a bug. -- Greg
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160501/d73e88fa/attachment-0001.html>
- Previous message (by thread): [Python-Dev] Bug in 2to3 concerning import statements?
- Next message (by thread): [Python-Dev] Looking for a Python programming mentor
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]