Question: behavior of stub files as packages evolve

[snakescott]

It doesn't look like stubs in third_party are versioned with the packages they represent. E.g. there is third_party/2/boto, not third_party/2/boto/v2.42.0, third_party/2/boto/v2.43.0, ....

As boto adds (or worse, changes or removes!) functionality and APIs, my dependent codebase -- and requires/install_requires dependencies -- will evolve with it in ways that seem potentially more complex than what picking a typeshed.git revision to power mypy supports.

In this case do I need to be managing my own typeshed? Are there best practices for ensuring consistency between a codebase (including dependencies) and a typeshed?

[gvanrossum]

This is a duplicate of #153.

[snakescott]

Thanks! I'll try to make sure to search existing issues next time.