Python 1.6 alpha 1 released

[jeremy at cnri.reston.va.us]

> Just read the announcement page, and found that socket.connect() no
> longer takes two arguments as was previously documented. If this
> change is staying I'm assuming the examples in the manual that uses
> a two argument socket.connect() will be changed?
Yes. The source and documentation releases are decoupled. The doc
release will take a bit longer, because Fred just finished a big
revision of the 1.5.2 docs.
> A quick look shows that this breaks all the network scripts I have
> installed (at least the ones that I found, undoubtedly there are many
> more). Because of this I will put any upgrade plans on hold.
I'm surprised at all the vituperative responses you got on this one.
I like the change, but agree that in some environments it makes a lot
of sense to delay upgrades. If you're project is mission critical
and its not broken, why upgrade? In the long run, you'll probably
benefit from all the little changes in 1.6 even if Unicode isn't
important, but do it on your own schedule.
Jeremy


Sent via Deja.com http://www.deja.com/
Before you buy.