The os module uses get/set for pretty much everything,
except for env, where it uses get/put. It still uses
un_set_env though.
This patch makes a newfunction setenv if putenv is
available, and makes setenv(key, value) call
putenv(key, value). I wasn't sure whether to use
default values (key=None, value=None) or not, but I
ended up doing so anyway.

Logged In: YES 
user_id=287697

And I just realised that the __doc__ was far too wide and
that both arguments to putenv are required, and thus they
should be required be setenv as well.

Pray let me know if there is anything I can do to better the
patch.

Logged In: YES 
user_id=287697

And apparently you can't upload/attach a file *and* delete
another one at the same time... ? (Or perhaps it's simple
due to the fact they were both of the same name... ?)

Logged In: YES 
user_id=38376

the os module generally uses the same name as the underlying
POSIX API.  in this case, os.putenv maps to POSIX putenv(3)
and os.getenv maps to POSIX getenv(3).

there is a setenv() function available on some platforms,
which is more like:

  def setenv(key, value, overwrite):
    if not getenv(key) or overwrite:
      putenv(key, value)

(why are you using these functions anyway?  use the environ
dictionary, already!)

Logged In: YES 
user_id=38376

(and yes, unsetenv is named that way because the underlying
Unix function is called unsetenv().  like setenv(), this
isn't a POSIX function, and is not available on all platforms).

Logged In: YES 
user_id=6380

-1.

"We already got one."