Keith Smiley
Keith Smiley
yea good point we can wait a bit
>(as an aside, doesn't the uv.lock format and pylock.toml have capabilities that would prevent this problem?) At the very least there is no index fetching because `uv lock` encodes all...
sorry I was out for a bit. Here are the numbers with this setup https://github.com/modular/modular/blob/4092f7fa206d4331ce39e8f9584d641c92a919d1/bazel/common.MODULE.bazel#L125-L140 for reference this is not using experimental_index_url if that matters. Since I opened this issue...
once I use experimental_index_url the numbers are 338, and then 898
so really we have multiple hubs, not all are used on all platforms, but maybe those are still fetched sometimes. and in that case the numbers are unsurprisingly quite a...
I was able to reduce the number of deps in our project a bit so it's not as bad: before: ``` bazel query 'kind(py_library, deps(set(@pip_torch-2_7_0_deps//... @modular_nvidia_gpu_pip_deps//... @modular_amd_gpu_pip_deps//...)))' | grep :pkg...
can't test yet re https://github.com/bazel-contrib/rules_python/pull/3058#issuecomment-3045938881
`go install` is a bit easier for testing non-released versions and local builds
I think supporting only Swift 6 for this is fine. especially for swift demangle which only ever supported the specific point release you were at too. tbh it's pretty fragile...
thanks for doing the real work here, i'm pulling this + the CI update into https://github.com/MobileNativeFoundation/swift-index-store/pull/64