> It also works the other way around, at least on the non-empty > set of systems that contains my workstation. export simply > marks the variable name for automatic export to the > environment of subsequent commands. The value at that time > doesn't matter. What matters is the value that the name has > at the time the command is run: > > [EMAIL PROTECTED] ~]$ export FOOD > [EMAIL PROTECTED] ~]$ FOOD=spam > [EMAIL PROTECTED] ~]$ python -c "import os; print os.environ['FOOD']" > spam > [EMAIL PROTECTED] ~]$ FOOD=eggs > [EMAIL PROTECTED] ~]$ python -c "import os; print os.environ['FOOD']" > eggs
Just tried on a FreeBSD 6.1 development box with stock /bin/sh and it works there too... ... And I just learned something new! -Doug -- http://mail.python.org/mailman/listinfo/python-list
