konsti f4f67ebde0 Rebase: Uninstall existing non-editable versions when installing editable requirements bug (#682) ... Separate branch for rebasing #677 onto main because i don't trust the rebase enough to force push. Closes #677. --- If you install `black` from PyPI, then `-e ../black`, we need to uninstall the existing `black`. This sounds simple, but that in turn requires that we _know_ `-e ../black` maps to the package `black`, so that we can mark it for uninstallation in the install plan. This, in turn, means that we need to build editable dependencies prior to the install plan. This is just a bunch of reorganization to fix that specific bug (installing multiple versions of `black` if you run through the above workflow): we now run through the list of editables upfront, mark those that are already installed, build those that aren't, and then ensure that `InstallPlan` correctly removes those that need to be removed, etc. Closes #676. Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>		2023-12-18 09:28:14 +00:00
..
benchmarks	Move dev requirements up a directory (#512)	2023-11-29 10:11:31 +00:00
compare_with_pip	Fix compare_with_pip.py debug profile (#503)	2023-11-27 10:48:05 +00:00
editable-installs	Rebase: Uninstall existing non-editable versions when installing editable requirements bug (#682)	2023-12-18 09:28:14 +00:00
requirements	Add transformers extra requirements (#618)	2023-12-12 16:18:05 +00:00
resolve	change global allocator to jemalloc (and mimalloc on Windows) (#399)	2023-11-10 14:48:59 -05:00