[Python-Dev] 3to2 0.1 alpha 1 released

[Jesse Noller]

On Thu, Aug 27, 2009 at 7:43 PM, "Martin v. Löwis"<martin at v.loewis.de> wrote:
>>> None at the moment. I think the community needs to show its interest
>>> in it and Joe his willingness to maintain it in the future in order
>>> for it to qualify for addition to the stdlib.
>>
>> Is that how 2to3 got in? If I remember correctly, this was a huge
>> request from the language summit - and by huge, I mean really, really
>> big.
>
> Ok, so then it should be easy to generate some real interest out of
> it, right? E.g. a somebody actually running the tool, or perhaps even
> a bug report?
>
> Regards,
> Martin
>

I'm sure we can get just as much interest in a 3 to 2 tool as we have
for python 3 itself.

Sorry, that was over-catty of me, but it's true. Right now 95% of the
known world is living in 2.x, and I would argue that some of this is
due to an unclear path of maintaining compatibility with 2.x code if
they should jump to python 3. That was part of the driving force
behind getting something like this done, at least at the language
summit and last year's PyCon.

Having an "official" - where "official" could mean linking to it in
the Python 3 docs, announcing something on a python blog, something -
anything to encourage/get more people to use it. I'm not disagreeing
that just plopping it into core may not be the Right Thing To Do, but
making it "semi-official" and "recommended" carries a lot of weight.

I know the mercurial migration is happening Really Soon Now, but even
hosting it in our svn/piggy backing our tracker and putting out a
little python.org post pointing out 2to3 and 3to2 exist as migration
tools could help.

Maybe just a post about the GSOC project, what it does and where to
get it, and "please try it out so we can smash the bugs" on the front
page?

i'd-like-to-be-able-to-use-python3-in-the-near-future-but-none-of-my-dependencies-have-portedly-yours

jesse