[issue22455] idna/punycode give wrong results on narrow builds

2020-12-01 Thread Irit Katriel
Change by Irit Katriel : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue22455] idna/punycode give wrong results on narrow builds

2016-06-24 Thread Mark Lawrence
Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___

[issue22455] idna/punycode give wrong results on narrow builds

2016-06-24 Thread Josh Lee
Changes by Josh Lee : -- nosy: +jleedev ___ Python tracker ___ ___ Python-bugs-list

[issue22455] idna/punycode give wrong results on narrow builds

2015-03-07 Thread Mark Lawrence
Mark Lawrence added the comment: As 2.7 is to be supported until 2020 and a potential fix is available shouldn't we be using it? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22455

[issue22455] idna/punycode give wrong results on narrow builds

2014-09-23 Thread Antoine Pitrou
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22455 ___ ___ Python-bugs-list mailing

[issue22455] idna/punycode give wrong results on narrow builds

2014-09-21 Thread Buck Golemon
New submission from Buck Golemon: I have fixed the issue in my branch here: https://github.com/bukzor/cpython/commit/013e689731ba32319f05a62a602f01dd7d7f2e83 I don't propose it as a patch, but as a proof of concept and point of discussion. If there's no chance of shipping a fix in 2.7.9, feel

[issue22455] idna/punycode give wrong results on narrow builds

2014-09-21 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- nosy: +lemburg, ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22455 ___ ___ Python-bugs-list