[issue25784] Please consider integrating performance fix for ipaddress.py

Changes by Serhiy Storchaka : -- resolution: duplicate -> out of date stage: -> resolved ___ Python tracker ___ ___ Python-bugs-list

[issue25784] Please consider integrating performance fix for ipaddress.py

Alexander Finkel added the comment: Thanks for the responses. I'm afraid I was looking at the Python 3.3 source code on my desktop, it looks like the problem was fixed in the Mercurial repo about 10 months ago by https://hg.python.org/cpython/rev/f7508a176a09 Marked this issue as a duplicate?

[issue25784] Please consider integrating performance fix for ipaddress.py

SilentGhost added the comment: Perhaps I'm wrong, but a superficial inspection of the ipaddress.py seem to indicate that it's not affected by the same issue. _find_address_range is implemented as a generator, it doesn't restart comparison on every iteration. Alexander, did you experience any p

[issue25784] Please consider integrating performance fix for ipaddress.py

Serhiy Storchaka added the comment: Could you provide a patch? -- components: +Library (Lib) nosy: +ncoghlan, pmoody, serhiy.storchaka type: -> performance versions: +Python 3.6 ___ Python tracker

[issue25784] Please consider integrating performance fix for ipaddress.py

New submission from Alexander Finkel: I encountered a performance problem using the ipaddr library to merge over 1 network addresses. I sent a patch upstream to fix it, and that patch has been merged: https://github.com/google/ipaddr-py/commit/6504b47a02739e853043f0a184f3c39462293e5c Since