On Thu, Jan 20, 2011 at 10:41 PM, Victor Stinner <victor.stin...@haypocalc.com> wrote: > Le jeudi 20 janvier 2011 à 10:04 +0100, raymond.hettinger a écrit : >> +Some operating systems allow direct access to the unencoded bytes in the >> +environment. If so, the :attr:`os.supports_bytes_environ` constant will be >> +true. >> + >> +For direct access to unencoded environment variables (if available), >> +use the new :func:`os.getenvb` function or use :data:`os.environb` >> +which is a bytes version of :data:`os.environ`. > > Hum, I think that "undecoded" bytes term is more appropriate. You can > decode bytes and encode characters, but not the opposite.
I was going to say the same thing. "encoded", "undecoded" or "raw" would all work, but "unencoded" definitely isn't right. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
