https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229562
--- Comment #13 from Kubilay Kocak <ko...@freebsd.org> --- @Dmitry The main reason for the delay has been complete analysis of the issue and an understanding/confidence in the best approach to take with a long-term view of resolving the issue permanently (upstream). Additionally this issue is within a notoriously difficult and challenging class of "base vs local library conflicts" issues who's initial solutions have caused regressions elsewhere (eg: libintl, ssl, elementtree, expat issues in the poast). Lastly, is this an issue in other Python ports? If so, we want to solve this consistently across the board. That said, a two line patch to carry locally is fine if has been well QA tested, as it appears to be. Could you please add a comment above the new post-patch lines referencing this issue. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
