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.
Type hints
See original GitHub issueAre there plans to add type annotations or stub files for mypy?
I’ve written an article about type annotations if you need one 😃
A related topic is the Python 2.7 support. Stub files can be added without affecting any runtime, but they are harder to maintain (as they are extra files - I’m not sure how often schedule is refactored / new functionality is added).
Having Python 3.6+ would allow schedule to use a very nice annotation syntax. Generally speaking, this type of type annotations makes code way easier to read.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
ah yes, I have no idea how to do auto-formatting using flake8, I just manually fix the errors 😆 Never took the time to figure that out. If you do, sharing would be much appreciated ❤️
Python 2.7 has been dropped! Is anyone willing to implement this and create a pr?
We can add the type hints to the main source file itself. Let’s focus on the library code first, adding types to the testing code is optional