FWIW, I agree that much of the rhetoric in the current version of PEP
414 is excessive.
Armin has given me permission to create an updated version of PEP 414
and toning down the hyperbole (or removing it entirely in cases where
it's irrelevant to the final decision) is one of the things
On Feb 28, 2012, at 08:41 AM, R. David Murray wrote:
Hmm. It seems to me that this argument implies that PEP 414 is just
as likely to *slow down* adoption of Python3 as it is to speed it up,
since if this issue is as big a barrier as indicated, many potential
porters may choose to wait until OS
On Tue, Feb 28, 2012 at 09:53, Barry Warsaw ba...@python.org wrote:
On Feb 28, 2012, at 08:41 AM, R. David Murray wrote:
Hmm. It seems to me that this argument implies that PEP 414 is just
as likely to *slow down* adoption of Python3 as it is to speed it up,
since if this issue is as big a
On Feb 28, 2012, at 10:23 AM, Brett Cannon wrote:
Well, when the code is committed I will update the porting HOWTO and push
the __future__ imports first since they cover more versions of Python (i.e.
Python 3.2). But I will mention the options that skip the __future__
imports for those that
If PEP 414 helps some projects migrate to Python 3, great.
But I really hope we as a community don't perpetuate the myth that you cannot
port to Python 3 without this, and I hope that we spend as much effort on
educating other Python developers on how to port to Python 3 *right now*
supporting
martin at v.loewis.de writes:
One thing that the PEP will certainly achieve is to spread the myth that
you cannot port to Python 3 if you also want to support Python 2.5. That's
because people will accept the single source approach as the one right
way, and will accept that this only works
On Tue, Feb 28, 2012 at 12:07, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
martin at v.loewis.de writes:
One thing that the PEP will certainly achieve is to spread the myth that
you cannot port to Python 3 if you also want to support Python 2.5.
That's
because people will accept the
Brett Cannon brett at python.org writes:
Changes to http://docs.python.org/howto/pyporting.html are welcome. I tried to
make sure it exposed all possibilities with tips on how to support as far back
as Python 2.5.
Right, will take a look. FYI a Google search for python 3 porting guide shows
On Tue, Feb 28, 2012 at 11:51, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
Brett Cannon brett at python.org writes:
Changes to http://docs.python.org/howto/pyporting.html are welcome. I tried
to
make sure it exposed all possibilities with tips on how to support as far
back
as Python 2.5.
mar...@v.loewis.de writes:
One thing that the PEP will certainly achieve is to spread the myth that
you cannot port to Python 3 if you also want to support Python 2.5. That's
because people will accept the single source approach as the one right way,
and will accept that this only works
On Wed, Feb 29, 2012 at 5:23 PM, Stephen J. Turnbull step...@xemacs.org wrote:
mar...@v.loewis.de writes:
One thing that the PEP will certainly achieve is to spread the myth that
you cannot port to Python 3 if you also want to support Python 2.5. That's
because people will accept the
11 matches
Mail list logo
