-
Notifications
You must be signed in to change notification settings - Fork 59
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
Remove legacy extension api #1464
Remove legacy extension api #1464
Conversation
0103147
to
0f1f1d7
Compare
8e0a6b9
to
dab163d
Compare
dab163d
to
57e9ba5
Compare
57e9ba5
to
8529c69
Compare
8529c69
to
0ddbd1e
Compare
weldx downstream job failure for this PR looks like it should be fixed by weldx PR: BAMWelDX/weldx#863 |
Yes we will release a new version soon based on the new extension API which should fix the downstream job |
feel free to rerun the downstream welx test again now with weldx 0.6.5 @braingram |
0ddbd1e
to
c4b71e5
Compare
a2d1aaf
to
95ee7c0
Compare
48ab7a7
to
d58a895
Compare
WeldX downstream failure related to new version of pint: BAMWelDX/weldx#872 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -254,23 +252,6 @@ def extension_manager(self): | |||
self._extension_manager = get_cached_extension_manager(self._user_extensions + self._plugin_extensions) | |||
return self._extension_manager | |||
|
|||
@property |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Begone!
a few tests required updating as now several types are being converted by asdf-astropy instead of astropy.io.misc.asdf
for more information, see https://pre-commit.ci
5437d52
to
19dc360
Compare
FWIW: devdeps are failing on python 3.8 because gwcs has dropped python 3.8: spacetelescope/gwcs#451 |
This might have broken 2 of the astropy release branches: v5.2.x and v5.3.x astropy v6.0.dev seems compatible but that is not going to be released until the end of 2023. Any chances this can be reverted and then wait 6 months? It is the v5.3.x that I worry about. Example logs: |
p.s. I opened astropy/astropy#14795 |
I would prefer to find a solution that does not revert and delay these changes for 6 months. One option might be to install asdf-astropy and require it for building the docs on v5.3.x and v5.2.x (and update the documentation for the modeling example to describe that asdf-astropy is now required for saving astropy models to a file). Similar changes appear to have been included in astropy/astropy#14668 |
That would be too confusing for astropy users, as we have not removed deprecated code yet in those branches. I can always pin maxversion of asdf for those branches but I have a feeling that @nden won't like that. |
Also, what is the rush of removing code here so much so soon? |
I must be missing something. How would adding a dependency for building the docs be confusing to an astropy user? |
We are breaking the promise of requiring something that should not be required. |
Serializing an astropy model with asdf 3.0 requires asdf-astropy. Are you proposing that asdf continue to support |
Didn't y'all write a whole long-term support policy a few months ago? I thought downstream would have another year, which wouldn't be a problem for us by then because astropy 6.0 should come out in 6 months. |
It would be very easy for me to pin |
It was agreed that ASDF does not have the resources to support formal LTS releases. Would committing to supporting 2.15 for 6 months meet your needs? The currently released version of ASDF (2.15) should allow the doctest you linked to pass. However the run you linked installed the 3.0 development branch (main) of ASDF. This will continue to fail even if we can agree to support 2.15.
Is that the solution you prefer? |
If you cannot revert this, then that is what I must do. It is wrong to introduce breaking changes in v5.3.x after the freeze. We are already in RC. Thanks for your inputs! |
This PR removes the public api for the deprecated legacy extensions.
Internally, ASDF still uses this api for building and registering the
BuiltinExtension
so removal of the legacy extension methods and functions is not possible at this point.Some objects were made private to prevent their inclusion in the documentation (
AsdfType
andAsdfExtension
).The
asdf_extension
entry point is preserved but modified to only load theBuiltinExtension
. This modification means that many types previously converted byastropy.io.misc.asdf
are now converted byasdf-astropy
. This required updates to thetest_version_map_support
test to match the supported tags inasdf-astropy
(and to make this test aware of the new extensions).