Bug#945741: tcvt: Python2 removal in sid/bullseye
wf...@niif.hu writes: > Helmut Grohne writes: > >> On Wed, Nov 27, 2019 at 11:58:53PM +, Sandro Tosi wrote: >> >>> - Convert your Package to Python3. This is the preferred option. >> >> Upstream here. While tcvt started on Python2, much of its development >> actually happend on Python3, so just changing the #! should work. > > And I wanted to package it for Python3 in the first place. I'm puzzled > that it uses Python2 despite dh --with python3 and the python3 build > dependency. I'd be grateful for an explanation or some suggestions. Maybe I expected too much of dh_python3. Patching the interpreter name to /usr/bin/python3 works of course, I'm just not sure it's best practice. -- Regards, Feri
Bug#945741: tcvt: Python2 removal in sid/bullseye
Helmut Grohne writes: > On Wed, Nov 27, 2019 at 11:58:53PM +, Sandro Tosi wrote: > >> - Convert your Package to Python3. This is the preferred option. > > Upstream here. While tcvt started on Python2, much of its development > actually happend on Python3, so just changing the #! should work. And I wanted to package it for Python3 in the first place. I'm puzzled that it uses Python2 despite dh --with python3 and the python3 build dependency. I'd be grateful for an explanation or some suggestions. -- Thanks, Feri
Bug#945741: tcvt: Python2 removal in sid/bullseye
Hi Sandro, On Wed, Nov 27, 2019 at 11:58:53PM +, Sandro Tosi wrote: > Your package either build-depends, depends on Python2, or uses Python2 > in the autopkg tests (the specific reason can be found searching this > source package in > https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). > Please stop using Python2, and fix this issue by one of the following > actions. Thank you for filing these bugs. I'm kinda surprised that this bug report comes so "late" given that tcvt is an application package, which should have received such a bug much earlier given that converting applications is much less controversial than removing python2 libraries. > - Convert your Package to Python3. This is the preferred option. In > case you are providing a Python module foo, please consider dropping > the python-foo package, and only build a python3-foo package. Please > don't drop Python2 modules, which still have reverse dependencies, > just document them. Upstream here. While tcvt started on Python2, much of its development actually happend on Python3, so just changing the #! should work. I was briefly looking whether this is easily fixable upstream. PEP-0394 appears to indicate that plain python is not the worst choice for publishers, so it seems to me that fixing this in the packaging is the way to go. Helmut
