Move the typing module to a separate installation package

[JukkaL]

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.

This discussion on python-ideas is relevant:

https://mail.python.org/pipermail/python-ideas/2014-August/028618.html

EDIT: Changed from 'separate project' to a 'separate installation package'

[gvanrossum]

It should be separately installable. But it should still live in the same
repo.

[mvcisback]

How do you feel about typing as a install dependency in setup.py and use requirements.txt to point to the typing package in the repo?

[iljabauer]

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
notifications@github.com 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)

[gvanrossum]

[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]

+1 for making it a separate repo

[JukkaL]

Some additional points that support having a separate repo:

1. 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).
2. 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.

[JukkaL]

I created a new repo: https://github.com/JukkaL/typing

What do you think?

[mvcisback]

nice, I think this is the right direction. It should make packaging a lot easier

[zyga]

Thanks for doing that. I'll start packaging typing for Debian today.

2014-09-01 7:55 GMT+02:00 Marcell Vazquez-Chanlatte <
notifications@github.com>:

nice, I think this is the right direction. It should make packaging a lot
easier

—
Reply to this email directly or view it on GitHub
#377 (comment).

[JelleZijlstra]

This is long obsolete, since typing is now in the stdlib and being developed in github.com/python/typing.