On April 30, 2020 7:21:39 AM UTC, Matthias Klose <d...@debian.org> wrote:
>On 4/30/20 5:28 AM, Scott Kitterman wrote:
>> I think Python policy changes should be discussed. I accidentally
>committed a
>> change to git [1] (I didn't realize I still had access, I thought it
>would be
>> a merge request) to allow Python 3 only wheels for packages that
>require
>> wheels, but that no longer support Python 2. This is going to happen
>the next
>> time I upload python-pip since the current version of setuptools is
>python3
>> only.
>
>this is not true. python-setuptools is still built from the source
>packages
>python-setuptools. Is there a reason that you cannot use it?
In the short run, the blocker is that dirtbike doesn't support it. In the
longer run I think adding back python2 dependencies is not a good idea.
At best it's a short-term avoidance mechanism.
>> Hopefully this won't be controversial. There's really no way to
>> avoid it.
>
>well, better don't assume that.
It's true that there is a short-term alternative, but I think it's a waste of
effort to try and implement it. At most it only buys you until the next pip
vendored lib that we unbundle as a wheel goes python3 only.
Are you volunteering to rewrite dirtbike so it can make a universal wheel from
python-setuptools?
Personally, I'm not interested. If you add the word reasonable to my original
statement, I stand bye it.
Scott K
