-
Notifications
You must be signed in to change notification settings - Fork 279
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
Addition of typing hints #970
Comments
Personally, I'm not against adding type hints. It definitely improves the documentation of the library, and makes it easier to work with in code editors. Although, after having updated a few codebases, I've yet to find any errors caused by incorrect types found using mypy (likely due to string test suites already in place). It seems a slightly strange requirement that any project dependency requires type checking - it is easy to ignore certain libraries with mypy. A few other thoughts:
I'll raise this discussion with the other maintainers. |
+1 for type hinting, and thanks for offering this contribution. We've done this with most of |
@eumetsat-usc-das - there's general agreement this would be a good addition to the project, so whenever you are ready, please submit an initial pull request for a file or module with type hints. See https://github.com/geopython/OWSLib/blob/master/owslib/ogcapi/features.py for a file where types are already in place. |
Dear OWSLib team, thanks a lot for the effort already put into the library. It has become part of what we suggest our users to use to interact with our OGC services.
Now we are considering leveraging the library in one of our projects but we have requirements in place that force us to use type checking using mypy. We can try and add the typing on our side and then prepare a pull request but I wanted to check with you before starting.
Is typing hints something you'd consider having (and then maintaining) in OWSLib?
The text was updated successfully, but these errors were encountered: