Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`typing.NoReturn` is new in Python 3.5.4 and 3.6.2
See original GitHub issueThe typing.NoReturn is New in version 3.5.4, 3.6.2
So it can’t run on python 3.6.1
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Typing `NoReturn` requires Python 3.5.4 · Issue #1271 - GitHub
Typing NoReturn was only introduced in 3.5.4 of Python, and PRAW allows for installation on 3.5.0 <= version <3.5.4 (3.5.0, 1, 2, ...
Read more >`typing.NoReturn` is new in Python 3.5.4 and 3.6.2 - - Bountysource
A utility library for parsing HTTP request arguments, with built-in support for popular web frameworks, including Flask, Django, Bottle, and Tornado. See More ......
Read more >typing — Support for type hints — Python 3.11.1 documentation
NoReturn can also be used as a bottom type, a type that has no values. Starting in Python 3.11, the Never type should...
Read more >typing - PyPI
This is a backport of the standard library typing module to Python versions older than 3.5. (See note below for newer versions.) Typing...
Read more >Incorrect "versionadded" info in typing.NoReturn documentation
NoReturn was added in both 3.5.4 and 3.6.2 It appeared from this change, that it was originally added in 3.6.5 (https://github.com/python/ ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks, @sirosen @lafrech . The problem is rare, and uses who face it can patch it themselves easily. So, it can be closed
Won’t fix is fine with me.
I remember @sloria wontfixing a similar issue in marshmallow. We could require >=3.6.2 but what about bugs that are fixed in a python version that is not the oldest supported major, like 3.7.3? We’d have to require 3.6.2 or >= 3.7.3. Not sure this is even feasible.
OTOH, this is not a bug fixed in 3.6.2 but a feature added there that we’re deciding to rely upon, so >=3.6.2 would make it clear indeed.