Control: tags -1 + patch

* Thomas Goirand <z...@debian.org> [2018-08-25 22:02:51 +0200]:

> Hi Sando,
> 
> I do support uploading 2 source packages, one for py2, and one for py3.
> This is the most reasonable solution. Worst case, if that cannot be
> done, then we got to move forward and restore Py3 support (and
> eventually drop Py2), but I prefer the former solution.
> 
> The issue has been opened for nearly 2 months now, with nearly a month
> without any news, and this makes me a bit nervous, as I need the py3
> support to be restored.
> 
> What's holding you off more?

Hi,

As a proof of concept I've gone and done the changes needed to pull this off on
a fork of the git repo in my personal namespace.

https://salsa.debian.org/olasd/astroid

The astroid source package is in the master / upstream branches;
The astroid2 source package is in the astroid2 / upstream-1.x branches.

I had to do some wrangling of the astroid source package, to convert it to
pybuild, because the default setuptools buildsystem only works when python2 is
in the build depends.

I could see a point in splitting the git repositories but I don't think that's
very critical.

I'm happy to do a NMU in a week so that we can move forward with the split
package plan.

Cheers,
-- 
Nicolas Dandrimont

We come to bury DOS, not to praise it.
(Paul Vojta, vo...@math.berkeley.edu, paraphrasing a quote of Shakespeare)

Attachment: signature.asc
Description: PGP signature

Reply via email to