Skip to content
This repository was archived by the owner on Jul 10, 2018. It is now read-only.

Python2 > Python3 - Support Debian 2020 #15

Open
diegosarzi opened this issue Apr 19, 2018 · 9 comments
Open

Python2 > Python3 - Support Debian 2020 #15

diegosarzi opened this issue Apr 19, 2018 · 9 comments

Comments

@diegosarzi
Copy link

How are you? I'm updating the "cplay" package in Debian, and I'd like to warn you that in 2020 we will no longer have support for python2, if you could pass the code to python3, thank you. So I can re-boot the Debian repository.

@pabs3
Copy link

pabs3 commented Apr 19, 2018

For more info about the Python 2 EOL:

https://pythonclock.org/

@xi
Copy link

xi commented Apr 19, 2018

This repository has not been updated in the last 7 years. I maintain an active fork at https://github.com/xi/cplay-ng. The only other active fork I know of is https://github.com/andreasvc/cplay. Both these forks support python3.

@pabs3
Copy link

pabs3 commented Apr 19, 2018 via email

@xi
Copy link

xi commented Apr 19, 2018

Of course we have. andreasvc and me exchange patches on a regular basis. As it is simple to use either version, there does not seem to be much demand for a unified release.

@pabs3
Copy link

pabs3 commented Apr 19, 2018 via email

@xi
Copy link

xi commented Apr 19, 2018

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896089

Efforts are concentrated. You can pick either fork. Both will receive the patches the other one gets. Sometimes there may be stylistic differences. But that does not need to concern you.

In other words: If debian decides to go with andreasvc's fork, I will be a regular contributor. However, I may additionally keep maintain my own fork just for fun.

@hukka
Copy link
Owner

hukka commented May 2, 2018

To avoid confusion I could either point to the selected repos, both, or simply close my repo here, which indeed is pretty much abandoned.

@diegosarzi
Copy link
Author

diegosarzi commented May 2, 2018 via email

@pabs3
Copy link

pabs3 commented May 4, 2018 via email

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

No branches or pull requests

4 participants