[Distutils] [Distribute] Python 3 porting effort - plans proposal for 0.7/0.8

[Tarek Ziadé]

On Thu, Jul 23, 2009 at 5:06 PM, Lennart Regebro<regebro at gmail.com> wrote:
> We are to create one
> compatible version for both Python 2 and Python 3.
[..]
> This has no significant benefits, creates more work and more
> confusion. There is simply no reason to do this.

Sorry, we are not making any progress in this thread :)

you don't seem to understand what backporting changes from a pure 3.x branch
to a 2.x compatible branch means. That's just a backport maintenance
work once the Py3K branch
has started + forwardport of part of the work done in 0.6. So there's
no "duplicate work".

As a developer, I am ok to have a mixed-code branch for a 0.7 version
that will not last,
but I don't want to work in a 2.x/3.x code soup for the future 0.8 branch.

I gave you the list of benefits and I don't see any benefits in what
you are describing.

I'd be curious to see how "clean" your 2.x/3.x code could be. How do
you intend for instance
to have a module with named exceptions that works in both versions,
without duplicating
the code. This work can be done afterwards, once we have a working
system under 3k.

Cheers
Tarek