Creating environment with some pip arguments (which are not supported in requirements.txt) broken in 4.4+ #7290
Comments
mkobit
changed the title
|
Sorry for the breakage @mkobit. I think we should first specify what can be done and what is to be expected to happen with pip dependencies declared in an environment definition, which hopefully would happen as a result of #7248. AFAIK there is not much documentation to this respect. In the meantime, an extension that would hopefully get us back to support anything supported by pip in environment.yml files is outlined here: #6805 (comment). I think that is a similar but slightly more elegant and expressive solution than going back to interpret pip items as parameter lists. What do you think? Should I open that PR, which would include documentation? As per @kalefranz comments I feel it is likely that it would not be taken into consideration any time soon. |
I think some documentation would definitely be helpful until #7248 is done. Right now, we manually generate this YAML file based on some our use cases for creating a consistent environment across different OS/systems and build environments without baking in too much information (e.g. prefix/name). https://conda.io/docs/user-guide/tasks/manage-environments.html#create-env-file-manually is lacking a little bit of information about the format, so maybe saying something like "
The extension would help us in the meantime, but I could see it being a potential usability problem due to the different syntax and also switch on/off functionality. It is up to you guys if you think that it would improve the experience. It looks like it would be a band-aid until #7248 is implemented.
I definitely would appreciate a little bit of documentation, even if all it says is "only supports options from pip requirements file". Thanks for the quick follow up! |
|
I seem to be having similar issues, however this breaks my Here's an offending name: 'temp_environment3'
channels:
- conda-forge
dependencies:
- jupyter==1.0.0
- pip>=10.0.1
- python=3.6
- pip:
- requests-htmlSo even so much as Note that it does work correctly when I remove Install log: |
|
Bump on the above. Trying to install a package via Pip hosted in nexus. To get that into an |
|
To circumvent this issue (I want to use |
|
Hi there, thank you for your contribution to Conda! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment and we will gladly reopen the issue. In case this issue was originally about a project that is covered by the Anaconda issue tracker (e.g. Anaconda, Miniconda, packages built by Anaconda, Inc. like Anaconda Navigator etc), please reopen the issue there again. Thanks! |
|
I am trying to create an environment using a
from https://github.com/luxonis/depthai . The |
github-actions
bot
added
stale::recovered
Broken in #3969 , specifically ebd0f1a
First breakage is that the lines used to just be "appended" and supplied to
pip, so something likeworked. Now, it would produce something like
pip: error: --index-url option requires an argumentdue to the changes mentioned above. To work now, it is now required to be"--index-url https://corp.repo/pypi-internal"Second breakage is that arguments supported by
pipCLI are not supported by the requirements.txt file format, so arguments like:worked. With the changes mentioned above, other options like
--proxy,--trusted-host, etc. (from here) cannot be used.I'm submitting a...
Current Behavior
Installing of
pipfails due to unsupported optionsSteps to Reproduce
Expected Behavior
Using
piparguments that are supported bypipbut not in arequirements.txtshould continue to be successful.Environment Information
`conda info``conda config --show-sources``conda list --show-channel-urls`The text was updated successfully, but these errors were encountered: