Martijn Faassen wrote:
> David Pratt wrote:
>> Ultimately, the
>> folks that will even want to maintain a 2.x code base will quickly
>> erode since the forefront of development is never the past. Perhaps
>> it will all move more quickly for this reason when python 3K is out
>> for real.
> This is what I fear will happen. This could mean either some huge
> codebases in Python 2.x are going to be left behind in some kind of
> ghetto, or that the single community will fracture into a Python 2.x
> and a Python 3.x community. Both scenarios suck, so I certainly hope
> I'm being pessimistic about this.
My first thought was, reading the subject of this thread, what the
twisted-folks say to all that (the topic of #twisted is "NO Twisted does
not run on Python 3" ). Might these projects coordinate their
transitions with each other? Would it make sense to move to p3K if not?
What about other dependencies? I remember a recent thread discussing
lxml recently. There'll be certainly no tool helping in the transition
of C/C++ extensions, not to mention those using Pyrex, Boost.Python, etc.
I fear the two options are either major cross-project organizing efforts
or a major disaster.
Zope3-dev mailing list