Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime. Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2 To help planning, we'd like to know the plans for python-socksipychain's future. Specifically: - What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) - What are the upstream/community plans/timelines regarding Python 3? - What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?) This bug is filed semi-automatically, and might not have all the context specific to python-socksipychain. If you need anything from us, or something is unclear, please mention it here. Thank you.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages If you need any information or help, or if you need some more time, please let us know.
- What is the reason for the Python2 dependency? Upstream does not support it yet. This is pure-python code, migration should not be difficult. - What are the upstream/community plans/timelines regarding Python 3? They have raised the priority now, both Fedora (me) and Debian packagers requested migration. - What is the guidance for porting to Python 3? I am going to wait, I don't know Python enough to do the migration.
Is there any bug tracker or mailing list we can follow to see the progress of the porting?
Any news here?
There is a PR to add Python 3 support for tests: https://github.com/pagekite/PySocksipyChain/pull/6
Changes in the mentioned PR look good. Please, do you have some working setup? I'd like to help to make this Python 3 compatible but the tests do not work for me.
Unfortunately I don't, let's wait what maintainers say.
There is a new PR from me which is working well with both Pythons and local instance of Socks5 proxy: https://github.com/pagekite/PySocksipyChain/pull/7 Could you please help me to test this?
Do we have anything new here?
Well I guess everything is on track: https://github.com/pagekite/PySocksipyChain/pull/7
Well, it seems that it will take some time until the PR will be merged. Could you please backport the patch and try to build/use it in rawhide? The current plan is to remove packages with dependency on Python 2 from Fedora 32 in the middle of November 2019. If you want to keep your package in Fedora after that date and you cannot port it to Python 3 yet, you need to request a FESCo exception for the package and all its Python 2 dependencies (even transitive) [1]. If you don't want to maintain it anymore, and nothing in Fedora uses it, you can retire it or just remove the Python 2 part from it (subpackage, module, bindings, etc.). If you're considering filing the exception request, let us know. We can help (for example, we can help find all the dependencies). [1] https://fedoraproject.org/wiki/Changes/RetirePython2#FESCo_exceptions
Any news here? We are closer and closer to the deadline and this package should either request an exception or switch to Python 3.
PR is merged. Could you please update the RPM package?
Hello, apologies for the delay. I was on PTO. Well, too late. The package has been removed. Upstream is actually not yet done, see the last comment: https://github.com/pagekite/PySocksipyChain/pull/7 I think we can close this BZ for now, the problem has been "solved" for now but I am going to monitor this and once this tool is released with full python3 support I am going to put it back in. Thanks for help.
Sorry, but I don't see the package removed. Should we do that?
*** This bug has been marked as a duplicate of bug 1775090 ***