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
It appears (juding by strace output) that uv doesn't currently support reading pip's config files (e.g. /etc/xdg/pip/pip.conf). The feature I'm after specifically is already described in #1474 (support for the cert entry in the config file/via a cmdline flag) but I'm curious about the general stance the uv takes with reading pip's config files, and other potential users might be interested too.
Thanks a lot in advance!
The text was updated successfully, but these errors were encountered:
I'd prefer not to read configuration files designed for other tools. Like, we should support a configuration file and configuration format, but (similar to in Ruff), I'd prefer if it's our own format, etc. Otherwise, we have to figure out how to support reading those files across multiple versions of the target tool, and support any changes they make to the format in the future.
I'm not sure if it makes sense to document this yet as we're still establishing our formal stance around configuration files. I appreciate the offer though!
It appears (juding by
strace
output) thatuv
doesn't currently support reading pip's config files (e.g./etc/xdg/pip/pip.conf
). The feature I'm after specifically is already described in #1474 (support for thecert
entry in the config file/via a cmdline flag) but I'm curious about the general stance theuv
takes with reading pip's config files, and other potential users might be interested too.Thanks a lot in advance!
The text was updated successfully, but these errors were encountered: