chore(migration): Migrate code from googleapis/python-spanner-django into packages/django-google-spanner#16045
Merged
chalmerlowe merged 582 commits intomainfrom Mar 13, 2026
Conversation
Also while here, fixed a typo in a setting field for `DATABASES`
that used
DATABASE
instead of
NAME
for the name of the database.
Fixes #433
… INT64 columns' limitation refs #331
This reverts commit 7959874a6f09da750533d10f90d94320e082be76. fixes #444
fixes #227 Co-authored-by: Emmanuel T Odeke <emmanuel@orijtech.com>
This is the way release-please currently expects the version to be declared. https://github.com/googleapis/release-please/blob/4e0bf11b7f4217b5c6b8cd1aa9ea4db1bce06b89/src/updaters/python/setup-py.ts#L36
* chore: add renovate.json Co-authored-by: skuruppu <skuruppu@google.com>
* feat: add PyPI release support * fix: update package name Fixes #455 * deps: remove dependency on google-cloud * chore: added extra fields to setup.py * fix: single-source the version * fix: made setup.py consistent with client lib * fix: removed comment that no longer applies * fix: only support python version >=3.5 * add missing os import * add missing io import * fix README file extension * add missing pkg_resources import * fix import ordering Co-authored-by: larkee <larkee@users.noreply.github.com>
ohmayr
force-pushed
the
migration.python-spanner-django.migration.2026-03-06_19-24-38.migrate
branch
2 times, most recently
from
c80102c to
241ad70
Compare
ohmayr
force-pushed
the
migration.python-spanner-django.migration.2026-03-06_19-24-38.migrate
branch
from
241ad70 to
4b0b3b4
Compare
ohmayr
force-pushed
the
migration.python-spanner-django.migration.2026-03-06_19-24-38.migrate
branch
from
609e531 to
5edc4e5
Compare
ohmayr
force-pushed
the
migration.python-spanner-django.migration.2026-03-06_19-24-38.migrate
branch
from
34d8c78 to
9694001
Compare
ohmayr
force-pushed
the
migration.python-spanner-django.migration.2026-03-06_19-24-38.migrate
branch
from
9694001 to
379c65a
Compare
chalmerlowe
approved these changes
Mar 13, 2026
Contributor
chalmerlowe
left a comment
chalmerlowe
left a comment
There was a problem hiding this comment.
To the best of my knowledge, this looks reasonable.
I have made several comments that should be addressed.
There are several tests not yet passing.
It looks like the three failing tests were not passing in the old repo, either.
Approving this pending the completion of the comments.
Contributor
There was a problem hiding this comment.
Please delete the owl-bot-staging directory and contents.
Contributor
There was a problem hiding this comment.
We should be able to delete this and the 3.7 file. Leaving the lowest constraint file as 3.8. Move this content with any minor tweaks, as needed to the 3.8 file.
daniel-sanche
approved these changes
Mar 13, 2026
chalmerlowe
deleted the
migration.python-spanner-django.migration.2026-03-06_19-24-38.migrate
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See #10953.
This PR should be merged with a merge-commit, not a squash-commit, in order to preserve the git history.