Shantanu 5a07923eb4 Use Metadata10 to parse PKG-INFO of legacy editable (#3450) ... It turns out setuptools often uses Metadata-Version 2.1 in their PKG-INFO: 4e766834d7/setuptools/dist.py (L64) `Metadata23` requires Metadata-Version of at least 2.2. This means that uv doesn't actually recognise legacy editable installations from the most common way you'd actually get legacy editable installations (works great for most legacy editables I make at work though!) Anyway, over here we only need the version and don't care about anything else. Rather than make a `Metadata21`, I just add a version field to `Metadata10`. The one slightly tricky thing is that only Metadata-Version 1.2 and greater guarantee that the [version number is PEP 440 compatible](https://peps.python.org/pep-0345/#version), so I store the version in `Metadata10` as a `String` and only parse to `Version` at time of use. Also did you know that back in 2004, paramiko had a pokemon based versioning system?		2024-05-08 10:58:18 +02:00
..
base_url.rs	Use scheme parsing to determine absolute vs. relative URLs (#2904)	2024-04-08 17:04:27 -04:00
direct_url.rs	Add basic `tool.uv.sources` support (#3263)	2024-05-03 21:10:50 +00:00
lenient_requirement.rs	Make `Requirement` generic over url type (#3253)	2024-05-07 16:45:49 +02:00
lib.rs	Use simpler pip-like `Scheme` for install paths (#2173)	2024-03-04 15:50:13 -05:00
metadata.rs	Use Metadata10 to parse PKG-INFO of legacy editable (#3450)	2024-05-08 10:58:18 +02:00
scheme.rs	Query interpreter to determine correct `virtualenv` paths (#2188)	2024-03-05 16:13:24 -05:00
simple_json.rs	Remove `Into::into` (#3337)	2024-05-02 10:26:42 +00:00