Ben Greiner

~~This is sound reasoning. I am not sure how meson and meson-python interfere with it, though. They seem to mangle some of the interpreter calls. Otherwise https://github.com/scipy/scipy/issues/20535#issuecomment-2067671013 would not have...

> What happened there is that I only applied the above rules partially before, so inside generate_f2pymod.py there was a python3 shebang and it was importing numpy.f2py But how did...

> The current version in `main` (before [gh-20612](https://github.com/scipy/scipy/pull/20612)) is explicitly running `py3 generate_f2pymod.py` How is that? From `main`: https://github.com/scipy/scipy/blob/d0ad5aa12fa4ef92a92ad55da23c472f1e2a7031/meson.build#L143 https://github.com/scipy/scipy/blob/d0ad5aa12fa4ef92a92ad55da23c472f1e2a7031/tools/generate_f2pymod.py#L1 https://mesonbuild.com/Reference-manual_functions.html#find_program > Meson will also autodetect scripts with a shebang...

I got it. The shebang was never `#!/usr/bin/python3`. Of course `#!/usr/bin/env python3` resolves to the interpreter of the build venv when not running non-isolated.

See #10. But it stopped working with Pytest 6.1

Any plans to fix this @bitprophet? All of your projects depending on pytest-relaxed currently fail with pytest 6.

That's what you get for using private functions

> To be fair, most of my projects tend to pin their deps in requirements.txt and if they don't, they should! But thanks for bringing this up. Pinning is not...

Hello everyone. Just for the record: No pytest 6 support also means no Python 3.10 support. So the only option from here on is @hroncok's proposed approach "patch pytest-relaxed out...

Note that most recent Flask and Werkzeug have changes incompatible with legacy oauth2client