-
Notifications
You must be signed in to change notification settings - Fork 52
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
Numpy 2.0.0 problems #506
Comments
@pc494 I'm going to try to make the switch this week when I have the time! (Which I should) |
As I mentioned in #507:
|
Sorry @hakonanes I had completely forgotten the #507 discussion when I opened this. |
Nono, you opened this long before my post, I just reposted here to say that we're on it (: |
orix 0.13.1 is now available from PyPI, with numpy-quaternion as an optional dependency. But whaddayaknow, latest diffpy.structure is not compatible with NumPy 2.0: diffpy/diffpy.structure#68. So orix is still not compatible with NumPy 2.0. |
Reports from the diffpy.structure folks is that NumPy 2.0 compatibility will be addressed in a week's time. |
patch to 0.13.2 with a minimum version on |
After they release a new diffpy.structure release compatible with NumPy 2.0? Yes, that sounds like a plan. |
With #525 and an official release of diffpy.structure v3.2.2 (currently an RC out https://pypi.org/project/diffpy.structure/3.2.2rc0/), orix is compatible with NumPy 2.0 (without numpy-quaternion). |
Now that diffpy.structure v3.2.2 is available on PyPI (https://pypi.org/project/diffpy.structure/) and conda-forge (https://anaconda.org/conda-forge/diffpy.structure), we can release orix v0.13.1 which is fully compatible with NumPy v2. |
v0.13.2 I mean |
This has filtered down from upstream (see pyxem/pyxem#1099).
quaternion
on which we depend is currently (and may not for some time be) compatible withnumpy 2.0.0
.It's possible we could drag and drop a sister package in place (see discussion moble/quaternion#229) but I'm acutely aware this project is really short of dev resourcing.
The alternative is that we make ourselves
numpy 1.x
for now.The text was updated successfully, but these errors were encountered: