Ned Deily <n...@python.org> added the comment:
Thank you for the report and for the analysis. As you probably know, Python 3.6 is now in the security phase of its life cycle so generally only fixes for security-related issues are provided at this point. This issue doesn't seem to fall into that category. If you have a workaround for 3.6.x, documenting it is probably the best available option. I'm going to close this as "wont fix". https://www.python.org/downloads/ ---------- nosy: +ned.deily resolution: -> wont fix stage: -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue41451> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
