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
Attachment:
signature.asc
Description: PGP signature