-
Notifications
You must be signed in to change notification settings - Fork 58
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
Get google-cloud-datastore onto 2.x, somehow #1115
Comments
Narrowing to just google-cloud-datastore, since the rest are now on 2.x. Background in googleapis/google-cloud-python#10566 (comment). The more worrying part from that comment is:
|
Asked about that in googleapis/python-ndb#765 |
Community-contribute ndb fork that upgraded to datastore v2: https://github.com/jacobg/python-ndb/tree/datastore-v2 |
Official PR! googleapis/python-ndb#841 |
^ It's merged! Can't wait for the release. |
We use the ndb library with Cloud Datastore. It has a mandate to maintain Python 2.7 compatibility, so it has to stay on google-cloud-datastore 1.x, which in turn requires the 1.x versions of most other Python Google Cloud libraries, including google-auth, google-cloud-core, etc. Background in googleapis/python-ndb#733.
Those Google libraries are now all on 2.x or beyond, so the 1.x branches are degrading and no longer getting bug fixes, new features, or even fixes for security vulnerabilities like googleapis/python-ndb#733 (comment). That specific vulnerability doesn't apply to us, and they say they'll backport patches for any vulnerability that does, but still, it's an unfortunate position.
As downstream ndb users, what can we do about this? I'm not sure. Our ndb usage is pretty deeply entrenched in the code. We could migrate away, but that would be a significant undertaking. We could fork ndb and drop its Python 2.7 compatibility, but that's not something I want to do or maintain either.
Hrm.
The text was updated successfully, but these errors were encountered: