[issue22490] Using realpath for __PYVENV_LAUNCHER__ makes Homebrew installs fragile

[Guido van Rossum]

Guido van Rossum <guido at python.org> added the comment:

I would love to know how to repro the original bug so I can demonstrate this actually fixes it.

Here's what I think should be the repro:

/Library/Frameworks/Python.framework/Versions/3.8/bin/python3  -c 'import subprocess; p = subprocess.Popen([".mypy/venv/bin/python3","-m","mypy.dmypy","-h"]).communicate()'

The setup is that .mypy/venv is a virtualenv that has mypy.dmypy installed. This is what failed for the user who reported this.

Unfortunately this does not fail for me (with a framework build from master installed). Would I have to do the install via brew? (I would have to learn about locally testing modified brew recipes, I suppose.)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22490>
_______________________________________