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 dgelessus
Recipients dgelessus, docs@python
Date 2019-09-27.11:48:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
According to bpo-35089 (and the GitHub issues linked there), the and modules should no longer be used. Starting with Python 3.6, the typing documentation no longer mentions the and modules, and instead documents their contents as part of the main typing module.

However, the typing module at runtime still supports and as before. Since these modules are not meant to be used anymore and are no longer documented, I would expect at least a DeprecationWarning when using them at runtime.

The documentation on this could also be a bit clearer. As long as the modules are still supported at runtime, I would expect the documentation to mention that they still exist, but shouldn't be used anymore. In its current state, the documentation is confusing when coming from Python 3.5 (where and were the only documented way to access IO, Pattern, etc., but accessing typing.IO and typing.Pattern directly also works at runtime).
Date User Action Args
2019-09-27 11:48:37dgelessussetrecipients: + dgelessus, docs@python
2019-09-27 11:48:37dgelessussetmessageid: <>
2019-09-27 11:48:37dgelessuslinkissue38291 messages
2019-09-27 11:48:36dgelessuscreate