[Python-ideas] Moving typing out of the stdlib in Python 3.7?

[Antoine Pitrou]

On Sun, 5 Nov 2017 18:22:11 +0000
Paul Moore <p.f.moore at gmail.com> wrote:

> On 5 November 2017 at 14:47, Antoine Pitrou <antoine at python.org> wrote:
> >
> > Le 05/11/2017 à 14:30, Paul Moore a écrit :  
> >> On 5 November 2017 at 10:48, Antoine Pitrou <solipsis at pitrou.net> wrote:  
> >>> On Sun, 5 Nov 2017 13:46:59 +1000
> >>> Nick Coghlan <ncoghlan at gmail.com> wrote:  
> >>>> * ensurepip gains the ability to also install bundled wheel files  
> >>>
> >>> Why? Why wouldn't you put the wheel directly in site-packages on
> >>> install?  
> >>
> >> I'm not quite sure what you mean? It needs to be "installed", in the
> >> sense of being unpacked into site-packages, and the ensurepip
> >> mechanism is already able to do that for pip and setuptools, so adding
> >> an extra wheel to install wouldn't be too hard.  
> >
> > Ok, perhaps my question wasn't quite clear.  Are you suggesting that
> > people have to run "python -m ensurepip typing" after they installed
> > Python?  Or would the typing module be importable as soon as you have an
> > installed Python, like stdlib modules are?  
> 
> Ah, I get you now. I'd expect typing to be available exactly the same
> way as pip is. For me (on Windows) that means that it's available in a
> standard install. On Unix, I don't know (I think there's certain
> situations where you need to take extra steps in a custom build to
> ensure pip is available? I'd expect those steps to also install
> typing.

I think typing shouldn't require any extra typing (ha) on Unix either.
I don't remember what the rationale was for having to type
"python -m ensurepip" to get pip installed, but typing is just a
library, not an executable tool that may be able to mess with the
system state, so I don't think it's worthwhile introducing an extra
step for it.

Regards

Antoine.