Skip to content

Conversation

@diegorusso
Copy link
Contributor

This is used in compile.py: compile_all installs pyperformance for every version it compiles. If the main pyperformance is installed in editable mode, this should be propagated down.
The mechamism to do that was broken because was checking the presence of setup.py, now long gone.

This is used in compile.py: compile_all installs pyperformance for every version it compiles. If the main pyperformance is installed in editable mode, this should be propagated down. The mechamism to do that was broken because was checking the presence of setup.py, now long gone.
Copy link
Contributor

@mdboom mdboom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but someone who has used it in this mode more than I have should probably also weigh in ... (@ericsnowcurrently, @vstinner...?)

@ericsnowcurrently
Copy link
Member

I don't recall enough about this to be useful. I'm sure Diego's fix is okay.

Copy link
Member

@ericsnowcurrently ericsnowcurrently left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mdboom mdboom merged commit a7585a1 into python:main Nov 20, 2024
13 checks passed
@diegorusso
Copy link
Contributor Author

diegorusso commented Nov 21, 2024

I don't recall enough about this to be useful. I'm sure Diego's fix is okay.

Yes, this is one of the thing that is useful only if you use a specific feature of the tool. @mdboom keeps saying that they don't use the compile_all at all, maybe it's time for me to move away from it.

Thanks for approving.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants