On Thursday, April 30, 2020 5:53:33 AM EDT Scott Kitterman wrote: > 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 by it.
Making dirtbike build a py3 wheel for setuptools (and pkg_resources), which is technically accurate at this point since dirtbike can't build wheels from a python2 package was trivial to do: dirtbike/__init__.py | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) Three of the five insertions were comment. If someone wants to provide a patch to dirtbike so it can also build wheels from python-setuptools and python-pkg-resources, then we could add then to build-depends and provide both a set of py2 wheels and py3 wheels for as long as they are in the archive. It still needs the Python policy change since they aren't universal, but it would allow setuptools to keep up for python3 in pip without dropping the local wheels from python2. We also have ipaddr back in the archive to support wheeling it so pip will run with python2. I think that would be the best technical approach for now, but I don't have time at the moment to proceed further. Contributions welcome. I'd like to resolve this one way or the other because as it stands, the next python-pip upload will make wheels from python3-setuptools and python3-pkg- resources that are formatted as universal wheels, but aren't in terms of content. I've started working on packaging pip 20.1. Once I have it ready to go, I'll upload dirtbike either as it stands or with support for making python2 wheels if someone provides it. Just uploading pip using the current dirtbike is not appropriate. Scott K
signature.asc
Description: This is a digitally signed message part.
