That sounds like you're supporting PEP 561 as is, right? Excuse my ignorance, but where are API testing stub interfaces described or used?
--Guido On Fri, Jun 22, 2018 at 6:10 AM Nick Coghlan <ncogh...@gmail.com> wrote: > On 21 June 2018 at 07:06, Guido van Rossum <gu...@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 > interfaces. > > 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 > option). > > 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. > > Cheers, > Nick. > > -- > Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia > -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
