Regardless, I still feel the introduction of a switch and all that stuff is too complicated. I understand you position, since all my applications are written in Python 2(except 1). However, I don't think this is the best solution.
On Fri, Jan 17, 2014 at 2:19 PM, Neil Schemenauer <n...@arctrix.com> wrote: > On 2014-01-17, Ryan Gonzalez wrote: > > A command line parameter?? > > I believe it has to be global flag. A __future__ statement will not > work. Probably we should allow the flag to be set with an > environment variable as well. > > > The annoying part would be telling every single user to call Python with > a > > certain argument and hope they read the README. > > > > If it's a library, out of the question. > > > > If it's a program, well, I hope your users read READMEs. > > The purpose of the command line parameter is not for end users. It > is intended to help developers port millions of lines of existing > Python 2.x code. I'm very sad if Python core developers don't > realize the enormity of the task and don't continue to make efforts > to make it easier. > > Regards, > > Neil > -- Ryan When your hammer is C++, everything begins to look like a thumb.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
