It's definitely not me.
As you seem to have not much background on IRIS you are probably on the wrong forum.
It's neither the place for  PHP nor MySQL
 

Hi @Vic Sun , @Akshay Pandey :
Just to complete this discussion.
From Terminal I could run Py also from a JOB, and over CPIPE without problems.
From Studio Output all this FAILS.
Which makes clear that the process behind Studio is far away from being a normal
IRIS/Caché process and just good for editing and compiling.  FullStop.

I would even assume that running COS commands was not planned but rather an accident that happened 20 yerars ago.

 

I spent quite a while on the subject of python. Also the asynchronous $ZF(-2) + error log

write $zf(-2,"C:\Users\cemper\AppData\Local\Microsoft\WindowsApps\pythonw3.9.exe <c:\temp\in.py 1>c:\temp\5out.txt 2>c:\temp\5er.txt")

And the error from WINDOWS was always: the program can not be executed
A further reason to use Embedded Python!

in.pyw is simply

print("success")
exit()
 

Just an idea:
I assumed that you use a local installation of IRIS
Is this correct ? 
Or does it run on some instance separate from your local WIN.
whoami is equivalent to echo %USERDOMAIN%\%USERNAME%

write $zf(-1,"hostname > c:\temp\hostname.txt")

may clarify this.
If it's not the same machine you need a PY installation this server

you can do it from SMP > SystemOperation > Databases > .....
or from Terminal, Namespace %SYS

%SYS>do ^DATABASE
 
 
 1) Create a database
 2) Edit a database
 3) List databases
 4) Delete a database
 5) Mount a database
 6) Dismount a database
 7) Compact globals in a database
 8) Show free space for a database
 9) Show details for a database
10) Recreate a database
11) Manage database encryption
12) Return unused space for a database
13) Compact free space in a database
14) Defragment a database
15) Show background database tasks
 
Option? 2
Database directory? ?
 
1) c:\intersystems\iris\mgr\
2) c:\intersystems\iris\mgr\ens\
3) c:\intersystems\iris\mgr\ens\ensenstemp\
4) c:\intersystems\iris\mgr\enslib\
5) c:\intersystems\iris\mgr\irislib\
6) c:\intersystems\iris\mgr\irislocaldata\
7) c:\intersystems\iris\mgr\iristemp\
8) c:\intersystems\iris\mgr\user\
 
Database directory? 8 c:\intersystems\iris\mgr\user\
 
 1)* Directory:                      c:\intersystems\iris\mgr\user\
 2)* Block size (bytes):             8192
 3)* Mirror DB Name:
 4)* Mirror Set Name:
 5)  Current Size (MB):              11
 6)  Max size (MB), 0=Unlimited:     0
 7)  Expansion size (MB), 0=Default: 0
 8)  Resource name:                  %DB_USER
 9)  Preserve global attributes:     Nein
10)  Global journal state:           Ja
11)  New global collation:           IRIS standard
12)  New global growth block:        50
13)  New global pointer block:       16
14)  Read Only:                      Nein
15)* Encrypted:                      Nein
 
Field number to change?

this looks like "python" is not recognized in the spawned process
You may try a full reference "C:\......python.exe...."   

In a terminal session you have a process and $ZF(-1) starts a child process
From Studio this is definitely different as Studio uses a different type of connection using SuperServer port.
https://docs.intersystems.com/iris20211/csp/docbook/DocBook.UI.Page.cls?KEY=RCOS_fzf-1

If this is your container from GitHub I had no problem on oct.22, ~22:00 (CEST)
BUT:
- I run all docker just from the Win CMD line
- docker system prune  -f      to clean away all old junk
- docker-compose build       no extra flags
- docker-compose up -d        works as expected
- docker-compose logs         to verify the startup