-
Notifications
You must be signed in to change notification settings - Fork 44
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
[ENH - Add back support for using private pypi repository #543
Comments
Thanks for opening this, Just noting, I couldn't reproduce this on a quick test on the Quansight Nebari instance (which I believe runs v0.4.14) - but this needs another attempt to reproduce against the latest release and main, and/or investigation |
Thanks @pavithraes ! Perhaps I was mistaken - do you mind trying the pip list in the
|
Ah it may have been introduced in 0.4.15 - https://github.com/conda-incubator/conda-store/blob/v0.4.15/conda-store-server/conda_store_server/build.py#L272 |
@ClaytonAstrom yes this was a move towards an explicit:
Where before this we used @ClaytonAstrom this is definitely a feature that we want to support but conda-lock allows us cross platform lockfile and a more explicit solve. We will need to upstream a feature to conda-lock to start supporting this feature again. |
Thanks for the context, @costrouc! I'll (1) mark this as need documentation in the short-term, and (2) change this from a bug to a feature request so that we don't lose track of it. :) |
Describe the bug
Including pip options (such as --index-url, #294 ) don't seem to pass validation as described by the conda-lock dependency. While they suggest to add it to the global poetry config, it looks like their vendored version of poetry isn't compatible with how poetry handles that now - conda/conda-lock#393 (comment)
Expected behavior
The pip arguments such as
--index-url
should pass to pip without issueHow to Reproduce the problem?
--index-url
Output
conda-lock throws, it tries to validate
--index-url
as a package itselfVersions and dependencies used.
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: