Paul Moore wrote:
> As I said at the start, I don't have any good answers. But would it be
> worth maintaining something like a wiki page of key libraries and
> their expectations for moving to 3.0? It might at least make people
> aware of reasonable timescales, and set some expectations for chronic
> early adopters like me :-)
My personal expectation is that 3.0 will serve mainly to provide the
developers of those 3rd-party frameworks and libraries with a solid
target to aim for, and that the more likely adoption point for end-user
production usage would be around the 3.1 timeframe. I might be
pleasantly surprised by the actual rate of adoption, but I wouldn't put
any money on that prospect ;)
Even with 2.x releases it usually takes a few months after the
python.org release for all the 3rd parties to get their binary
installers up to date and released (some of the bigger projects that
have the resources to closely track the alpha/beta releases may get
something out quickly, but I'm other projects will wait for at least the
release candidates before looking at what needs to be done)
Cheers,
Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia
---------------------------------------------------------------
http://www.boredomandlaziness.org
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
