Message104826
| 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 |
<1272877379.47.0.536353580696.issue8514@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|