[issue41169] socket.inet_pton raised when pass an IPv6 address like "[::]" to it
Wator Sead added the comment: The point is square brackets, not the address, they (socket.inet_pton and socket.socket) behave different. Can make it not be accepted, any conditions? -- versions: -Python 3.7, Python 3.8 ___ Python tracker <https://bugs.python.org/issue41169> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41169] socket.inet_pton raised when pass an IPv6 address like "[::]" to it
Wator Sead added the comment: Can you try bind "::". My ask is "Can make a consistent behave via constraints it?". -- ___ Python tracker <https://bugs.python.org/issue41169> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41169] socket.inet_pton raised when pass an IPv6 address like "[::]" to it
Wator Sead added the comment: [::] can be bound, but the resoult is [::1], you must use this address to connect. Excuse me, are you a developer of the Python? >>> import socket >>> ls = socket.socket(socket.AF_INET6) >>> cs = socket.socket(socket.AF_INET6) >>> ls.bind(('[::]', 888)) # no raise >>> ls.listen(1) >>> cs.connect(('[::1]', 888)) # no raise -- ___ Python tracker <https://bugs.python.org/issue41169> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41169] socket.inet_pton raised when pass an IPv6 address like "[::]" to it
Wator Sead added the comment: I did not build it, just download the Windows pre-built releases. Can make a consistent behave via constraints it? socket.socket accepted it, but socket.inet_pton did not. -- ___ Python tracker <https://bugs.python.org/issue41169> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41169] socket.inet_pton raised when pass an IPv6 address like "[::]" to it
New submission from Wator Sead : 3.6: >>> import socket >>> socket.inet_pton(socket.AF_INET6,'[::]') b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' 3.7 and above: >>> import socket >>> socket.inet_pton(socket.AF_INET6,'[::]') Traceback (most recent call last): File "", line 1, in OSError: illegal IP address string passed to inet_pton Both: >>> import socket >>> addr = '[::1]', 888 >>> ls = socket.socket(socket.AF_INET6) >>> cs = socket.socket(socket.AF_INET6) >>> ls.bind(addr) # no raise >>> ls.listen(1) >>> cs.connect(addr) # no raise -- components: Library (Lib) messages: 372694 nosy: seahoh priority: normal severity: normal status: open title: socket.inet_pton raised when pass an IPv6 address like "[::]" to it type: behavior versions: Python 3.7, Python 3.8 ___ Python tracker <https://bugs.python.org/issue41169> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37535] Client SSLSocket with select.select() always returns readable with OpenSSL 1.1.1
Wator Sead added the comment: So, that means there are some additional optional operations after do_handshake(), the data is needed. Thanks for explanation! -- ___ Python tracker <https://bugs.python.org/issue37535> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37535] Client SSLSocket with select.select() always returns readable with OpenSSL 1.1.1
Wator Sead added the comment: Thanks for explanation, I understand what the reason is. But why do_handshake() not clear of useless data buffer after it is completed? I think that must be easy to do. -- ___ Python tracker <https://bugs.python.org/issue37535> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37535] Client SSLSocket with select.select() always returns readable with OpenSSL 1.1.1
Wator Sead added the comment: All new releases which include an OpenSSL version above 1.1.1 has the same issue. Can anybody fix it? Thanks a lot! -- nosy: +seahoh versions: +Python 3.5, Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue37535> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38534] Version 3.8.0 has released with a wrong MS KB number reference
Change by Wator Sead : -- pull_requests: -16425 ___ Python tracker <https://bugs.python.org/issue38534> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38534] Version 3.8.0 has released with a wrong MS KB number reference
Wator Sead added the comment: I can't signe the CLA. Someone will make a new PR. -- ___ Python tracker <https://bugs.python.org/issue38534> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38534] Version 3.8.0 has released with a wrong MS KB number reference
Wator Sead added the comment: PR16881 I just use the right one to replaced them. -- keywords: +patch message_count: 2.0 -> 3.0 pull_requests: +16425 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16881 ___ Python tracker <https://bugs.python.org/issue38534> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38534] Version 3.8.0 has released with a wrong MS KB number reference
New submission from Wator Sead : https://bugs.python.org/msg347421 Maybe you forgot it, please fix it in next versions. -- assignee: docs@python components: Documentation, Installation, Windows messages: 354986 nosy: docs@python, paul.moore, seahoh, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Version 3.8.0 has released with a wrong MS KB number reference type: resource usage versions: Python 3.8 ___ Python tracker <https://bugs.python.org/issue38534> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37894] [win] shutil.which can not find the path if 'cmd' include directory path and not include extension name
New submission from Wator Sead : The current code is: ... if os.path.dirname(cmd): if _access_check(cmd, mode): return cmd return None ... In Windows, if 'cmd' include directory path and not include extension name, it return 'None'. e.g. a file's path is 'd:\dir\app.exe', call shutil.which with 'cmd=="d:\dir\app"'. How about this patch: ... if os.path.dirname(cmd): path, cmd = os.path.split(cmd) ... -- components: Library (Lib) messages: 350019 nosy: seahoh priority: normal severity: normal status: open title: [win] shutil.which can not find the path if 'cmd' include directory path and not include extension name type: behavior versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8 ___ Python tracker <https://bugs.python.org/issue37894> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com