<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div>AFACT, in that message Victor was only talking about allowing Unicode filenames.<br>
</div></div></div></div></blockquote><div>... </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">
<div><div><div>Finally, in most places Python 2.7 *does* handle Unicode filenames just fine.</div></div></div></div></blockquote><div><br></div><div style>I'm a bit confused. In this example:</div><div style><br></div>
<div style><a href="http://bugs.python.org/issue18695">http://bugs.python.org/issue18695</a></div><div style><br></div><div style>You are proposing that the issue should be considered a bug and a well-written patch accepted?</div>
<div style><br></div><div style>Or is is just too late for 2.7 ?</div><div style><br></div><div style>Personally I think that having some, but not all file functions accept unicode paths is pretty broken....and fixing these kinds of thing will ease 2 to 3 transition, so a good thing overall.</div>
<div style><br></div><div style>-Â Chris</div></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div>-- <br><br>Christopher Barker, Ph.D.<br>Oceanographer<br><br>Emergency Response Division<br>NOAA/NOS/OR&R Â Â Â Â Â Â (206) 526-6959Â Â voice<br>
7600 Sand Point Way NE Â Â (206) 526-6329Â Â fax<br>Seattle, WA Â 98115 Â Â Â Â (206) 526-6317Â Â main reception<br><br><a href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4