Re: [RFC] Dropping Python2 support for my package

On Sat, Jan 12, 2019 at 04:39:44PM +0100, Bastian Venthur wrote: > > just drop the python-debianbts binary, without doing any kind of > > strange migration, and keep the name python-debianbts for the > > python3 package, as the Debian Python Policy states. > > I think there's an error in your

Re: [RFC] Dropping Python2 support for my package

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am 12.01.19 um 16:49 schrieb Andrey Rahmatullin: > On Sat, Jan 12, 2019 at 04:39:44PM +0100, Bastian Venthur wrote: The question is: if I drop Python2 support, what happens with the package names? Should I simply provide the

Re: [RFC] Dropping Python2 support for my package

On Sat, Jan 12, 2019 at 04:39:44PM +0100, Bastian Venthur wrote: > >> The question is: if I drop Python2 support, what happens with the > >> package names? Should I simply provide the python3-debianbts and > >> drop python-debianbts, or shall I attempt some kind of migration > >> to make the

Re: [RFC] Dropping Python2 support for my package

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am 12.01.19 um 16:32 schrieb Mattia Rizzolo: > On Sat, Jan 12, 2019 at 04:28:26PM +0100, Bastian Venthur wrote: >> The question is: if I drop Python2 support, what happens with the >> package names? Should I simply provide the python3-debianbts and

Re: [RFC] Dropping Python2 support for my package

On Sat, Jan 12, 2019 at 04:28:26PM +0100, Bastian Venthur wrote: > The question is: if I drop Python2 support, what > happens with the package names? Should I simply provide the > python3-debianbts and drop python-debianbts, or shall I attempt some > kind of migration to make the python-debianbts

[RFC] Dropping Python2 support for my package

Hi, I'm about to drop Python2 support for python-debianbts. Currenty the source package produces two packages: python-debianbts and python3-debianbts. The question is: if I drop Python2 support, what happens with the package names? Should I simply provide the python3-debianbts and drop