pytest-shutil: Replace deprecated imp module

[mgorny]

Replace the use of the deprecated imp module with `importlib.util', as the former has been removed from Python 3.12.

[wpbonelli]

If no further maintenance is planned (cf #214, #218) I'm wondering about re-homing pytest-virtualenv as a standalone project.

• Would anyone be willing to contribute? @mgorny @JamesWrigley @kloczek @mayeut @abravalheri
• Is ownership transfer an option? I would not like to take on this whole repo but may consider if others will help.
• Is pytest-venv an alternative? It also seems unmaintained, maybe @mmerickel has insight
• If a new project is needed, should it continue to use virtualenv or builtin venv?
• Is PyPI ownership transfer possible, either pytest-virtualenv or pytest-venv? If not, what to name a new plugin?

[mmerickel]

Is pytest-venv an alternative? It also seems unmaintained, maybe @mmerickel has insight

pytest-venv is not unmaintained, it's just going at the speed of free... :-) But yes, I'm not looking to change the scope of the library much past what it is right now. I did just release 0.3 with several improvements including Python 3.12 support. I'm not clear why pytest-venv is being pinged on this issue about pytest-shutil - I do not use pytest-shutil - but regardless hopefully this serves as my insight!

If a new project is needed, should it continue to use virtualenv or builtin venv?

Well pytest-venv uses virtualenv so that it can create virtualenvs with different versions of Python if desired. venv is limited to the interpreter executing the command. I do not see the problem with continuing to depend on virtualenv to create virtualenvs - it's a great library with more features than the builtin venv.

[jonbannister]

Looks sensible to me, thank you for your contribution. Apologies for the long wait!

[mgorny]

Thanks!