-
Notifications
You must be signed in to change notification settings - Fork 2
Python2 > Python3 - Support Debian 2020 #15
Comments
For more info about the Python 2 EOL: |
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. |
@hukka @xi @andreasvc @Argafal @climent
Have all the cplay folks considered joining forces on one version of
cplay instead of maintaining individual forks?
|
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. |
The reason I ask is that @diegosarzi was intending to adopt the Debian
package of cplay and update it and so would have to chose one of the
forks as the successor of the version @hukka abandoned. It would be
thus be better for Debian if efforts were solely organised around one
of the forks rather than being split into two forks.
|
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. |
To avoid confusion I could either point to the selected repos, both, or simply close my repo here, which indeed is pretty much abandoned. |
As I know the cplay is a little abandoned and because of the python2 losing
support soon, the fork is active I packed the cplay-ng and am waiting for
the sponsor to check.
https://mentors.debian.net/package/cplay-ng
2018-05-02 2:57 GMT-03:00 Tomi Hukkalainen <[email protected]>:
… To avoid confusion I could either point to the selected repos, both, or
simply close my repo here, which indeed is pretty much abandoned.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ASngrZSa1rjwiO-mlXnx_a2I3HOwWN3Tks5tuUrYgaJpZM4TbWzW>
.
--
Diego Sarzi
...........................................
*Visite meu Website:*
*diego.sarzi.com.br <http://diego.sarzi.com.br/>*
|
@hukka, if there is a way to redirect to one of the forks, that would
be best. Otherwise, add a note that the repository is abandoned and
that the code is now developed in the two new repositories.
@diegosarzi, I'd suggest calling the new package cplay instead of
cplay-ng. Renaming packages is just annoying for users, it is better to
continue using the same name.
|
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.
The text was updated successfully, but these errors were encountered: