[issue8514] Create fsencode() and fsdecode() functions in os.path
STINNER Victor
report at bugs.python.org
Mon May 3 11:02:59 CEST 2010
STINNER Victor <victor.stinner at haypocalc.com> added the comment:
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.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8514>
_______________________________________
More information about the Python-bugs-list
mailing list