Conversation
|
Hey @jamesfricker, this is already looking pretty good. Are you planning on continuing with this? |
Hey @tdejager, I'm currently not able to properly test the implementation where I was having this issue. I think what is here should fix it, but I'm not able to verify the build in my environment. @benmoss may be interested |
|
This works for me! I pushed a repro here: https://github.com/benmoss/pixi-tls-pypi-repro On pixi 0.49.0: on a PR build: |
|
@jamesfricker @tdejager It looks like this was ready for review 2 months ago, and now needs to have merge conflicts resolved. |
# Conflicts: # Cargo.lock # crates/pixi_core/src/lock_file/resolve/pypi.rs # crates/pixi_install_pypi/src/lib.rs # crates/pixi_uv_context/src/lib.rs
|
Oh sorry! It looks good to me, could we add some documentation for this though :)? There should be some global config options. |
- Add comprehensive documentation for tls-no-verify configuration option - Clarify that it affects both Conda and PyPI package operations - Document common use cases (Windows cert issues, corporate networks, internal registries) - Add configuration examples for global, local, and CLI usage - Enhance pypi-config section to clarify allow-insecure-host vs tls-no-verify - Add cross-references between related security options This addresses the documentation request in PR prefix-dev#4067 for global configuration options related to insecure TLS for PyPI operations.
|
Ok finished up the PR:
I'll wait for CI and then I'll merge. |
Closes #3359