<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 well with Python 2.6.

Let's hope not. We can mitigate that by spelling out in the docs that there's
no one right way, how to choose which approach is best for a given project, and
so on.

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. 
">

(original) (raw)



On Tue, Feb 28, 2012 at 12:07, Vinay Sajip <vinay_sajip@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 "single source" approach as the one right
> way, and will accept that this only works well with Python 2.6.

Let's hope not. We can mitigate that by spelling out in the docs that there's
no one right way, how to choose which approach is best for a given project, and
so on.

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\.