-
Notifications
You must be signed in to change notification settings - Fork 66
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
Revisit the reserved terms in gapic/utils/reserved_names.py #2015
Comments
It exists as a built-in constant: https://docs.python.org/3/library/constants.html#constants-added-by-the-site-module
|
I'm going to close this issue but please feel free to open a new issue with more information. |
This does not prevent it from being used as a field name. |
In the example from #2015 (comment)
We would be clobbering the built-in constant Nonetheless, I'll keep this open as a feature request so we can evaluate when we are considering the next breaking change. (Regardless of whether it can be done technically, it would be a breaking change to remove terms from the reserved words list. ) |
license
should not be a reserved field name
I've just noticed that the generated classes mangle the
license
field name:https://github.com/googleapis/python-aiplatform/blob/c56dd50310ecc42d6a3b0cd2f30db71e8cad0cf6/google/cloud/aiplatform_v1/types/content.py#L572
I think this is incorrect.
license
is not a Python reserved keyword and it can definitely be used as an attribute name.The text was updated successfully, but these errors were encountered: