This issue is preventing me from updating a script to python3. The
script isn't part of a debian package, but it is crucial to building
roxterm, which is packaged. I'm willing to use a new lockfile API as
part of the update to python3, whereas most projects which aren't
prioritising on migrating from 2 to 3 are probably more "legacy" and the
maintainers won't want to have to deal with an API change.
So that gave me an idea, would it make sense to deal with it by keeping
the existing package for python2, and only supporting python3 for >= 0.9
and renaming the binary package to python3-lockfile? That way legacy
packages can carry on working for now without having to change anything,
while those wanting to migrate from python 2 to 3 can move on.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
