Use pip install --no-deps to avoid overwiting packages from the conda environment

[bouweandela]

Description

Use pip install --no-deps to avoid overwiting packages from the conda environment

• Closes Use the --nodeps option when installing from PyPI? #2735
• Link to documentation:

---

Before you get started

• ☝ Create an issue to discuss what you are going to do

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

• 🛠 This pull request has a descriptive title
• 🛠 Documentation is available
• 🛠 Tests run successfully
• 🛠 The list of authors is up to date
• 🛠 All checks below this pull request were successful

---

To help with the number of pull requests:

• 🙏 We kindly ask you to review two other open pull requests in this repository

[bouweandela]

Tests are failing pip check with the message:

esmvalcore 2.13.0rc1 requires intake-esm, which is not installed.
dodgy 0.2.1 is not supported on this platform
pylint-flask 0.6 is not supported on this platform

@jlenh It looks like you may have forgotten to add intake-esm as a dependency on conda-forge for the ESMValCore v2.13.0rc1 release candidate

The other two packages are related to prospector/pylint, so I will try to solve #3739 before continuing with this pull request.

[jlenh]

Tests are failing pip check with the message:

esmvalcore 2.13.0rc1 requires intake-esm, which is not installed.
dodgy 0.2.1 is not supported on this platform
pylint-flask 0.6 is not supported on this platform

@jlenh It looks like you may have forgotten to add intake-esm as a dependency on conda-forge for the ESMValCore v2.13.0rc1 release candidate

The other two packages are related to prospector/pylint, so I will try to solve #3739 before continuing with this pull request.

I am preparing esmvalcore 2.13.0rc3, I will include it then if that's alright?

[bouweandela]

Yes, that would be great.

[valeriupredoi]

many thanks @jlenh - would you have a bit of time to pop the same flags in the GHAs? No worries, I can do that if it's too much hassle 🍺

[jlenh]

many thanks @jlenh - would you have a bit of time to pop the same flags in the GHAs? No worries, I can do that if it's too much hassle 🍺

Do you mean in these places? (to make sure I do not miss any)

ESMValTool/.github/workflows/create-condalock-file.yml

Line 64 in 6c500d7

run: pip install -e .[develop]

ESMValTool/.github/workflows/install-from-condalock-file.yml

Line 54 in 6c500d7

- run: pip install -e .[develop]

ESMValTool/.github/workflows/install-from-source.yml

Line 44 in 6c500d7

run: pip install -e .[develop] 2>&1 | tee source_install_linux_artifacts_python_${{ matrix.python-version }}/install.txt

ESMValTool/.github/workflows/run-tests-monitor.yml

Line 51 in 6c500d7

run: pip install -e .[develop] 2>&1 | tee test_linux_artifacts_python_${{ matrix.python-version }}/install.txt

ESMValTool/.github/workflows/run-tests-monitor.yml

Line 101 in 6c500d7

pip install -e .[develop] 2>&1

ESMValTool/.github/workflows/test-development.yml

Line 50 in 6c500d7

run: pip install -e .[develop] 2>&1 | tee develop_test_linux_artifacts_python_${{ matrix.python-version }}/install.txt

ESMValTool/.github/workflows/test-development.yml

Line 56 in 6c500d7

pip install -e .[develop]

ESMValTool/.github/workflows/test.yml

Line 48 in 6c500d7

run: pip install -e .[develop] 2>&1 | tee test_linux_artifacts_python_${{ matrix.python-version }}/install.txt

ESMValTool/.github/workflows/test.yml

Line 104 in 6c500d7

run: pip install -e .[develop] 2>&1 | tee test_osx_artifacts_python_${{ matrix.python-version }}/install.txt

[valeriupredoi]

@jlenh yessir, those there indeed 🍺

[valeriupredoi]

@jlenh @bouweandela this should be good to run on green too, now that Julien released rc4 (well, in a couple hous when conda forge records get updated)

[valeriupredoi]

@bouweandela I've merged and fixed the latest main into this - it looks like pip check is hitting the same issue as prospector hits at build on the feedstock, might not want to use pip check while we still pull in prospector 🍺

[valeriupredoi]

@bouweandela let's remove pip check and merge this now, I think it's better if we merged now and not waited for the complete removal of prospector

[bouweandela]

That would lead to us having a development environment with incompatible versions of software installed. Why the rush? This issue has been open for years

[valeriupredoi]

That would lead to us having a development environment with incompatible versions of software installed. Why the rush? This issue has been open for years

@jlenh will have to close one eye at the failed Monitor Test GHA when releasing, but OK - we'll make sure he don't complain 😁 The env is not broken per se, it's just missing a couple prospector components that we don't even need.