[Pkg-fonts-devel] Bug#876439: Bug#876439: Continue providing Python 2 libraries

[Balasankar C <balasankarc@autistici.org>]

On Wed, 4 Oct 2017 10:22:22 +0200 Rene Engelhard <rene@debian.org> wrote:
> On Wed, Oct 04, 2017 at 04:16:58PM +0800, Yao Wei wrote:
> > Hi,
> > 
> > So, to actually maintain the dependency of fonts building, is it
> > advisable to let fonttools depend on python-fonttools instead of
> > python3-fonttools?
>
> There's neither. The module is in "fonttools". Which is why I asked
>
> > P.S:
> >
> > Shouldn't the python modules be split out to python-* and python-* packages?
> > That would make the support more clear. Or are they not supposed to be used
> > externally?
>
> in my initial report. (But yes, python-fonttools/python3-fonttools would make sense,
> but then fonttools probably should depends on the python3 thingy and people who need
> the python2 module can build-depend on python-fonttools. Or does stuff use stuff
> from fonttools _and a different_ python version?
>
> Regards,
>
> Rene

If we are splitting out python libraries, we need to have both 
python-fonttools and python3-fonttools packages, at least till Python 
2's EOL (or Python 2 is out of Debian). Even though mostly used as a 
library, fonttools do ship some binaries (like pyftinspect) that can 
remain in fonttools package.

So, I think there should be three packages
1. python-fonttools (Python 2.x libraries)
2. python3-fonttools (Pytohn 3.x libraries)
3. fonttools (Binaries like pyftinspect)

fonttools should depend on python-fonttools. Once when Python 2 is out 
of Debian, we can make python-fonttools use Python 3 and drop 
python3-fonttools.

WDYT?

Regards
Balasankar C