Thomas Bartelmess added the comment:
The datagram handler seems still not useable with IPv6 in Python 3.4. Is this
patch still under consideration ?
--
nosy: +Thomas Bartelmess
___
Python tracker rep...@bugs.python.org
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
Or should it go to the separate ticket?
Yes, please.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14855
___
Yuriy Syrovetskiy c...@cblp.su added the comment:
Can the datagramHandler.host change during execution? If so, the address family
of the socket can change. So, we should create a socket for every new message.
Check my patch #2.
Also I extended socket.create_connection to support UDP.
Yuriy Syrovetskiy c...@cblp.su added the comment:
test_logging is not broken, but just fails.
test test_logging failed -- Traceback (most recent call last):
File /home/cblp/my/cpython_default/Lib/test/test_logging.py, line 2903, in
test_time
self.assertEqual(f.formatTime(r), '1993-04-21
New submission from Yuriy Syrovetskiy c...@cblp.su:
IPv4 operations may fail on IPv6 systems, and vice versa. So we have to create
sockets with the proper address family.
Maybe this behaviour could be incapsulated in socket object, but didn't find a
good way to do it.
No documentation
Yuriy Syrovetskiy c...@cblp.su added the comment:
More correct description: IPv4 operations may fail on IPv6 systems, and vice
versa; so we have to detect the proper address family before creating a socket.
--
___
Python tracker
Antoine Pitrou pit...@free.fr added the comment:
For TCP, socket.create_connection() is your friend. For UDP I'm not sure, but
adding a helper to the socket module might also be a good idea.
--
nosy: +gregory.p.smith, pitrou
versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.2,
Antoine Pitrou pit...@free.fr added the comment:
The Linux getaddrinfo() man page has an UDP client example which uses connect()
to decide whether the target address is valid or not.
--
___
Python tracker rep...@bugs.python.org
Martin v. Löwis mar...@v.loewis.de added the comment:
Apparently, connecting the socket is better because some systems (BSDs in
particular) only report ICMP errors to connected UDP sockets. The Linux man
page claims that this reporting is necessary regardless of whether the socket
is
Yuriy Syrovetskiy c...@cblp.su added the comment:
On my computer, connect() on a UDP socket always finishes successfully. What's
wrong?
I tried that C example from man getaddrinfo(3).
--
___
Python tracker rep...@bugs.python.org
Antoine Pitrou pit...@free.fr added the comment:
On my computer, connect() on a UDP socket always finishes
successfully. What's wrong?
Nothing wrong I guess, since connect() on an UDP socket doesn't actually
do anything, network-wise (UDP being an unconnected protocol).
--
Martin v. Löwis mar...@v.loewis.de added the comment:
On my computer, connect() on a UDP socket always finishes
successfully. What's wrong?
Nothing is wrong. UDP is connection-less, so connect() is a no-op,
except that it remembers the address so you can use send() instead
of sendto(). Any
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
I worked on the 3.2 branch, because the default branch has broken
test_logging.
What breakage are you referring to? There's a race condition test that fails on
Windows sometimes, but that's on the 2.7 branch. Apart from that, I don't
13 matches
Mail list logo
