docs: extend datajoint.migrate timeline to 2.4 or 2.5#176
Merged
Conversation
The original warning said migrate would be deprecated in 2.1 and removed in 2.2, but the module is still present at 2.2.x and 2.3 is shipping with it intact. Update the timeline to match the current plan: - Removal target: 2.4 or 2.5 (was: 2.2) - Safe migration window: 2.3 or earlier (was: 2.0) A matching docstring update goes to datajoint-python/src/datajoint/ migrate.py in a separate PR.
2 tasks
MilagrosMarin
approved these changes
May 21, 2026
Collaborator
MilagrosMarin
left a comment
MilagrosMarin
left a comment
There was a problem hiding this comment.
Thanks @dimitri-yatsenko! Verified datajoint.migrate is still present on master at v2.2.2 and the paired upstream PR datajoint-python#1456 will land the docstring + runtime warning update in lockstep. Softer "2.4 or 2.5" framing reads well.
Approving.
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
2 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.
Summary
The "Temporary module" warning at the top of Migrate to DataJoint 2.0 was authored before the timeline slipped. It said the
datajoint.migratemodule would be deprecated in 2.1 and removed in 2.2, but the module is still present on master at 2.2.x and 2.3 is about to ship with it intact.Update to the current plan:
A matching docstring update for
datajoint-python/src/datajoint/migrate.py(which currently says "deprecated in 2.1 and removed in 2.3. Complete your migrations while on 2.0.") is in a separate PR — keeping the source and docs in lockstep.Test plan
/how-to/migrate-to-v20/reflects the new timeline