[issue24295] Backport of #17086 causes regression in setup.py

Irit Katriel added the comment: Python 2-only issue. -- nosy: +iritkatriel resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ __

[issue24295] Backport of #17086 causes regression in setup.py

Moritz Sichert added the comment: This is still an issue in Python 2.7.11. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue24295] Backport of #17086 causes regression in setup.py

Moritz Sichert added the comment: No this isn't an issue in Python 3.5. It was caused by the backport that was diffed against an older version that didn't include 7955d769fdf5 and thus reverted that. -- ___ Python tracker

[issue24295] Backport of #17086 causes regression in setup.py

STINNER Victor added the comment: doko wrote: "I'll look at this in June." @doko: ping? :-) @moritzs: Does Python 3.5 have the same issue? -- nosy: +haypo ___ Python tracker __

[issue24295] Backport of #17086 causes regression in setup.py

Moritz Sichert added the comment: I wouldn't call it reverting since it already was like this before and only got changed by accident in another backport. -- ___ Python tracker

[issue24295] Backport of #17086 causes regression in setup.py

Matthias Klose added the comment: I'll look at this in June. I don't think that reverting is the right choice here. -- ___ Python tracker ___ ___

[issue24295] Backport of #17086 causes regression in setup.py

Changes by Ned Deily : -- nosy: +doko priority: normal -> high ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24295] Backport of #17086 causes regression in setup.py

New submission from Moritz Sichert: In 7955d769fdf5 a bug of #14330 got fixed and it got backported for 2.7. But these changes were reverted by another backport in 8ee6d96a1019 (which was a backport for #17086). The issue here is that right know setup.py looks for ssl and other libs' headers i