This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author DennisJensen
Recipients DennisJensen, docs@python
Date 2016-09-21.15:26:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474471581.82.0.975810420091.issue28242@psf.upfronthosting.co.za>
In-reply-to
Content
I was encountering what seemed to be odd behavior from os.environ.get() from what I could find out about it and so I tried to locate the actual documentation on how it is supposed to be used now.  However, all I can find is a minor reference to os.environ.  There appears to be no documentation on os.environ.get() and/or any other methods of this sort associated with os.environ.  The alternate functionality os.getenv() is documented but this is not supposed to work the same as os.environ.get()   Still the behavior that I encountered is that it seems that either os.environ.get()) has been changed and/or it is now just simply a proxy for os.getenv() -- as these two seem to function the same way now.  Note: From what I was able to discern about how os.environ.get() worked is that it accepts only 1 parameter and if the item does not exist it throws an error -- while os.getenv() takes 2 parameters and does not throw an error if the item does not exist.
History
Date User Action Args
2016-09-21 15:26:21DennisJensensetrecipients: + DennisJensen, docs@python
2016-09-21 15:26:21DennisJensensetmessageid: <1474471581.82.0.975810420091.issue28242@psf.upfronthosting.co.za>
2016-09-21 15:26:21DennisJensenlinkissue28242 messages
2016-09-21 15:26:21DennisJensencreate