This is, as far as I'm aware, the "correct" way to handle the new world of isolated builds, dev dependencies, and pep517.
As an example, if you have your angr-dev with a bunch of repos with maybe-uncommitted changes and you want to distribute this, you can run ./admin/build_dev_wheels.sh and it will produce a folder named build which contains wheels for each of the core angr repos. You can then distribute this folder, and then pip install angr==9.2.5.dev0 --find-links=./build will work.
This is, as far as I'm aware, the "correct" way to handle the new world of isolated builds, dev dependencies, and pep517.
As an example, if you have your angr-dev with a bunch of repos with maybe-uncommitted changes and you want to distribute this, you can run
./admin/build_dev_wheels.shand it will produce a folder namedbuildwhich contains wheels for each of the core angr repos. You can then distribute this folder, and thenpip install angr==9.2.5.dev0 --find-links=./buildwill work.