Hi itojun, As you may have noticed, I just committed the last chunk of your IPv6 patch. Thanks a lot for your contributions, I think you've provided a highly valuable contribution to Python 2.2. We still have to figure out a way to provide documentation, but I expect that we can complete that before 2.2a2. As with all new code, there may occur some problems; I hope you'll be around for the coming weeks and give the professional advise that you've provided throughout the integration of the code. People finding problems in the IPv6 code (ie. with the current socket applications) are encouraged to use the SF bug-reporting procedure as they do for all other problems in the Python libraries; you can assign all such bugs to me. Kind regards, Martin
Martin v. Loewis writes:
We still have to figure out a way to provide documentation, but I expect that we can complete that before 2.2a2.
I'll warn you now that I know next to nothing about IPv6, and my attempts to spend enough time reading about it to be useful have been thwarted more than one. I'm afraid I'll be able to provide no more than editorial & markup assistance for the IPv6 documentation. ;-( -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Digital Creations
Martin and Itojun, I would like to thank you both for adding IPv6 support to Python. It's a big boon for Python as well as for IPv6! --Guido van Rossum (home page: http://www.python.org/~guido/)
Hi itojun,
As you may have noticed, I just committed the last chunk of your IPv6 patch. Thanks a lot for your contributions, I think you've provided a highly valuable contribution to Python 2.2. We still have to figure out a way to provide documentation, but I expect that we can complete that before 2.2a2.
sorry that i'm delayed about documentation (specificaly socket module). i have no TeX environment now (i had before) and having trouble checking if i'm typesetting right. do you mind if i send you just plaintext?
As with all new code, there may occur some problems; I hope you'll be around for the coming weeks and give the professional advise that you've provided throughout the integration of the code.
as for Lib/*.y changes, there shouldn't be much changes unless you have faulty IPv6 connectivity - the code will try to connect to IPv6 destination then IPv4 against FQDN hostnames, so if IPv6 connectivity is faulty you will see more delays. with Lib/ftp.py people is most likely to see something is happening as it will try protocol-independent FTP commands (EPSV/EPRT) first. anyway... if possible drop me notes. i don't check SF too frequently (i cannot adapt to the SF UI). i'll subscribe to python-dev. itojun
sorry that i'm delayed about documentation (specificaly socket module). i have no TeX environment now (i had before) and having trouble checking if i'm typesetting right. do you mind if i send you just plaintext?
That's fine; I'll then put it into the python-tex format - in the end, Fred will compile it into HTML and publish it on SF (devel-docs), so that we can check whether it came out right.
anyway... if possible drop me notes.
I'll keep you informed, no problem. Regards, Martin
participants (4)
-
Fred L. Drake, Jr. -
Guido van Rossum -
itojun＠iijlab.net -
Martin v. Loewis