radicamc / exoTEDRF

Tools for end-to-end reduction of JWST exoplanet observations
BSD 3-Clause "New" or "Revised" License
0 stars 1 forks source link

Installation fails when following instructions #20

Open iancrossfield opened 3 weeks ago

iancrossfield commented 3 weeks ago

In a clean new conda environment, installation fails using the instructions on the docs page. The final error after pip install jmespath and then pip install exotedrf is

ERROR: Cannot install exotedrf==1.4.0 and exotedrf==2.0.0 because these package versions have conflicting dependencies.

The conflict is caused by: exotedrf 2.0.0 depends on ray exotedrf 1.4.0 depends on ray ... but no guidance is provided on what ray refers to.

The full error trace is below.

(exotedrf) user@computer:/directory/$ pip install jmespath Collecting jmespath Using cached jmespath-1.0.1-py3-none-any.whl.metadata (7.6 kB) Using cached jmespath-1.0.1-py3-none-any.whl (20 kB) Installing collected packages: jmespath Successfully installed jmespath-1.0.1

(exotedrf) user@computer:/directory/$ pip install exotedrf Collecting exotedrf Downloading exotedrf-2.0.0.tar.gz (76 kB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Collecting applesoss==2.1.0 (from exotedrf) Downloading applesoss-2.1.0.tar.gz (25 kB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Collecting astropy (from exotedrf) Downloading astropy-6.1.4-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (10 kB) Collecting astroquery (from exotedrf) Using cached astroquery-0.4.7-py3-none-any.whl.metadata (7.2 kB) Collecting bottleneck (from exotedrf) Downloading Bottleneck-1.4.2-cp313-cp313-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (7.7 kB) Collecting corner (from exotedrf) Using cached corner-2.2.2-py3-none-any.whl.metadata (2.2 kB) Collecting jwst==1.12.5 (from exotedrf) Downloading jwst-1.12.5.tar.gz (18.5 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 18.5/18.5 MB 17.5 MB/s eta 0:00:00 Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Collecting matplotlib (from exotedrf) Downloading matplotlib-3.9.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (11 kB) Collecting more-itertools (from exotedrf) Using cached more_itertools-10.5.0-py3-none-any.whl.metadata (36 kB) Collecting numpy (from exotedrf) Using cached numpy-2.1.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (60 kB) Collecting pandas (from exotedrf) Downloading pandas-2.2.3-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (89 kB) INFO: pip is looking at multiple versions of exotedrf to determine which version is compatible with other requirements. This could take a while. Collecting exotedrf Downloading exotedrf-1.4.0.tar.gz (69 kB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Collecting applesoss==2.0.2 (from exotedrf) Downloading applesoss-2.0.2.tar.gz (25 kB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done ERROR: Cannot install exotedrf==1.4.0 and exotedrf==2.0.0 because these package versions have conflicting dependencies.

The conflict is caused by: exotedrf 2.0.0 depends on ray exotedrf 1.4.0 depends on ray

To fix this you could try to:

  1. loosen the range of package versions you've specified
  2. remove package versions to allow pip to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

radicamc commented 3 weeks ago

Hi Ian, I'm not able to reproduce this error, either on Mac or Linux. The installation proceeds without issue in a fresh conda env in both cases.

iancrossfield commented 3 weeks ago

I'm really in trouble then, I guess! Thanks -- we'll continue to troubleshoot.