Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python3 Compatibility #211

Open
Cabalist opened this issue Mar 17, 2017 · 1 comment
Open

Python3 Compatibility #211

Cabalist opened this issue Mar 17, 2017 · 1 comment

Comments

@Cabalist
Copy link

REPORT A BUG/PROBLEM


Hi, I want to notify you of a bug/problem that is happening on the Planet.

I am using:
O.S: N/A
Browser: N/A
Platform: N/A

Problem

Python 2 is going away. This code is not compatible with Python3.

Details

This is more of a request for information than a bug. What is the path forward with this code as Python2 goes away? Is there any interest in moving this to 2.7 with compatibility for 3.4+?

Is it worthwhile to migrate this fork of planet over to python3 or is a new platform in the wings to replace this one?

Upon glancing at different parts of this code:
feedparser.py:
I know that feedparser has been maintained and has 10+ years of development over the one included in this repo. It also has python3 support

compat_logging:
Is there any reason the built-in logging won't work?

htmltmpl:
some work has been done in a github fork of the sourceforge repo

planet:
Main project looks dead. Has been rewritten in a number of different languages. The version included seems to have very little code commited to it. There is a later version in the main projects repo that includes TESTS. Perhaps rebase on that?

I would be happy to take some of this on if there is some willingness to accept pull requests. Any thoughts?

Thanks.

@Cabalist
Copy link
Author

More info as I am reading mailing lists and other old posts:

planet was superseded by venus (https://github.com/rubys/venus) based on the original planet code. The maintainer has said he is not working on it and it also has no Python3 support but the code is much further along than planet. (rubys/venus#37)

I've put in a request to see if that repo can get reactivated. There are quite a number of branches and pull requests active for it.

It should then be just a matter of moving the configs and templates over for the same functionality. I am not sure about other requirements as this is technically part of the python infrastructure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant