[Python-Dev] Intent to accept PEP 561 -- Distributing and Packaging Type Information

Nick Coghlan ncoghlan at gmail.com
Fri Jun 22 09:10:23 EDT 2018

On 21 June 2018 at 07:06, Guido van Rossum <guido at python.org> wrote:
> Only the last two commits are new since the last posting: support for
> partial packages and a bunch of small textual tweaks I found today while
> reviewing. There wasn't a lot of feedback then so I don't expect a flamewar
> today, but better late than never. ;-)

Something that was raised indirectly in
https://github.com/pypa/warehouse/issues/4164 was the terminology
collision between type hinting stub files, and API testing stub

I don't think that's actually a problem, since type hinting stubs will
only contain interface files, and not regular source files. This means
that a type hinting stub could later be expanded in scope to also
become an API emulating testing stub, and the two use cases wouldn't
conflict (I'm not commenting on whether or not that would actually be
a good idea - I'm just noting that PEP 561 claiming the
"<project>-stubs" naming convention on PyPI doesn't close out that

Beyond that, I think the other points I raised in the Warehouse
tracker issues can be considered derived requirements arising from the
PEP acceptance - if anyone tries to use the window between PEP 561
being accepted, and the related permissions being enforced in PyPI to
squat on stubs-related project names, then PEP 541 provides a
mechanism for addressing that.


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list