You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are we making the conda-forge imdclient package a full dependency of the MDAnalysis cf package? I thought so but that shapes a bit how to write PR MDAnalysis/UserGuide#430
@orbeckst - I'm strongly voting no here. I'm not sure there's much room for discussion. As far as I can tell imdclientimports MDAnalysis. We can't have a package that depends on MDAnalysis also be a dependency of MDAnalysis, that's how we ended up breaking the MDA package and causing a ton of headaches with circular imports.
@orbeckst my suggestion is that we do a release with the cf package deps "as-is". In the meantime, if you (or another coredev) can start the discussion on voting for "what deps should we ship with", we can do another build release with more deps.
Edit: when I say "build release", I mean we just increment the 2.10 build on conda-forge, with more/less deps.
Reacted by Oliver Beckstein and Hugo MacDermott-Opeskin
The base library package is up on conda-forge, but we hit some issues with the py3.14 migration. This means that a) we don't have py3.14 out yet, b) MDAnalysisTests hasn't been released yet, c) if you own a package downstream of MDAnalysis, you might get a py3.14 migrator bot from conda-forge that doesn't actually work (because MDAnalysis didn't finish its migration).
Hooray!!! Thank you!Am 10/18/25 um 13:09 schrieb Irfan Alibay ***@***.***>:IAlibay left a comment (MDAnalysis/mdanalysis#5124)
Ok, manual migration went through, both MDAnalysis and MDAnalysisTests packages are up on conda-forge. Release is done.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>
Activity
orbeckst commentedon Oct 13, 2025
(I merged PR #5113 , which wasn't on the original list, an hour ago as it was complete.)
orbeckst commentedon Oct 14, 2025
No more PRs from my side to include urgently.
IAlibay commentedon Oct 15, 2025
Ok since no one else raised anything else, we will go ahead with the release.
orbeckst commentedon Oct 15, 2025
Are we making the conda-forge imdclient package a full dependency of the MDAnalysis cf package? I thought so but that shapes a bit how to write PR MDAnalysis/UserGuide#430
(For the pip package it's optional in extras.)
IAlibay commentedon Oct 15, 2025
@orbeckst - I'm strongly voting no here. I'm not sure there's much room for discussion. As far as I can tell
imdclientimports MDAnalysis. We can't have a package that depends on MDAnalysis also be a dependency of MDAnalysis, that's how we ended up breaking the MDA package and causing a ton of headaches with circular imports.orbeckst commentedon Oct 15, 2025
imdclient does not have MDAnalysis as a dependency (only for tests). It only depends on numpy.
IAlibay commentedon Oct 15, 2025
I see, thanks for the clarification. I still vote no - I don't want to add more work to this release.
IAlibay commentedon Oct 15, 2025
(I note, given it's not a hard dependency block - this is a coredev vote [unless it becomes a headache / too much work])
orbeckst commentedon Oct 15, 2025
Ok, I defer to you here.
We can revisit in the future (given that other file format packages such as gsd, h5py, pytng are bundled – https://github.com/conda-forge/mdanalysis-feedstock/blob/9f699f3281a3ab29b7594404e3c6c457b197d6df/recipe/meta.yaml#L36 ).
orbeckst commentedon Oct 15, 2025
Future discussion:
IAlibay commentedon Oct 15, 2025
@orbeckst my suggestion is that we do a release with the cf package deps "as-is". In the meantime, if you (or another coredev) can start the discussion on voting for "what deps should we ship with", we can do another build release with more deps.
Edit: when I say "build release", I mean we just increment the 2.10 build on conda-forge, with more/less deps.
orbeckst commentedon Oct 15, 2025
Totally agree!
orbeckst commentedon Oct 15, 2025
(sorry, wrong button, didn't mean to close)
IAlibay commentedon Oct 18, 2025
The base library package is up on conda-forge, but we hit some issues with the py3.14 migration. This means that a) we don't have py3.14 out yet, b) MDAnalysisTests hasn't been released yet, c) if you own a package downstream of MDAnalysis, you might get a py3.14 migrator bot from conda-forge that doesn't actually work (because MDAnalysis didn't finish its migration).
Working on a solution this evening.
IAlibay commentedon Oct 18, 2025
Ok, manual migration went through, both MDAnalysis and MDAnalysisTests packages are up on conda-forge. Release is done.
orbeckst commentedon Oct 19, 2025