gh-108303: Move all inspect test files to test_inspect/

[sobolevn]

This PR also moves ready_to_import helper to test/support/import_helper, because test_inspect was importing test_import, which is not good at all.

• Issue: Move test files into test subdirectories #108303

[sobolevn]

Looks like there's one more hidden dependency: in test.test_tokenize.TestRoundtrip.test_random_files

[vstinner]

Can you please try with a first PR to move ready_to_import() to test.support?

[vstinner]

LGTM.

[vstinner]

@serhiy-storchaka: It would be nice if we could magically generate such function, instead of having to duplicate the same 4 lines in each test_xxx/ test package. Do you think that it would be possible?

[vstinner]

This change is LGTM, but I would to wait until #109626 is backported to 3.11. If the backport queue is too big, it becomes really complicated to handle it :-(

[sobolevn]

I've solved conflicts, it should be now good to go, since all backports are done.
Thanks a lot, @vstinner, for your help!

[vstinner]

Before:

$ ./python -m test test_inspect
...
Total duration: 1.4 sec
Total tests: run=287
Total test files: run=1/1

After:

$ ./python -m test test_inspect
...
Total duration: 1.3 sec
Total tests: run=287
Total test files: run=1/1

Same number of tests: good. And tests pass :-)

[miss-islington]

Thanks @sobolevn for the PR, and @vstinner for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12.
🐍🍒⛏🤖

[miss-islington]

Sorry, @sobolevn and @vstinner, I could not cleanly backport this to 3.12 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 732532b0af9d1b5c7ae4932526c8d20d86c15507 3.12

[miss-islington]

Sorry, @sobolevn and @vstinner, I could not cleanly backport this to 3.11 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 732532b0af9d1b5c7ae4932526c8d20d86c15507 3.11

[vstinner]

@sobolevn: Thanks. I merged your PR. But the thing couldn't be backported automatically. Can you please try to backport the change manually to 3.12?

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x SLES 3.x has failed when building commit 732532b.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/540/builds/6819) and take a look at the build logs.
4. Check if the failure is related to this commit (732532b) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/all/#builders/540/builds/6819

Failed tests:

• test.test_concurrent_futures.test_shutdown

Failed subtests:

• test_interpreter_shutdown - test.test_concurrent_futures.test_shutdown.ProcessPoolForkProcessPoolShutdownTest.test_interpreter_shutdown

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
File "/home/dje/cpython-buildarea/3.x.edelsohn-sles-z/build/Lib/test/test_concurrent_futures/test_shutdown.py", line 50, in test_interpreter_shutdownself.assertEqual(out.strip(), b"apple")
AssertionError: b'' != b'apple'

[sobolevn]

Working on it.

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot PPC64LE RHEL7 3.x has failed when building commit 732532b.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/446/builds/4013) and take a look at the build logs.
4. Check if the failure is related to this commit (732532b) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/all/#builders/446/builds/4013

Failed tests:

• test.test_multiprocessing_fork.test_processes

Summary of the results of the build (if available):

==

Click to see traceback logs

remote: Enumerating objects: 12, done. remote: Counting objects: 9% (1/11) remote: Counting objects: 18% (2/11) remote: Counting objects: 27% (3/11) remote: Counting objects: 36% (4/11) remote: Counting objects: 45% (5/11) remote: Counting objects: 54% (6/11) remote: Counting objects: 63% (7/11) remote: Counting objects: 72% (8/11) remote: Counting objects: 81% (9/11) remote: Counting objects: 90% (10/11) remote: Counting objects: 100% (11/11) remote: Counting objects: 100% (11/11), done. remote: Compressing objects: 11% (1/9) remote: Compressing objects: 22% (2/9) remote: Compressing objects: 33% (3/9) remote: Compressing objects: 44% (4/9) remote: Compressing objects: 55% (5/9) remote: Compressing objects: 66% (6/9) remote: Compressing objects: 77% (7/9) remote: Compressing objects: 88% (8/9) remote: Compressing objects: 100% (9/9) remote: Compressing objects: 100% (9/9), done. remote: Total 12 (delta 2), reused 7 (delta 2), pack-reused 1 
From https://github.com/python/cpython
* branch main -> FETCH_HEAD
Note: checking out '732532b0af9d1b5c7ae4932526c8d20d86c15507'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at 732532b... gh-108303: Move all inspect test files to `test_inspect/` (#109607)
Switched to and reset branch 'main'
make: *** [Makefile:2014: buildbottest] Error 5

[bedevere-app]

GH-110732 is a backport of this pull request to the 3.12 branch.

[bedevere-app]

GH-111543 is a backport of this pull request to the 3.11 branch.