The problem with your approach is that you are trying to interpret bash scripts. First you just try to interpret the export statement. Then you notice people are using variable expansion. Later people will put conditionals in their files, or process substitutions. In the end you will have a full blown bash script interpreter with a gazillion bugs. Don't do that.
Let Bash interpret the file for you and then collect the results.
You can do it like this:
#! /usr/bin/env python
import os
import pprint
import shlex
import subprocess
command = shlex.split("env -i bash -c 'source init_env && env'")
proc = subprocess.Popen(command, stdout = subprocess.PIPE)
for line in proc.stdout:
(key, _, value) = line.partition("=")
os.environ[key] = value
proc.communicate()
pprint.pprint(dict(os.environ))
Make sure that you handle errors in case bash fails to source init_env
, or bash itself fails to execute, or subprocess fails to execute bash, or any other errors.
the env -i
at the beginning of the command line creates a clean environment. that means you will only get the environment variables from init_env
. if you want the inherited system environment then omit env -i
.
Read the documentation on subprocess for more details.
Note: this will only capture variables set with the export
statement, as env
only prints exported variables.
Enjoy.
Note that the Python documentation says that if you want to manipulate the environment you should manipulate os.environ
directly instead of using os.putenv()
. I consider that a bug, but I digress.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…