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

Versions of requirements are too tightly fixed #120

Open
morcuended opened this issue Jun 19, 2024 · 1 comment
Open

Versions of requirements are too tightly fixed #120

morcuended opened this issue Jun 19, 2024 · 1 comment

Comments

@morcuended
Copy link
Collaborator

iop4/pyproject.toml

Lines 20 to 40 in 090cc97

"numpy==1.24.2",
"matplotlib==3.7.1",
"bokeh==3.2.2",
"scipy==1.10.1",
"astropy==5.2.2",
"astroquery",
"photutils==1.8.0",
"pandas",
"scikit-learn==1.2.2",
"scikit-image",
"coloredlogs",
"ipython",
"django==4.1.7",
"astrometry==4.1.2",
"multiprocess==0.70.14",
"pypandoc",
"termcolor",
"pyyaml<5.4",
"psutil",
]

In principle, there is no showstopper to run iop4 with the latest Python version 3.12 (3.13 coming already in a few months) other than some requirements above that need to be updated as well to make installation possible. I ran iop4 tests with Python 3.12 leaving dependency versions free (e.g. setting "matplotlib>=3.7.1" instead of "matplotlib==3.7.1"), and it worked.

Still to be thoroughly checked though. But something to keep in mind.

@juanep97
Copy link
Owner

I think we first should improve test coverage by a good deal, then progressively free dependencies, to make sure nothing inadvertently breaks. Patch versions are probably fine anyway, although I remember that some of them at least were to avoid some bug.

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

No branches or pull requests

2 participants