On Fri, Feb 13, 2009 at 7:22 PM, Basilisk96 <basilis...@gmail.com> wrote:
> On Feb 12, 10:39 pm, Damon <damonwisc...@gmail.com> wrote: > > * Like R, every time there is a new version of Python, the repository > > should rebuild the packages, for all supported platforms, and make > > available all those that compile cleanly. R also forces you to write > > properly structured documentation for every exposed function, before > > the repository will accept it. > > A very good idea indeed. I would love to start using Py3k today, but I > am still on 2.5 because I depend on win32 binaries for the majority of > my library packages. I can build some myself, but not all. A > repository of prebuilt binaries that stay in step with currently > available language releases would be most welcome. > > Just my $0.02, > -Basilisk96 With Py3K, it's a little bit more complicated than rebuilding all the packages. Because it broke compatibility, all of the C extensions have to be rewritten before they'll work. That's why it's taking longer to create Python 3 packages than to create 2.6 versions. > > -- > http://mail.python.org/mailman/listinfo/python-list >
-- http://mail.python.org/mailman/listinfo/python-list
