Skip to content
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

Merged
merged 18 commits into from
Nov 26, 2024
Merged

v2.8.0 #68

merged 18 commits into from
Nov 26, 2024

Conversation

IAlibay
Copy link
Contributor

@IAlibay IAlibay commented Nov 22, 2024

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 22, 2024

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Nov 22, 2024

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 (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

For recipe/meta.yaml:

  • ℹ️ No valid build backend found for Python recipe for package mdanalysis using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.
  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.
  • ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

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.

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 22, 2024

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Nov 22, 2024

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 (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

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.

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 22, 2024

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

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.

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 22, 2024

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

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.

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 22, 2024

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

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.

Copy link
Contributor

@orbeckst orbeckst left a 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]
Copy link
Contributor

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?

Copy link
Contributor Author

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
Copy link
Contributor

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

Comment on lines +72 to +73
license: LGPL-3.0-or-later
license_family: LGPL
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

big step forward!

@orbeckst
Copy link
Contributor

Obviously, we shouldn't merge until all runners build correctly.

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 22, 2024

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.

@IAlibay IAlibay mentioned this pull request Nov 23, 2024
3 tasks
@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 25, 2024

@conda-forge-admin, please rerender

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 25, 2024

@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
Copy link
Contributor Author

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.

Copy link
Contributor

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

Copy link
Contributor Author

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.

@orbeckst
Copy link
Contributor

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.

Ok – I wouldn't know how to.

Is the issue that the kits depend on MDA and MDA depends on the kits?

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 25, 2024

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.

@orbeckst
Copy link
Contributor

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".

@orbeckst
Copy link
Contributor

Basically, the installation instructions would be

mamba install mdanalysis waterdynamics mdahole2 pathsimanalysis ## did not look up package names

instead of

mamba install mdanalysis

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 25, 2024

@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.

@orbeckst
Copy link
Contributor

You're in charge here — merge when ready. 🚀

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 25, 2024

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 25, 2024

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

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.

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 25, 2024

Looks like we're hitting this bug now.. conda/conda-build#5416

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 25, 2024

@conda-forge-admin, please rerender

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 26, 2024

Having to drop windows too...

@wshanks
Copy link

wshanks commented Nov 26, 2024

If you don't want to drop Windows, consider pinning conda-build until the issue is fixed:

conda/conda-build#5416 (comment)

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 26, 2024

@conda-forge-admin, please rerender

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 26, 2024

@wshanks you are my hero 🚀

@IAlibay IAlibay merged commit 6ab988d into conda-forge:main Nov 26, 2024
21 checks passed
@IAlibay IAlibay deleted the v2.8.0 branch November 26, 2024 19:42
@orbeckst
Copy link
Contributor

Thank you @IAlibay !!

@IAlibay
Copy link
Contributor Author

IAlibay commented Nov 26, 2024

Py13 support will have to be done elsewhere.. that might be a lot harder.

@orbeckst
Copy link
Contributor

Can you please add a footnote to the release blog post MDAnalysis/MDAnalysis.github.io#411 if there are some conda-forge packages missing?

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.

4 participants