-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Type hinting for common functions #1260
Comments
Hey, I was hoping to pick this up ! What do you mean by "common" functions in this context ? |
I am primarily talking about the ones exposed to the end user. The end goal is that things like self.client.post() and basic Locust properties (for example wait_time) should be picked up by a user's IDE (for example vscode) and type errors be picked up when checked with MyPy (http://mypy-lang.org/). |
Lets do this after 1.0. I tried some stuff, but it is harder than it seems and I dont want to delay 1.0 |
The API documentation should provide a good list of functions and methods that we would like to add type hinting for. |
… done). Removes NoClientWarningRaiser, because it was hard to type check and hasn't been relevant for a long time. Not really finished.
Now that we have updated to python 3.6 we can have sensible type hinting ("->" syntax for methods for example). We should add that.
The text was updated successfully, but these errors were encountered: