You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This causes problems with recipes that depend on inquirer and use pip check to verify that dependencies are correct. One example can be found here, where I tried to fix the recipe for chalice, but it only worked after removing the pip check command.
$ conda env create -n inquirer-test
$ conda install -c conda-forge inquirer
$ pip check
inquirer 2.7.0 has requirement blessed==1.17.6, but you have blessed 1.18.0.
In my opinion, the root cause is that inquirer, being a library, should be more flexible when pinning dependencies. Nevertheless, the conda package should use the same dependencies.
I tried to update the recipe to use the same versions as in setup.py, but I found that despite blessed=1.17.6 and python-editor=1.0.4 are available in conda-forge, it turns out that readchar=2.0.1 is not. Looking at readchar's conda recipe I see that version is already set to 3.0.4 and I don't know if it's possible to create a PR that builds and old version (2.0.1 in this case). What would be the best way to proceed in this case?
jcollado
changed the title
conda package doesn't honor dependency pinning in setup.py
conda package doesn't honor dependency pinning in requirements.txt
May 6, 2021
This causes problems with recipes that depend on inquirer and use
pip check
to verify that dependencies are correct. One example can be found here, where I tried to fix the recipe forchalice
, but it only worked after removing thepip check
command.Issue: inquirer conda package doesn't honor dependency pinning in inquirer's
requirements.txt
file.Steps to reproduce problem:
In my opinion, the root cause is that inquirer, being a library, should be more flexible when pinning dependencies. Nevertheless, the conda package should use the same dependencies.
I tried to update the recipe to use the same versions as in
setup.py
, but I found that despiteblessed=1.17.6
andpython-editor=1.0.4
are available inconda-forge
, it turns out thatreadchar=2.0.1
is not. Looking atreadchar
's conda recipe I see that version is already set to3.0.4
and I don't know if it's possible to create a PR that builds and old version (2.0.1
in this case). What would be the best way to proceed in this case?Environment (
conda list
):Details about
conda
and system (conda info
):The text was updated successfully, but these errors were encountered: