Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #11231 > unrolled thread

[RFC] Dropping Python2 support for my package

Started byBastian Venthur <venthur@debian.org>
First post2019-01-12 16:30 +0100
Last post2019-01-12 18:40 +0100
Articles 6 — 3 participants

Back to article view | Back to linux.debian.maint.python

Contents

  [RFC] Dropping Python2 support for my package Bastian Venthur <venthur@debian.org> - 2019-01-12 16:30 +0100
    Re: [RFC] Dropping Python2 support for my package Mattia Rizzolo <mattia@debian.org> - 2019-01-12 16:40 +0100
      Re: [RFC] Dropping Python2 support for my package Bastian Venthur <venthur@debian.org> - 2019-01-12 16:50 +0100
        Re: [RFC] Dropping Python2 support for my package Andrey Rahmatullin <wrar@debian.org> - 2019-01-12 16:50 +0100
          Re: [RFC] Dropping Python2 support for my package Bastian Venthur <venthur@debian.org> - 2019-01-12 17:00 +0100
        Re: [RFC] Dropping Python2 support for my package Mattia Rizzolo <mattia@debian.org> - 2019-01-12 18:40 +0100

#11231 — [RFC] Dropping Python2 support for my package

FromBastian Venthur <venthur@debian.org>
Date2019-01-12 16:30 +0100
Subject[RFC] Dropping Python2 support for my package
Message-ID<xftot-33q-7@gated-at.bofh.it>
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 python-debianbts, or shall I attempt some
kind of migration to make the python-debianbts the new default package
name for Python3?

Thanks for your hints!

Bastian


-- 
Dr. Bastian Venthur                                 https://venthur.de
Debian Developer                                 venthur at debian org

[toc] | [next] | [standalone]

#11232

FromMattia Rizzolo <mattia@debian.org>
Date2019-01-12 16:40 +0100
Message-ID<xftya-36z-13@gated-at.bofh.it>
In reply to#11231

[Multipart message — attachments visible in raw view] — view raw

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 the new default package
> name for Python3?

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.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

[toc] | [prev] | [next] | [standalone]

#11233

FromBastian Venthur <venthur@debian.org>
Date2019-01-12 16:50 +0100
Message-ID<xftHQ-3a7-5@gated-at.bofh.it>
In reply to#11232
-----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
>> drop python-debianbts, or shall I attempt some kind of migration
>> to make the python-debianbts the new default package name for
>> Python3?
> 
> 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 advice and I can't figure out what
you mean. You're suggesting to drop *and* to keep the python-debianbts
package :) Can you please clarify?

Thanks!





- -- 
Dr. Bastian Venthur                                 https://venthur.de
Debian Developer                                 venthur at debian org

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEh5WvLkoaTvugaKRJjoiVRNmFAA0FAlw6CjQACgkQjoiVRNmF
AA3TNA//eKN0UMeJ6iQDwwVs6cH/s+j3qcx4AfXCAaDuOrY3++BDZk03jKRlCu7a
357Tq1k0MOlAJ0w6sT4xqp4+4/9/Hf/nS2TnB0y4fvE/mLfkJiwMMCVh1eS6Hwu2
L0qiMf65aHOV3Jr5roWfVU35dXBE5PoTPJGP5ZgKVRQ/kJeD58oNORu70SnMhHyu
a2qbyDVtc64mhq7uq8beylPd4H9lLRfras95EwKH+U9SAF8a9hh1H7a+Lxpb91mx
8ZarUQziSX2xMiOCtGPi2RDEJBdC4mVIfizQD536Aznp7OerRzkKwpW2aSLOJU2X
rBlm96mGH79ekvt+pQbh+1PqsnA5feb96bWVq4CwCFCrhCcz7C1rFy4aN3LFNoIx
vBGdpwRKdY6CColddqY2Yj73IebF9gMNrOybM69Q0xDvEOQVGTWP29yuKUdOQoKp
FslNIATxITml4HpTBmI0Mh8wDMoNq7q47d0XzmmGvESbN+7gqR9XCBqvaBb7EALG
XDNPBo55Zflgh82GpRbKcSV888pESTsYviZrtlpMFHIDH9kztaThTFX0eygZUPik
5Se+yKBpdB5BChVQznhemFTcKZcmvar1Eb1Hn9wKLUFZTlHs9Ecxu8uK5kAXN6Eq
EGKJBSsto/RrmLC46WQaDbEDylzPRSAVBnkcAP+se0lTqTzulgA=
=w1LF
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#11234

