Python 2 removal strategy

Hi, I am the maintainer of the "python-astropy" package, that currently creates packages for both Python 2 and Python 3. Both packages have a number of reverse dependencies. Recently, upstream announced a new version 3.0 of astropy, which supports Python 3 only, and I think of the best mid-term s

PyQwt3D packaging strategy

Hi list I am updating my package pyqwt3d. It is tested for Qt5, python2 and python3. The changes were so huge that I made GitHub fork of it: https://github.com/GauiStori/PyQwt3D Now I have two questions: 1. Shall I skip the python2 version since it is already end of life? 2. Shall I make my chan

Re: Python 2 removal strategy

On 10.01.2018 17:06, Ole Streicher wrote: > Hi, > > I am the maintainer of the "python-astropy" package, that currently > creates packages for both Python 2 and Python 3. Both packages have a > number of reverse dependencies. > > Recently, upstream announced a new version 3.0 of astropy, which >

Re: Python 2 removal strategy

Hi Ole, It would be great have two different package. One of them, the python3 version and maintain the python2 version. Regards! Emmanuel El mié., 10 de ene. de 2018 a la(s) 18:03, Matthias Klose escribió: > On 10.01.2018 17:06, Ole Streicher wrote: > > Hi, > > > > I am the maintainer of the

Re: Python 2 removal strategy

Hi Ole, > I thought of a temporary package split: create a new source package > "astropy" that inherits of the current python-astropy package, but only > builds python3-astropy (and the utils + doc, which depend on > python3-astropy), and update this to version 3.0. Then I would remove > these bin