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

Unpin parmed imports once parmed supports numpy 2.0 #4625

Open
IAlibay opened this issue Jun 22, 2024 · 1 comment · May be fixed by #4883
Open

Unpin parmed imports once parmed supports numpy 2.0 #4625

IAlibay opened this issue Jun 22, 2024 · 1 comment · May be fixed by #4883

Comments

@IAlibay
Copy link
Member

IAlibay commented Jun 22, 2024

Related to #4624

WIth #4620 we prevent importing parmed if we have numpy 2.0 due to compatibility issues.

Once parmed supports numpy 2.0, we should go ahead and remove these import skips.

@tclick
Copy link

tclick commented Dec 5, 2024

I believe that ParmEd 4.3.0 supports numpy 2.0+.

@IAlibay IAlibay linked a pull request Jan 7, 2025 that will close this issue
5 tasks
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 a pull request may close this issue.

2 participants