build: Remove transient directories after install to allow for rebuild

[matthewfeickert]

• Resolves Re-building from source during development #140
• Addresses part of Issue Add repository reset tools for developers #279
• Addresses part of Discussion How to rebuild the _ext.cpp when developing? #302

While doing multiple rebuilds it is advisable to also clean up the state of the Git submodules with git clean -f, removing the OUTPUT directory at src/fastjet/_fastjet_core/ and the top level build directory is sufficient to do local development rebuilds — i.e., the command python -m pip install --upgrade . can be run twice in a row without error.

[matthewfeickert]

This is ready for review. The CI build wheels jobs are broken in general given

fastjet/pyproject.toml

Lines 16 to 23 in f90dc72

	[tool.cibuildwheel.linux]
	before-all = [
	"yum update -y",
	"yum install -y mpfr-devel",
	"curl -L https://boostorg.jfrog.io/artifactory/main/release/1.84.0/source/boost_1_84_0.tar.bz2 -o boost_1_84_0.tar.bz2",
	"tar --bzip2 -xf boost_1_84_0.tar.bz2",
	"mv boost_1_84_0/boost /usr/include/boost",
	]

is hitting

Error: Command ['sh', '-c', 'yum update -y && yum install -y mpfr-devel && curl -L https://boostorg.jfrog.io/artifactory/main/release/1.84.0/source/boost_1_84_0.tar.bz2 -o boost_1_84_0.tar.bz2 && tar --bzip2 -xf boost_1_84_0.tar.bz2 && mv boost_1_84_0/boost /usr/include/boost'] failed with code 1.

but that can get fixed in another PR.

For this PR what matters is that I can now do

python -m pip install --upgrade --verbose . && python -m pip install --upgrade --verbose .

without erroring out.

[matthewfeickert]

cc @kawaho

[jpivarski]

I don't know if this is everything that's needed, but directories named "build" and "_*" are the sorts of things that should be cleaned up.

You should also get a review from someone who is more qualified to verify it.

[matthewfeickert]

@rkansal47 unless you have any thoughts here I'm going to merge this at the end of the day to make @kawaho's development experience easier on PR #312.

[rkansal47]

Thanks @matthewfeickert! Does this resolve #140? (Sorry, I'm not able to test the re-build myself currently.)

EDIT: Looks like it should, so LGTM!

[matthewfeickert]

Ah good catch @rkansal47! I hadn't even noticed Issue #140 while thinking on Issue #279.