feat: warn on pypi conda clobbering

[nichmor]

pixi will print a warning, if for some reason a conda package was mapped wrong
and we reinstall it again but as a pypi package.

Example:
using this custom mapping https://gist.githubusercontent.com/nichmor/6e0b8965e948536ed278f03aac31feb0/raw/635b0b849b88530a70889c4ef2f861bcb2ecc88e/wrong_mapping.json

and having both mdurl in dependencies and pypi-dependencies

user will see following warning

benchmarks:

[project]
name = "benchmark_hash"
version = "0.1.0"
description = "Add a short description here"
authors = ["nichmor <nmorkotilo@gmail.com>"]
channels = ["conda-forge"]
platforms = ["osx-arm64"]
conda-pypi-map = { "conda-forge" = "https://gist.githubusercontent.com/nichmor/9f2d0e5015f84c639394dfbf1c5d8cee/raw/79a2de856b835c81b2f2e78bb30933690bd7ed0b/wrong_jupterlab_mapping.json"}

[tasks]



[dependencies]
jupyterlab = "*"
detectron2 = "*"


[pypi-dependencies]
rich = "*"

with pixi.lock already present and warm cache

for ahash:

(default) graf@Nichitas-MacBook-Pro benchmark_hash % hyperfine '../../target/release/pixi install' --prepare 'rm -rf .pixi'
Benchmark 1: ../../target/release/pixi install
  Time (mean ± σ):     12.035 s ±  3.149 s    [User: 4.990 s, System: 21.933 s]
  Range (min … max):   10.001 s … 20.496 s    10 runs

for std::HashMap

(default) graf@Nichitas-MacBook-Pro benchmark_hash % hyperfine '../../target/release/pixi install' --prepare 'rm -rf .pixi'
Benchmark 1: ../../target/release/pixi install
  Time (mean ± σ):     10.753 s ±  0.611 s    [User: 4.972 s, System: 21.655 s]
  Range (min … max):    9.964 s … 11.517 s    10 runs

for std::HashMap with pre-allocated map:

(default) graf@Nichitas-MacBook-Pro benchmark_hash % hyperfine '../../target/release/pixi install' --prepare 'rm -rf .pixi'
Benchmark 1: ../../target/release/pixi install
  Time (mean ± σ):     11.482 s ±  2.112 s    [User: 4.955 s, System: 21.883 s]
  Range (min … max):    9.945 s … 16.980 s    10 runs

for ahash with pre-allocated map:

(default) graf@Nichitas-MacBook-Pro benchmark_hash % hyperfine '../../target/release/pixi install' --prepare 'rm -rf .pixi'
Benchmark 1: ../../target/release/pixi install
  Time (mean ± σ):     10.909 s ±  0.537 s    [User: 4.978 s, System: 21.892 s]
  Range (min … max):   10.065 s … 11.552 s    10 runs

so by using ahash and preallocating the map we have a win of 5% performance increase! ⬆️

without clobbering check:

 (default) graf@Nichitas-MacBook-Pro benchmark_hash % hyperfine 'pixi install' --prepare 'rm -rf .pixi'
Benchmark 1: pixi install
  Time (mean ± σ):     12.127 s ±  1.601 s    [User: 4.844 s, System: 23.112 s]
  Range (min … max):   10.413 s … 16.113 s    10 runs

with clobbering check:

(default) graf@Nichitas-MacBook-Pro benchmark_hash % hyperfine '../../target/release/pixi install' --prepare 'rm -rf .pixi'
Benchmark 1: ../../target/release/pixi install
  Time (mean ± σ):     12.241 s ±  2.749 s    [User: 5.005 s, System: 22.088 s]
  Range (min … max):   10.330 s … 19.690 s    10 runs

we add overhead of 0.100s

[ruben-arts]

Nice, LGTM

[nichmor]

it's missing a warning for the usecase when we first install pypi and later conda which don't remove the pypi one and we end up with two .dist-info in site-packages

[tdejager]

Conflict it seems!

[tdejager]

Nice that you've included benchmarks! Just wondering what the cost is of doing the check as opposed to not doing it :), for these large environments?

[nichmor]

Nice that you've included benchmarks! Just wondering what the cost is of doing the check as opposed to not doing it :), for these large environments?

added benchmark in the description!
but tl;dr - we add overhead of 0.100 seconds for large env

[ruben-arts]

Could you describe what it returns? And why this is important.

[nichmor]

done