Michele Orrù added the comment: > >> Buggy due to the use of scanf at Modueles/socketmodule.c:868 > > I don't think so. The following test fails because sscanf() returns 5 > instead of 4: You are right, sorry for didn't notice.
> If you consider that '192.168.1.1 ' is an invalid name, you should > report the issue to the vendor of the C library of your OS. Yep, I'm going to ask on #glibc if there is any specific reason for accepting trailing spaces. But this concerns the specific underlying implementation if getaddrinfo(), so IMO we should just update the int overflow issue for now, maintaining the coherence with other utilities having the same "problem". For this, I am attaching a new patch which which just do not test for trailing whitespaces. -- ù ---------- Added file: http://bugs.python.org/file27549/issue16201.1.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16201> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
