-
Notifications
You must be signed in to change notification settings - Fork 184
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
[PROPOSAL] Merge .pyi types inline #536
Comments
Hi @dblock, I'm considering taking up this issue, just have a couple clarification questions:
|
Probably. We don't want to lose type information.
I don't have it. I tried to express "the problem" :) |
Thanks @dblock! I'd like to request assignment on this issue. |
Hi @dblock, I'm very sorry but can I be unassigned from this issue. I think I bit off more than I can chew with respect to the difficultly level of this fix. I'm going to pick another issue shortly that is more inline with my experience level with the repo. |
Much of this change needs to be done in the client generator, so we should get #543 in first. |
Current state: https://github.com/opensearch-project/opensearch-py/compare/main...dblock:merge-pyi?expand=1
|
I finished this in #563. If anyone has any good reasons not to do it, speak up! |
What/Why
What are you proposing?
We have the codebase littered with .pyi files. Is it time to merge types into Python code?
What problems are you trying to solve?
Updating types in multiple places is error prone.
What is the developer experience going to be?
No more .pyi files.
The text was updated successfully, but these errors were encountered: