How to handle compat when a dep is only used in an extension?

General Usage
1

I’m using Julia’s extensions system (with ext/ and [extensions] in Project.toml), and I ran into a small issue. I use a package like QuadGK only inside an extension (e.g. for DataInterpolationsExt), but Aqua marks it as a stale dep if I put it in [deps], since it’s not used in the main code.

If I leave it out of [deps], I can’t set a [compat] entry for it — which feels risky, since I still rely on it. I’m wondering how others handle this? I’d love to hear if there’s a clean way to keep Aqua happy and track versions of deps used only in extensions.

Sorry for the chatgpt message, didn’t know how to explain it clearly.
Thanks

2

If you use it inside an extension it should be in weakdeps?

3

does not seem to find it

[weakdeps]
DataInterpolations = "82cc6244-b520-54b8-b5a6-8a565e85f1d0"
QuadGK = "1fd47b50-473d-5c70-9696-f719f8f3bcdc"

[extensions]
BloodFlowTrixiDataInterpolationsExt = "DataInterpolations"

and I don’t wanna do this

[weakdeps]
DataInterpolations = "82cc6244-b520-54b8-b5a6-8a565e85f1d0"
QuadGK = "1fd47b50-473d-5c70-9696-f719f8f3bcdc"

[extensions]
BloodFlowTrixiDataInterpolationsExt = ["DataInterpolations","QuadGK"]

because it would force people to add both to access the ext. For now, I think I should have it as strong dep and just add a using statement to make Aqua happy

4

Indeed, that’s what I was suggesting. Otherwise it’s a useless main dep for your package and Aqua is right. You can probably ignore it manually within Aqua though.

5

Yes for now I just added it to the using statement at the beginning it made aqua happy and since it’s light I’m fine with it.
It would be nice if each extension could have its own project.toml even though it could lead to crazy dependencies

6

The problem is that, by definition, an extension is only loaded when its triggers are present in the environment. If that dependency is only useful in the extension, then it should be an extension trigger, and users should be asked to load it explicitly. As things stand, you’re just burdening the main package for nothing?

1 Like
7

Yes but its really understandable for the user that they need to add DataInterpolations to do what the extension does but not QuadGK, I’ve open a feature request to DataInterpolations to get the length of curve from it without relying on this so, if it is important enough for people, all this won’t be a problem anymore (in my case)

2 Likes
8

The danger of extensions loading their own dependencies is a runaway chain reaction. ABExt has using C, so that triggers BCExt, which has using D and that triggers CDExt, etc. While loading a package also loads a tree of implicit dependencies, there is an acceptance that each package needs what it needs. On the other hand, ABExt obviously does not need BCExt, D, or CDExt to work, and loading unnecessary modules goes against the intention of extensions. Extensions have restrictions for good reasons.

1 Like