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 lemburg
Recipients Arfrever, ezio.melotti, gregory.p.smith, lemburg, loewis, pitrou, vstinner
Date 2010-07-29.07:56:22
SpamBayes Score 0.0015567661
Marked as misclassified No
Message-id <4C513424.2090300@egenix.com>
In-reply-to <1280365707.71.0.0176269867884.issue8603@psf.upfronthosting.co.za>
Content
Ezio Melotti wrote:
> 
> Ezio Melotti <ezio.melotti@gmail.com> added the comment:
> 
> A quick search[0] also shows that environ.data is used by several projects. Changing it from str to bytes will most likely break these programs, so I'm not sure it's a good idea.
> Also, if I understand correctly, on Windows os.environ.data still contains str, so it's inconsistent with other systems.
> IMHO os.environ.data should contain str, whereas os.environb.data bytes. If they must share the same data I would prefer them to be both str.
>
> [0]: http://www.google.com/codesearch?q=lang%3Apython+environ.data&hl=en

Direct use of os.environ.data is not permitted as it is not a documented
feature, so I wouldn't worry about this.

The few uses you found are easy to fix.
History
Date User Action Args
2010-07-29 07:56:24lemburgsetrecipients: + lemburg, loewis, gregory.p.smith, pitrou, vstinner, ezio.melotti, Arfrever
2010-07-29 07:56:22lemburglinkissue8603 messages
2010-07-29 07:56:22lemburgcreate