I've just released a source tarball and a Windows installer for Python 1.6 alpha 1 to the Python website: http://www.python.org/1.6/ Probably the biggest news (if you hadn't heard the rumors) is Unicode support. More news on the above webpage. Note: this is an alpha release. Some of the code is very rough! Please give it a try with your favorite Python application, but don't trust it for production use yet. I plan to release several more alpha and beta releases over the next two months, culminating in an 1.6 final release around June first. We need your help to make the final 1.6 release as robust as possible -- please test this alpha release!!! --Guido van Rossum (home page: http://www.python.org/~guido/)
Guido, """where you used to write sock.connect(host, port) you must now write sock.connect((host, port))""" Is it possible to keep old notation ? I'm understand (according you past mail about parameters of the connect) this may be not what you has have in mind, but we do use this notation "a lot" and for us it will means to create workaround for socket.connect function. It's inconvinient. In general, I'm thinknig the socket.connect(Host, Port) looks prettier :)) than socket.connect((Host, Port)) Vladimir
Guido van Rossum wrote:
I've just released a source tarball and a Windows installer for Python 1.6 alpha 1 to the Python website:
Probably the biggest news (if you hadn't heard the rumors) is Unicode support. More news on the above webpage.
Note: this is an alpha release. Some of the code is very rough! Please give it a try with your favorite Python application, but don't trust it for production use yet. I plan to release several more alpha and beta releases over the next two months, culminating in an 1.6 final release around June first.
We need your help to make the final 1.6 release as robust as possible -- please test this alpha release!!!
--Guido van Rossum (home page: http://www.python.org/~guido/)
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? 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. -- bjorn
participants (3)
-
Bjorn Pettersen -
Guido van Rossum -
Vladimir Ulogov