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
{{ message }}
Repository navigation
Move the typing module to a separate installation package #377
The typing module could be more generally useful even outside mypy, such as for annotating code for documentation purposes. Also, other tools such as IDEs, documentation tools could more easily use it.
I like the idea of a separate repo. Maybe we could include it as dependency and as git-submodule?
On Fri, Aug 15, 2014 at 7:13 PM, Guido van Rossum [email protected] wrote:
I am beginning to change my mind. Maybe typing.py should become a separate package in a separate repo after all, so that we can start working on the definitive version of typing.py to be included in the Python stdlib. (Of course, changes to typing.py would still need to be accompanied by changes in mypy, in most cases. But it might encourage contributors, and it could have its own, less overwhelming tracker.)
Reply to this email directly or view it on GitHub: #377 (comment)
I am beginning to change my mind. Maybe typing.py should become a separate package in a separate repo after all, so that we can start working on the definitive version of typing.py to be included in the Python stdlib. (Of course, changes to typing.py would still need to be accompanied by changes in mypy, in most cases. But it might encourage contributors, and it could have its own, less overwhelming tracker.)
Some additional points that support having a separate repo:
It's more convenient to maintain documentation in a standard format, and written using a
"neutral point of view" (i.e., not from the point of view of the mypy type checker).
We can iterate on it more quickly since mypy can trail a bit behind. If it's part of mypy, every
change in typing needs to be reflected in the mypy type parser, stubs files, documentation,
potentially the type checker, etc.
Activity
gvanrossum commentedon Aug 14, 2014
It should be separately installable. But it should still live in the same
repo.
[-]Move the typing module to a separate project[/-][+]Move the typing module to a separate installation package[/+]mvcisback commentedon Aug 14, 2014
How do you feel about
typingas a install dependency insetup.pyand userequirements.txtto point to the typing package in the repo?iljabauer commentedon Aug 15, 2014
I like the idea of a separate repo. Maybe we could include it as dependency and as git-submodule?
On Fri, Aug 15, 2014 at 7:13 PM, Guido van Rossum
[email protected] wrote:
gvanrossum commentedon Aug 15, 2014
[I wrote this and accidentally deleted it]
I am beginning to change my mind. Maybe typing.py should become a separate package in a separate repo after all, so that we can start working on the definitive version of typing.py to be included in the Python stdlib. (Of course, changes to typing.py would still need to be accompanied by changes in mypy, in most cases. But it might encourage contributors, and it could have its own, less overwhelming tracker.)
mvcisback commentedon Aug 15, 2014
+1 for making it a separate repo
JukkaL commentedon Aug 16, 2014
Some additional points that support having a separate repo:
"neutral point of view" (i.e., not from the point of view of the mypy type checker).
change in typing needs to be reflected in the mypy type parser, stubs files, documentation,
potentially the type checker, etc.
JukkaL commentedon Aug 31, 2014
I created a new repo: https://github.com/JukkaL/typing
What do you think?
mvcisback commentedon Sep 1, 2014
nice, I think this is the right direction. It should make packaging a lot easier
zyga commentedon Sep 1, 2014
Thanks for doing that. I'll start packaging typing for Debian today.
2014-09-01 7:55 GMT+02:00 Marcell Vazquez-Chanlatte <
[email protected]>:
JelleZijlstra commentedon Jul 1, 2017
This is long obsolete, since typing is now in the stdlib and being developed in github.com/python/typing.