I've installed Rocket Open AppDev for Z (free solution), but Python doesn't seem to be working quite right.

In particular, I'm getting different behavior based on whether I invoke Python via executing the script vs. invoking Python manually and passing it the script.  For example, with the following sample test.py:

#!/z/rocket/tools/bin/python

print("Hello world!")

If I invoke Python explicitly and pass it the script, it works just fine:

$ /z/rocket/tools/bin/python test.py

Hello world!

If I instead invoke the script directly, I get the following.

$ ./test.py

./test.py: can't open file '/u/z123/SHELL=/z/rocket/tools/bin/bash': [Errno 129] EDC5129I No such file or directory.

That looks like it's somehow interpreting the environment being passed to python ("SHELL=...") as the script name it's supposed to execute.  Indeed, if I then pass the script name as the first argument, it works:

$ ./test.py test.py

Hello world!

Stranger still, I don't see this behavior with scripts that invoke /bin/sh or /z/rocket/tools/bin/bash.

The following environment variables seem to be correctly set:

_BPXK_AUTOCVT=ON

_CEE_RUNOPTS=FILETAG(AUTOCVT,AUTOTAG) POSIX(ON)

PATH=/z/rocket/tools/condabin:/z/rocket/tools/bin:/bin:.

Changing the value of _BPX_SPAWN_SCRIPT doesn't change the behavior either.

Any ideas?

I've installed Rocket Open AppDev for Z (free solution), but Python doesn't seem to be working quite right.

In particular, I'm getting different behavior based on whether I invoke Python via executing the script vs. invoking Python manually and passing it the script.  For example, with the following sample test.py:

#!/z/rocket/tools/bin/python

print("Hello world!")

If I invoke Python explicitly and pass it the script, it works just fine:

$ /z/rocket/tools/bin/python test.py

Hello world!

If I instead invoke the script directly, I get the following.

$ ./test.py

./test.py: can't open file '/u/z123/SHELL=/z/rocket/tools/bin/bash': [Errno 129] EDC5129I No such file or directory.

That looks like it's somehow interpreting the environment being passed to python ("SHELL=...") as the script name it's supposed to execute.  Indeed, if I then pass the script name as the first argument, it works:

$ ./test.py test.py

Hello world!

Stranger still, I don't see this behavior with scripts that invoke /bin/sh or /z/rocket/tools/bin/bash.

The following environment variables seem to be correctly set:

_BPXK_AUTOCVT=ON

_CEE_RUNOPTS=FILETAG(AUTOCVT,AUTOTAG) POSIX(ON)

PATH=/z/rocket/tools/condabin:/z/rocket/tools/bin:/bin:.

Changing the value of _BPX_SPAWN_SCRIPT doesn't change the behavior either.

Any ideas?

I've installed Rocket Open AppDev for Z (free solution), but Python doesn't seem to be working quite right.

In particular, I'm getting different behavior based on whether I invoke Python via executing the script vs. invoking Python manually and passing it the script.  For example, with the following sample test.py:

#!/z/rocket/tools/bin/python

print("Hello world!")

If I invoke Python explicitly and pass it the script, it works just fine:

$ /z/rocket/tools/bin/python test.py

Hello world!

If I instead invoke the script directly, I get the following.

$ ./test.py

./test.py: can't open file '/u/z123/SHELL=/z/rocket/tools/bin/bash': [Errno 129] EDC5129I No such file or directory.

That looks like it's somehow interpreting the environment being passed to python ("SHELL=...") as the script name it's supposed to execute.  Indeed, if I then pass the script name as the first argument, it works:

$ ./test.py test.py

Hello world!

Stranger still, I don't see this behavior with scripts that invoke /bin/sh or /z/rocket/tools/bin/bash.

The following environment variables seem to be correctly set:

_BPXK_AUTOCVT=ON

_CEE_RUNOPTS=FILETAG(AUTOCVT,AUTOTAG) POSIX(ON)

PATH=/z/rocket/tools/condabin:/z/rocket/tools/bin:/bin:.

Changing the value of _BPX_SPAWN_SCRIPT doesn't change the behavior either.

Any ideas?