The part of "as X" of either "import foo.bar as X" or "from foo import bar as X" does _one thing_ and is fully self-consistent.
The part of "import foo.bar" and "from foo import bar" does different things, that sometimes are interchangeable, and in some cases may have different results - however, these are well stablished, and overall, they don't even "care" or "know" if the imported part is to be renamed with an "as X" complement. For me that is "one obvious way to do it" and there is nothing of "oounerintuitive" on that. Also, trying to change or limit this now, besides blocking behaviors that sometimes are needed, would introduce severe backwards incompatibility for no gain at all. js -><- On Mon, 30 Mar 2020 at 11:54, Joseph Perez <[email protected]> wrote: > There is no other advantage than respect of the Zen of Python (and I don't > know how much it counts). Maybe it can simplify interpreter code, but I > don't know about it and I doubt it. > With that, it could help newcomers to Python to choose between the two > syntaxes. (And I've already experienced team conflict about syntax) > By the way, I think this issue is not fundamental, that's why a removal > would actually maybe be too strong. > _______________________________________________ > Python-ideas mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-ideas.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/FD5PIOEUFEQQWY475TYZPZF5SOKDQW3S/ > Code of Conduct: http://python.org/psf/codeofconduct/ >
_______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/YBO44XWDMY35CQ4ESPFIUZXWE4VNPF6Q/ Code of Conduct: http://python.org/psf/codeofconduct/
