-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
Update developer requirements.txt
so folks can contribute using more recent Pythons
#987
Comments
requirements.txt
so folks can contribute using more recent Pythons
The last time I tried updating I wish the Python community had more respect for other people's time, and would maintain backwards compatibility. |
@brandon-rhodes here is a working requirements.txt using all latest packages except for the commented ones. Passes all tests. No code changes required. But does make min python version 3.10 due to astropy. Dropping astropy from latest (6.1.2) down to (6.0.1) makes min python version 3.9 instead. Both options fix OP's initial issue of Only two problem packages:
Locking sphinx to v2.4.5 unfortunately makes it necessary to pin
|
Also, as a side note, there appears to be some sort of race condition in |
So I went down a rabbit hole of your CI pipeline and whatnot and ended up making a PR for my proposed updates 😅 ... You can see the action results here: https://github.com/EndlessDex/python-skyfield/actions/runs/10443120176 |
I tried to batch install packages from https://github.com/pepi-p/python-skyfield/blob/master/requirements.txt on windows 11, MINGW64, Python 3.12.2, but It failed.
The reason was the imp module on which astropy 3.2.2 depends.
Since the latest version of astropy is 6.1.2 and the version specified in requirements.txt is 3.2.2, it seems that the problem can be solved by depending on a newer version of astropy.
The text was updated successfully, but these errors were encountered: