-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
Compatibility with Numpy 2.0 and Python 3.12 #898
Comments
This work should also probably add Edit: And/or could switch to a pyproject.toml file to describe the build system. |
Oh you'll also need to drop usage of Lines 3 to 8 in dda493b
|
Also: brandon-rhodes/assay#15 is still an issue with Python 3.12 |
You can still use it when you use the setuptools backport. |
I just tested and was able to |
But you can't run your unit tests to be sure, can you? |
Indeed not! Alas. So many bytecode operations have been removed that the introspection magic in |
Wow. Completely unrelated to assert introspection, I just spent an hour wading into how exception traceback line numbers work in relation to context managers, because a change in Python 3.10 broke the (Where "broke" means, it's no longer showing the user which of their line numbers raised the faulty exception, but instead shows the line number of the That's enough of a foray to indicate that the changes to Python in the past couple of years have been substantial enough that I won't just casually be able to digest them in an hour or so — I'll need to think about priorities, and when I can spend maybe a few days working on either getting |
It's called pytest nowadays and I doubt that it takes several seconds to just import skyfield. The |
They are different beasts but probably can kill two birds with one stone. Actions offer Python 3.12 ("dev") and NumPy has nightly wheel for 2.0 in https://anaconda.org/scientific-python-nightly-wheels/numpy
The text was updated successfully, but these errors were encountered: