Erwan Le Pape <lepaperw...@gmail.com> added the comment:
I don't have an AIX lying around to test so would you mind just running the
test on `getaddrinfo` for AIX. A simple `python3 -c 'import socket;
print(socket.getaddrinfo("fe80::1%1", 80))'` should fairly rapidly determine if
there is a legitimate reason for the test to fail (ie. this is internal to
`asyncio`) or if this is tied to the underlying AIX `getaddrinfo`.
The IPv6 Scoped Address Architecture RFC clearly indicates that `<addr>%<zone>`
should be supported although it isn't a must. Hopefully there's a subtlety to
`getaddrinfo` on AIX (maybe in the way the zone should be specified, I already
had to fallback to numeric interfaces so the test would work on both Linux &
Windows, I wouldn't be surprised if AIX had yet another syntax for it).
Also, it would be worthwhile to ensure that the patches mentioned by IBM
https://www-01.ibm.com/support/docview.wss?uid=isg1IV52116 are applied on the
machine running the test.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue35545>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
