-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
v2.8.0 #68
v2.8.0 #68
Conversation
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe/meta.yaml:
For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11980776031. Examine the logs at this URL for more detail. |
…nda-forge-pinning 2024.11.22.21.06.17
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12037303447. Examine the logs at this URL for more detail. |
…nda-forge-pinning 2024.11.22.21.06.17
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11980985833. Examine the logs at this URL for more detail. |
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11981087520. Examine the logs at this URL for more detail. |
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11981221367. Examine the logs at this URL for more detail. |
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.
- LICENSE was properly updated.
- numpy 2.0 migration looks good
LGTM, thanks for the update.
- matplotlib-base >=1.5.1 | ||
- seaborn # [not ppc64le] | ||
- netcdf4 >=1.0 | ||
- biopython >=1.80 | ||
- biopython >=1.80 # [not py>312] |
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.
Does biopython not work for 3.13 yet?
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.
Not as far as I can tell, their migrator is currently up.
- {{ pin_compatible('numpy', lower_bound='1.22.3') }} | ||
- numpy >=1.23.2 |
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.
nice — I read the npy 2.0 migrator notes
license: LGPL-3.0-or-later | ||
license_family: LGPL |
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.
big step forward!
Obviously, we shouldn't merge until all runners build correctly. |
Thanks @orbeckst - the main thing we need to do is make a new release of mdahole2, waterdynamics, and pathsimanalysis. The former is most important because it has a py<3.13 pin on. |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2024.11.25.08.53.39
@orbeckst we have a weird cycling dependency going on - I'm going to not add python 3.13 support for now and do it as a separate build. |
recipe/meta.yaml
Outdated
@@ -56,6 +56,9 @@ requirements: | |||
- pytng >=0.2.3 # [not ppc64le] | |||
- pyedr >=0.7.1 | |||
- mda-xdrlib | |||
- waterdynamics |
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.
We need to put a lower pin once we merge the LGPL PR & update the feedstock upstream.
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.
Waterdynamics is now LGPL MDAnalysis/waterdynamics#41
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.
Thanks, just waiting on the waterdynamics feedstock to update and we should be good.
Ok – I wouldn't know how to. Is the issue that the kits depend on MDA and MDA depends on the kits? |
Yup exactly, it's a problematic cyclic dependency - we might need to hurry up a v3.0 release. |
Then perhaps we drop the dependency on kits in MDAnalysis and tell users in an error message that they need to install the kit? I know that this is not how SemVer works but it would fix the problem and be in the spirit of "deprecations". |
Basically, the installation instructions would be
instead of
|
@orbeckst the issue is that the mdakits themselves need MDAnalysis... so it's just weird packaging wise. That being said - I think it works for now, at least the checks are passing. The issue was that py3.13 didn't work because it was attempting to first look for a compatible MDA version with py3.13 (for that mdakit) and then failing to resolve. Once 2.8.0, we can create a new build that should work. |
You're in charge here — merge when ready. 🚀 |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12020308304. Examine the logs at this URL for more detail. |
Looks like we're hitting this bug now.. conda/conda-build#5416 |
@conda-forge-admin, please rerender |
…onda-forge-pinning 2024.11.25.17.21.37
Having to drop windows too... |
If you don't want to drop Windows, consider pinning conda-build until the issue is fixed: |
@conda-forge-admin, please rerender |
…onda-forge-pinning 2024.11.26.07.33.56
@wshanks you are my hero 🚀 |
Thank you @IAlibay !! |
Py13 support will have to be done elsewhere.. that might be a lot harder. |
Can you please add a footnote to the release blog post MDAnalysis/MDAnalysis.github.io#411 if there are some conda-forge packages missing? |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)