RetroSearch Browse

Mon Feb 22 22:09:14 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-February/097881.html

On Sat, Feb 13, 2010 at 2:23 PM, Benjamin Peterson <benjamin at python.org> wrote:
> 2010/2/13 "Martin v. Löwis" <martin at v.loewis.de>:
>> I still think that the best approach for projects to use 2to3 is to run
>> 2to3 at install time from a single-source release. For that, projects
>> will have to adjust to whatever bugs certain 2to3 releases have, rather
>> than requiring users to download a newer version of 2to3 that fixes
>> them. For this use case, a tightly-integrated lib2to3 (with that name
>> and sole purpose) is the best thing.
>
> Alright. That is reasonable.
>
> The other thing is that we will loose some vcs history and some
> history granularity by switching development to the trunk version,
> since just the svnmerged revisions will be converted.

So the consensus is that 2to3 should be pulled out of the main Python
tree? Should the 2to3 hg repository be deleted, then?

Thanks,
Collin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-February/097881.html below:

[Python-Dev] PEP 385 progress report