From b2618726bd91af921e1bd9a87601488d9f019e14 Mon Sep 17 00:00:00 2001 From: Dimitri Yatsenko Date: Wed, 20 May 2026 21:54:56 -0500 Subject: [PATCH] docs: extend datajoint.migrate timeline to 2.4 or 2.5 The module's docstring and runtime DeprecationWarning still pointed at the older "removed in 2.3 / while on 2.0" timeline. The module is still present at 2.2.x and 2.3 is shipping with it intact, so push the targets forward: - Removal target: 2.4 or 2.5 (was: 2.3) - Safe migration window: 2.3 or earlier (was: 2.0) Matches the warning text in the migration how-to in datajoint-docs. --- src/datajoint/migrate.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/datajoint/migrate.py b/src/datajoint/migrate.py index c2b71cc5f..1f174ccfd 100644 --- a/src/datajoint/migrate.py +++ b/src/datajoint/migrate.py @@ -7,8 +7,8 @@ .. note:: This module is provided temporarily to assist with migration from pre-2.0. - It will be deprecated in DataJoint 2.1 and removed in 2.3. - Complete your migrations while on DataJoint 2.0. + It is scheduled for removal in DataJoint 2.4 or 2.5. + Complete your migrations while on DataJoint 2.3 or earlier. Note on Terminology ------------------- @@ -32,8 +32,8 @@ # Show deprecation warning starting in 2.1 if Version(__version__) >= Version("2.1"): warnings.warn( - "datajoint.migrate is deprecated and will be removed in DataJoint 2.3. " - "Complete your schema migrations before upgrading.", + "datajoint.migrate is deprecated and is scheduled for removal in DataJoint 2.4 or 2.5. " + "Complete your schema migrations while on DataJoint 2.3 or earlier.", DeprecationWarning, stacklevel=2, )