Chris's Wiki :: blog/python/FilenamesUniqueType Commentshttps://utcc.utoronto.ca/~cks/space/blog/python/FilenamesUniqueType?atomcommentsDWiki2020-01-26T04:41:19ZRecent comments in Chris's Wiki :: blog/python/FilenamesUniqueType.By mk-fg on /blog/python/FilenamesUniqueTypetag:CSpace:blog/python/FilenamesUniqueType:e5d53914b3be8b382c9fd29d190e61da5d0f9fddmk-fg<div class="wikitext"><p>I suspect long-term py3 might come around to your suggestion via pathlib, actually.</p>
<p>It wasn't there at first, then as an option, then supported in all os.* stuff, then recommended over os.path or open() and such, and next step might be phasing-out path strings entirely.
And by that point, it can accomodate for any kind of underlying os quirks internally.</p>
<p>Anecdotally, came to always use it for paths these days (as it's way more clean and convenient than os.path), especially with convenience stuff like .read_text()/.read_bytes() and .write_text()/.write_bytes() (which is like 80%-90% of what paths are used for).</p>
</div>2020-01-26T04:41:19ZBy anon on /blog/python/FilenamesUniqueTypetag:CSpace:blog/python/FilenamesUniqueType:caa1a1cd56d678e8c1ecd8999714ab17be747535anon<div class="wikitext"><p>extra points for os x which does unicode normalisation differently, eg. "ü" on windows/linux/bsd is just that, whereas on os x it's "u¨".
fun times transferring files between systems...</p>
</div>2019-12-29T14:32:41Z