-
Notifications
You must be signed in to change notification settings - Fork 715
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature]: Generating type hints for API #568
Comments
Hello @sbdchd, Thank you for the suggestion! This issue has been added to our internal backlog to be prioritized. Pull requests and +1s on the issue summary will help it move up the backlog. With best regards, Elmer |
A little over a year. How long would it take an intern to do this and someone else to review it? Or maybe hire a contractor to do it for you? I know we are tossing $1000 a day at you for services.... |
Work is in progress on the v8 RC branch. |
Are there any updates on the progress here. v8 RC has been released as well as v8.1 and v8.2, but still no typing. Is this something that is still in progress? |
Jan 2024, more than 2.5 years after the issue is opened and still nothing v8.12.0 is what's installed and still NOTHING! We currently spend more than $2K every 3 days for your verify service. Maybe it's time to move to someone that cares enough to help out the developers.... |
Issue Summary
Currently the library doesn't have inline type hints or type stubs so we can't type check library usage
Since this library supports python 2.7 the inline type hints would need to follow the comment syntax
Another option is to package separate type stubs (
.pyi
files) alongside the existing codeSteps to Reproduce
Run your type checker of choice and see warnings about missing types / type stubs
The text was updated successfully, but these errors were encountered: