Upgrade py-spy to 0.4.0 for py312 support

[alanwguo]

Why are these changes needed?

py-spy 0.4.0 has support for python 3.12.

Related issue number

Fixes #47388

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[can-anyscale]

oh, you can upgrade this in python/requirements.txt files i think

[can-anyscale]

you can copy the generated content for this PR here https://ray-ci-artifact-pr-public.s3.amazonaws.com/bc9fbdaa9cc5d971bca51db672e7692b91dc316a/tmp/artifacts/requirements_compiled.txt

[aslonnie]

this constraint file is used in py39 test environments, and I think this can lead to failures. I think we need to have separate requirement constraint files for different python versions in the long run. in the short run, maybe py-spy can be treated as a special case.

[aslonnie]

• the changes in python/setup.py and python/requirements.txt files are okay
• the constraint file update probably has issues.

how is py-spy being tested, and are they tested on different python versions?

[alanwguo]

In my manual testing, the wheels still seem to have v0.3.14. Not sure what I need to do differently here.

There are automated tests in test_reporter.py which runs the test_get_task_traceback_running_task test.
I don't know the matrix of environments (if any) it runs on.

[aslonnie]

In my manual testing, the wheels still seem to have v0.3.14. Not sure what I need to do differently here.

could you tell me how you did the manual testing?

[alanwguo]

could you tell me how you did the manual testing?

I downloaded the wheel and launched a Anyscale workspace with that wheel installed.
specifically, I uploaded the wheel to S3 and used Anyscale container images to install the wheel from S3.

[richardliaw]

(looks good from my side for setup.py)

[can-anyscale]

you can copy the generated content for this PR here https://ray-ci-artifact-pr-public.s3.amazonaws.com/bc9fbdaa9cc5d971bca51db672e7692b91dc316a/tmp/artifacts/requirements_compiled.txt

[alanwguo]

do we currently run all tests on all python versions? Is there a way to add configure a test file to run on python 3.12?
the test_reporter.py file.

[can-anyscale]

@alanwguo you can add the continuous-build tag into the PR, update branch again to kick off tests and it will run python 3.12 tests

[can-anyscale]

https://github.com/ray-project/ray/blob/master/.buildkite/core.rayci.yml#L62

[aslonnie]

so we just upgrade py-spy to 0.4.0, like for images of all python versions now?

[alanwguo]

I think this is reasonable behavior:
For our images, we use 0.4.0 out of the box.

For users installing ray themselves, we won't enforce 0.4.0 unless python 3.12 is used.

[aslonnie]

nice!

wonder why we did not upgrade py-spy earlier.. like was there something blocking us to do so? seems like a simple change based on this PR..

[alanwguo]

Just wasn't aware of 0.4.0's release. Which was released this november. I just saw someone comment that 0.4.0 had python 3.12 support so I updated after seeing that.