Skip to content

Remove Julia v1.9 get_extension compatibility code #115

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

Merged
merged 4 commits into from
Jul 28, 2025

Conversation

ChrisRackauckas
Copy link
Member

Description

This PR removes the compatibility checks for isdefined(Base, :get_extension) since all SciML packages now require Julia v1.10+, where package extensions are built-in.

Changes

  • Removed unnecessary version checks in extension loading code
  • Simplified extension imports by removing conditional logic
  • Cleaned up obsolete compatibility code

Context

As identified in the SciML-wide analysis, all SciML packages have moved to requiring Julia v1.10+ as the minimum version. This makes the compatibility code for checking whether package extensions are available redundant.

The isdefined(Base, :get_extension) checks were used to support Julia v1.9 where extensions were loaded differently. Since we no longer support v1.9, this code can be safely removed.

Testing

  • Package tests pass locally
  • No changes to functionality, only removal of version checks

Since all SciML packages now require Julia v1.10+, we can remove the
compatibility checks for `isdefined(Base, :get_extension)` as package
extensions are available in all supported Julia versions.

This removes unnecessary version checks in extension loading code.
@gdalle
Copy link
Collaborator

gdalle commented Jul 27, 2025

Might as well bump the compat to 1.10 and remove the extension triggers from the deps? Otherwise I think the PR as written is breaking for Julia 1.6-1.9

@ChrisRackauckas
Copy link
Member Author

Ahh I thought we had already done that for all repos, thanks

@ChrisRackauckas
Copy link
Member Author

I'll get a script going to find any other stragglers.

This isn't triggering package tests though?

@gdalle
Copy link
Collaborator

gdalle commented Jul 27, 2025

Apparently we no longer test this on 1.6. Thats fine if we bump the compat (although we may want to run the tests on the last 1.6-friendly release one last time to be sure), but on the other hand we probably want to test on 1.11 and pre.

@ChrisRackauckas
Copy link
Member Author

This was a good test of the new downgrade 😅 sorry that rollout was a bit of a mess.

@thazhemadam can you help me get downgrade into the https://github.com/SciML/.github/tree/master/.github/workflows and roll that out globally? I think we should just make the normal CI have an option to error on depwarn and turn it off by default just to get the rest of the rollout around, as I'm surprised this repo isn't on the global CI yet. Also, I'm surprised not to see downstream on here, but now we should just wait for the rollout

@ChrisRackauckas ChrisRackauckas merged commit e7cf792 into main Jul 28, 2025
8 checks passed
@ChrisRackauckas ChrisRackauckas deleted the remove-get-extension-compat branch July 28, 2025 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants