➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients evan_, flying sheep, gvanrossum, levkivskyi
Date 2017-01-15.23:00:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJK8Q4_dzx0qTH2qr6kRoxsx_MHPtQWcZuy1Hf7oLL49wQ@mail.gmail.com>
In-reply-to <1484521006.76.0.610826727885.issue29262@psf.upfronthosting.co.za>
Content 
Posting to python-dev would probably cause more friction than a PR for the
PEPs repo. But maybe the best way to do this is to use a third party module
with a proposed API? E.g. typing_inspect. We could then iterate quickly on
the design and implementation there, and we could commit to keeping it in
sync with changes to typing.py, so flying sheep's package could depend on
it.
History
Date User Action Args
2017-01-15 23:00:47gvanrossumsetrecipients: + gvanrossum, flying sheep, levkivskyi, evan_
2017-01-15 23:00:47gvanrossumlinkissue29262 messages
2017-01-15 23:00:46gvanrossumcreate