David Goodger schrieb:
> On Tue, Nov 25, 2008 at 15:34, Georg Brandl <g.brandl@...> wrote:
>> in order to get more people porting and testing things on Python 3000,
>> I want to start by getting Sphinx running on it. That requires having
>> I'd like to port the Docutils to Python 3000. Assuming you all are OK
>> with that,
> I am.
>> how should we organize that? Since the Docutils have quite
>> strict compatibility requirements,
> What do you mean?
>> it is very probably not sensible to
>> use the "on codebase from which the 3000 version is converted by 2to3"
> I don't know if that will work or not -- it might!
The website says that Python 2.2 is still supported. Since the "single
codebase" strategy relies on the 2to3 conversion doing everything needed
to make it run on 3k, the more backwards compatible you have to stay,
the more impossible this is. It works best for code that only needs to
run on 2.6, which is of course not possible for Docutils.
There might be a way to do it, using two converters: one to 2.x, one to
>> Therefore, I propose the Python model: a separate branch in
>> the repository into which new changes in the trunk are merged with the
>> svnmerge tool. If that's fine, should the branch be in /branches/, or
>> in /trunk/sandbox/?
> If we need a branch, I think /branches/ would be best.