FromAndrey Rahmatullin <wrar@debian.org>
Date2019-01-12 16:50 +0100
Message-ID<xftHQ-3a7-13@gated-at.bofh.it>
In reply to#11233

[Multipart message — attachments visible in raw view] — view raw

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 python-debianbts the new default package name for
> >> Python3?
> > 
> > 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 advice and I can't figure out what
> you mean. You're suggesting to drop *and* to keep the python-debianbts
> package :) Can you please clarify?
Drop binary python-debianbts package, keep the source package name as
python-debianbts.

Or were you asking about shipping the py3 module inside the
python-debianbts binary package? We don't do that.


-- 
WBR, wRAR

[toc] | [prev] | [next] | [standalone]

#11235

FromBastian Venthur <venthur@debian.org>
Date2019-01-12 17:00 +0100
Message-ID<xftRw-3dg-1@gated-at.bofh.it>
In reply to#11234
-----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
>>>> python3-debianbts and drop python-debianbts, or shall I
>>>> attempt some kind of migration to make the python-debianbts
>>>> the new default package name for Python3?
>>> 
>>> 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 advice and I can't figure out
>> what you mean. You're suggesting to drop *and* to keep the
>> python-debianbts package :) Can you please clarify?
> Drop binary python-debianbts package, keep the source package name
> as python-debianbts.
> 
> Or were you asking about shipping the py3 module inside the 
> python-debianbts binary package? We don't do that.
> 
> 
Thanks!

- -- 
Dr. Bastian Venthur                                 https://venthur.de
Debian Developer                                 venthur at debian org

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEh5WvLkoaTvugaKRJjoiVRNmFAA0FAlw6DhQACgkQjoiVRNmF
AA07yRAAyHk8QZgk/GcDmINyrz1JfA9LyNFJCtBWzNxA9h8heZDQ0+YjJo5Nv9u6
9GNmq4OujP9yBEI7zTqROnI95sLJfSAQSOP2u+EWEji5e6gS7C/bQedhOIfjpX6O
x9TMyI6wRfX0yN1A/sT8C/iA0Wku8afyEV81cNA5aLmZx2EKo+hpPaV4nkYaVFbH
O/GBcrsqAxP591XsBFo5MhRS4mvCdBL5hM2pLCf8cdBAWjO/yYOPAFJuW+P7Q6Wu
J700Dh8WDQQb/t/eudOiOihORwfBJPrgtiF+IH2zXIn6kLGNmqNNZEw6n9bnn/m4
srNYFY9oTaXjdYVzTCB1cRVhXMva2jxR7WKCYaWRDLsyK+EfZhATE9iRRO0S7waG
y1BgKpCY4SkCGgH5vYIr20FpvYNUptYmQh/ZCDbl1guDfS0Lzy1h0ZDasOjbCt2L
hl6Yqidphh1LdryZoOfrSCex5sj8mBOnpfeVxZyHQMpoULvSnx/+F/2wASIbWxTR
551rY6gy2B5rm2YGk1rGaN/OF44jhx8K8NoFB6uCsteOlFuR9Ll8wEFLIPqL8GSE
5EMgmuoNnMpFfhV8EIeASWfKbVor8RQwLcdoYYDuq9vXaMQ3loRflla5Y0+CVKtl
SLWtx79FN/mfxaA2AMU3QxmgKJMkQXyKZ8fu+lHwQYFjMzJ7ix4=
=xxSc
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#11238

FromMattia Rizzolo <mattia@debian.org>
Date2019-01-12 18:40 +0100
Message-ID<xfvqi-4er-15@gated-at.bofh.it>
In reply to#11233

[Multipart message — attachments visible in raw view] — view raw

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 advice and I can't figure out what
> you mean. You're suggesting to drop *and* to keep the python-debianbts
> package :) Can you please clarify?

Yes, I made an error there indeed (that I think Andrey corrected
already).  But let my try again:

just drop the python-debianbts binary, without doing any kind of
strange migration, and keep the name python3-debianbts for the
python3 package, as the Debian Python Policy states.

As Andrey wrote, don't touch the source package name either.


Sorry if I spread confusion accidentally…

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web