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 vstinner
Recipients Arfrever, ezio.melotti, gregory.p.smith, lemburg, loewis, pitrou, vstinner
Date 2010-05-03.09:02:56
SpamBayes Score 0.0067167263
Marked as misclassified No
Message-id <>
loewis> I really, really, REALLY think that it is bad to mix issues.
loewis> This makes patch review impossible.

I tried to, but it looks difficult :-) Anyway, I opened #8603.

> This specific issue is about introducing an fsdecode and fsencode 
> function; this is what the bug title says, and what the initial patch
> did.

I know, but the two topics (fs*code() and os.environb) are very close and related. My os.environb implementation uses fsencode()/fsdecode().

> FWIW, I'm +0 on adding these functions. MAL, please stop messing
> issue subjects. (...)

I think that we cannot decide correctly about fs*code() until we decided for os.environb.
Date User Action Args
2010-05-03 09:03:00vstinnersetrecipients: + vstinner, lemburg, loewis, gregory.p.smith, pitrou, ezio.melotti, Arfrever
2010-05-03 09:02:59vstinnersetmessageid: <>
2010-05-03 09:02:57vstinnerlinkissue8514 messages
2010-05-03 09:02:56vstinnercreate