➜

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 loewis
Recipients Arfrever, ezio.melotti, gregory.p.smith, lemburg, loewis, pitrou, vstinner
Date 2010-05-03.19:32:05
SpamBayes Score 0.00037185053
Marked as misclassified No
Message-id <4BDF24B0.2090000@v.loewis.de>
In-reply-to <1272877379.47.0.536353580696.issue8514@psf.upfronthosting.co.za>
Content 
> I think that we cannot decide correctly about fs*code() until we decided for os.environb.

Why is that? In msg104063, you claim that you want to create these
functions to deal with file names (not environment variables), in
msg104064, you claim that #8513 (which is about the program name in
subprocess) would benefit from these functions. Do these use cases
become invalid if os.environb becomes available?
History
Date User Action Args
2010-05-03 19:32:07loewissetrecipients: + loewis, lemburg, gregory.p.smith, pitrou, vstinner, ezio.melotti, Arfrever
2010-05-03 19:32:06loewislinkissue8514 messages
2010-05-03 19:32:05loewiscreate