You can't change the environment of the parent process.
IOW, the python programs can't change the environment of the
calling csh script (or, by extenstion, the environment of
subsequent python programs that are called by the csh script).
Unless one is using "global" environment variables under AmigaOS --
but then, one would not be using a csh script...
AmigaOS had two levels of environment variables; locals were stored
in a memory structure of the shell, globals were really files in the
ENV: directory (and AmigaOS had logical names for directory paths too...
sort of the best of both VMS and UNIX <G> ENV: => SYS:env/, SYS: => dh0:
(or hd0: depending on driver) if booting from hard disk partition, df0:
for floppy) [and that has skipped the fact that it also /used/ volume
names, unlike Windows]
Uh, back on subject... Changes to global environment variables meant
writing a value to the file ENV:<variable-name>, hence it did become
available to the parent, to other programs, and even to other shell
windows...
--