How can I change the Framework path my Python file is referring?

Usual spot for establishing PATH for zsh on macOS would be in .zprofile

The following is a pruned-down version of a local .zprofile login:

export PATH="$PWD:$HOME/bin:/usr/local/bin:${PATH}"
export PATH="/Library/Frameworks/Python.framework/Versions/3.9/bin:${PATH}"
export MANPATH="/usr/share/man:/usr/local/share/man"
export EDITOR="/usr/bin/vim"

You’ll need to switch to and use the local Python 2 path in that.

Once you have .zprofile updated, close the terminal window and re-open it.

To then see the translation of PATH:

echo $PATH

That third-party posix_spawn module was last updated in 2015 via PyPy, and for some unknown reason, is attempting to directly access the Python binary within the Python bundle in that now outdated System Python 2.7 framework location. Odd it would do that when the same binary would have been located by Apple in /usr/bin/python at the time this code was developed.

You won't fix this outdated module hardcoding issue by reinstalling Python 2.7.18 from Python.org, or by changing any PATH statement in ~/.zshrc or ~/.zprofile files. The inclusion of the posix_spawn module breaks this third-party application you are attempting to use, and unless the vendor has replaced that posix_spawn module with newer code to workaround this issue. you are very likely done with this app on Monterey.

VikingOSX wrote:

That third-party posix_spawn module was last updated in 2015 via PyPy, and for some unknown reason, is attempting to directly access the Python binary within the Python bundle in that now outdated System Python 2.7 framework location. Odd it would do that when the same binary would have been located by Apple in /usr/bin/python at the time this code was developed.

You won't fix this outdated module hardcoding issue by reinstalling Python 2.7.18 from Python.org, or by changing any PATH statement in ~/.zshrc or ~/.zprofile files. The inclusion of the posix_spawn module breaks this third-party application you are attempting to use, and unless the vendor has replaced that posix_spawn module with newer code to workaround this issue. you are very likely done with this app on Monterey.

Two options exist there then: add a link at the location (easiest), or xxd hexdump the app or module performing the posix_spawn, find and alter the string, and xxd hexdump it back to working (not particularly difficult, probably requires re-signing or overriding signing).

I have looked at the source code for posix_spawn since my earlier post and there is no explicit dependency on the path in that source as reported by the OP. This module depends on another third-party module, and something else in that other module, or the third-party application itself must be triggering that Python 2.7 path issue.

Wouldn’t expect the string in the posix_spawn. It’s the posix_spawn caller that usually specifies that string. It’s the caller that’d be the target for the patch too, if not using a link to the Python giblets as a workaround.

catherine.deangelis wrote:

That's what I've determined. I just ended up downgrading my system to a pre-Monterey OS, and the app opens and runs totally fine.

Stick a Python at that path, or add a link to same, and the app should work on Monterey and later, too.

I ended up using a variation of this:

https://stackoverflow.com/questions/3696124/changing-python-path-on-mac

You need to enter the path to the new install into PATH, not the old and stale and gone path.

Did you log out and back in to load the new PATH, or manually issue the PATH and export commands?