Python 3.0 migration plans?

[Alia Khouri]

Couldn't agree with you more. What would be fantastic is if I could
drop into the Pypi (and/or use easy_install) and download
automatically compiled versions of extension modules for different
versions of python.

I'm sure the community at large would be happy to chip in an annual
fee to help build/maintain this infrastructure: I know my firm would.

PS: IMHO The growth of Ruby is, to a large extent, due to easy
installation of modules via its gem system...



On Sep 28, 6:53 pm, John Nagle <na... at animats.com> wrote:

>      Insofar as Python has an organization, it's not adequately managing
> extension modules.  Each extension module has its own infrastructure,
> with its own build procedures, its own bug list, and its own maintainers.
> There's not even an archive.  Unlike CPAN, Cheese Shop is just a directory of
> URLs.
>
>      Take a look at how Perl does it.  Here are the instructions on
> how to contribute to CPAN:
>
>        http://www.cpan.org/modules/04pause.html
>
> There's a way to get your module into the system, a standardized format,
> build, and installation procedure, and an archive which is mirrored.
> There's a common bug reporting system.  Modules abandoned by their
> original developers are not lost, and can be "adopted" by someone else.
>
>      Python doesn't have any of this.  And that's far more of a problem
> than Python 3.x.
>
>                                 John Nagle