-
Notifications
You must be signed in to change notification settings - Fork 150
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
custom pypi index #1094
Comments
Yes, supporting index options would be great. We would need to create the following struct to pass it to uv pub struct IndexLocations {
index: Option<IndexUrl>,
extra_index: Vec<IndexUrl>,
flat_index: Vec<FlatIndexLocation>,
no_index: bool,
} @tdejager , what would be your preference in terms of TOML configuration? a |
I think it can be placed directly under the |
does this related with #906? |
Also related: #588 |
also related to #1058 |
@olivier-lacroix @gzm55 @zen-xu @vigneshmanick Would it be fine to have this on the level of project similar to channels? |
I am fine with the project level definition, but it would also be good if it can be defined per package similar to how the conda dependencies are mentioned in the current documentation . [dependencies]
vtk-osmesa = { version = "~=9.3", channel = "conda-forge" } similar way for pypi should be [pypi-dependencies]
vtk-osmesa = { version = "~=9.3", extra-index-url= "wheels.vtk.org" } |
LGTM. both index-url and extra index-urls need to be set separately. |
That would be awesome I agree, I'm afraid that's technically more difficult because |
@tdejager project/ feature level settings mirroring the UV struct would be sufficient yes. |
Thank you @tdejager . Looking forward to this. ( its the primary blocker for uptake in my company. ) |
I'm now just thinking, all of these optional [project]
# other config
[pypi-options]
# When not used, will use uv default which is just pypi
primary-index = "pypi.org/simple"
extra-indices = ["foo", "bar"]
flat-indices = ["path/to/index"] @ruben-arts and others in-thread WDYT? |
this looks good and should cover my usecase |
That should be fine! It should be part of the |
@ruben-arts Ideally yes, how does this work for channels now because part of it also at a project level, but you can redefine per feature? Also the |
The platforms and channels are special cases where they are part of the Should we just use |
I'm fine with naming it |
Started on this: #1225 |
...( excitedly waits for the release )..... |
In the current version you can set them in the global config, they will be automatically added on init. But they are still required in the manifest file. This was chosen because otherwise the installs are not reproducible across systems. |
This feature should now be included in the latest release (with some basic ways of authenticating, through uv's keyring or netrc features). See documentation: https://pixi.sh/latest/reference/configuration/#the-pypi-options-table I will be closing this issue for now, feel free to make a new issue if there are any problems. |
Problem description
I use self-hosted pypi within the company, and
uv
can set the pypi index through environment variables.Since pixi uses uv to install pip-related packages, I hope this can be supported.
The text was updated successfully, but these errors were encountered: