Message104210
| Author |
vstinner |
| Recipients |
Arfrever, ezio.melotti, gregory.p.smith, lemburg, loewis, vstinner |
| Date |
2010年04月26日.10:37:58 |
| SpamBayes Score |
1.2612153e-06 |
| Marked as misclassified |
No |
| Message-id |
<1272278280.43.0.421714122935.issue8514@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> They're also useful for dealing with environment variables
> which are not strictly filesystem (fs) related but also suffer
> from the same issue requiring surrogate escape.
Yes, Python3 decodes environment variables using sys.getfilesystemencoding()+surrogateescape. And since my last fix on os.execve(), subprocess (and os.execv(p)e) uses also surrogateescape to encode environment variables.
And yes again, I also patched os.getenv() to decode bytes name to unicode using sys.getfilesystemencoding()+surrogateescape.
> But other than just calling these os.encode and os.decode
*fs*encode() and *fs*decode() is a reference to the encoding: sys.get*filesystem*encoding().
> I just wanted to point the other use out
See also issue #8513. |
|