Xavier Fernandez

> I think the easiest way to make sure this works correctly is to spin up our own PyPI endpoint locally. We could also, for each test, put the artefacts...

> Can we guarantee that virtualenv is using these pip options, though? According to https://github.com/pypa/virtualenv/blob/bcce79d2e827c32153a1a199ddbb99f289f7694d/virtualenv.py#L1014 it seems we cannot ^^ So a small http.server serving our artefacts with the matching...

Why option 3 and not any other one ? :-) Note also that all these discussions relate to the use of distutils/setuptools as build tool.

> Per the discussion earlier in this thread, option 3 seems to be the option that new projects are converging on. Do you observe otherwise? I must admit I usually...

:wave: As I was the one suggesting to add this classifier I would have used it in my (modest) pylint plugin https://pypi.org/project/pylint-strict-informational/ (and will use it).

> As a note I found the output of pip._internal.pep425tags.get_supported() to be very informative in identifying which tags pip will consider for a given target. Answered some questions I didn't...

Given that cpython automatically [caches](https://github.com/python/cpython/blob/master/Lib/re.py#L286) the last 512 regexes used, is there really a need to pre-compile all those regexes ?

I think it should (very) slowly be deprecated in favor of the PEP-508 blessed `pkg_name @ url`. (or am I missing something ?)

Maybe a warning to suggest the new PEP 508 syntax ? And a very long deprecation period...