[issue27644] Expand documentation about type aliases and NewType in the typing module

Guido van Rossum added the comment: Mercurial revs: fd0dce6d33e7, 15a35a8da24b, 4ecea1ea11bf, 4ecea1ea11bf. -- ___ Python tracker ___

[issue27644] Expand documentation about type aliases and NewType in the typing module

Guido van Rossum added the comment: Thanks! Should go live later today. -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue27644] Expand documentation about type aliases and NewType in the typing module

Ivan Levkivskyi added the comment: I have only one optional comment on the second revision. -- nosy: +gvanrossum ___ Python tracker ___

[issue27644] Expand documentation about type aliases and NewType in the typing module

Michael Lee added the comment: Ok, here's revision 2 of my patch, after applying the changes from the last round of feedback. -- Added file: http://bugs.python.org/file43939/document_newtype_rev2.patch ___ Python tracker

[issue27644] Expand documentation about type aliases and NewType in the typing module

Ivan Levkivskyi added the comment: > Should I edit the patch to include a sentence or two describing this > distinction, just remove the word "almost", or do something else? I think the best way is to remove the "almost" and briefly explain that you cannot subclass types returned by NewType.

[issue27644] Expand documentation about type aliases and NewType in the typing module

Ivan Levkivskyi added the comment: Added two small comments to the review. -- ___ Python tracker ___ ___

[issue27644] Expand documentation about type aliases and NewType in the typing module

Changes by Ivan Levkivskyi : -- nosy: +levkivskyi ___ Python tracker ___ ___

[issue27644] Expand documentation about type aliases and NewType in the typing module

New submission from Michael Lee: This is a patch to update the documentation on the typing module. It expands the section on type aliases and adds a section on [NewType][0]. Since support for NewType was [recently added][1] to mypy, it seemed like a prudent time to update the docs to describe