Re:The History and rationale of the Python 3 Unicode model f...
by adgjlsfhk1 on Wednesday December 14, 2022 @12:42PM
(#33986915)
The problem with using strict UTF-8 for paths is that paths aren't guaranteed to be valid UTF-8. How do you want to write a program that opens a path who's name is invalid UTF-8?
[ Parent
| on HN ]
Re:The History and rationale of the Python 3 Unicode model f...
by masklinn on Wednesday December 14, 2022 @01:28PM
(#33987648)
> The problem with using strict UTF-8 for paths is that paths aren't guaranteed to be valid UTF-8.
Ok but I’m not saying to do that. I’m saying if you have not-utf8 strings don’t call them UTF8.
> How do you want to write a program that opens a path who's name is invalid UTF-8?
That’s not my problem given I’m not advocating for that.
Re:The History and rationale of the Python 3 Unicode model f...
by StefanKarpinski on Wednesday December 14, 2022 @04:09PM
(#33990601)
The issue is that when you're implementing something like a programming language or a robust general purpose utility, then simply not being able to open—or list or remove or stat—paths with invalid names is not really acceptable.