You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if the typeshed would be updated before the next release (next week? #10600).
Pitch
Recently I improved some commonly used classes in tkinter stubs: python/typeshed#5586, python/typeshed#5584, python/typeshed#5583. These are not actually usable to most people, and in my project, a custom typeshed as submodule causes trouble to other people working on the project.
Releasing a new version of typeshed is a pretty heavy process, since we want to validate it with internal Dropbox repos. I don't want to go through a full release process now, so this means that we can't really update typeshed until later. However, cherry-picking specific typeshed commits that are known to cause trouble is fine. Would that work for you?
It would work, but perhaps we should ask other typeshed people if there's anything they want to include. My cherry-picked typeshed branch, based on the latest "Sync typeshed" commit in mypy history, is https://github.com/Akuli/typeshed/tree/mypy-typeshed.
Cherry-picking typeshed fixes is not something we have normally done, but we can use just the tkinter stub fixes as a test run. If things work out well, we can publicize this more widely.
Feature
It would be nice if the typeshed would be updated before the next release (next week? #10600).
Pitch
Recently I improved some commonly used classes in tkinter stubs: python/typeshed#5586, python/typeshed#5584, python/typeshed#5583. These are not actually usable to most people, and in my project, a custom typeshed as submodule causes trouble to other people working on the project.
To show the difference, I created #10620.
The text was updated successfully, but these errors were encountered: