HowTo: Set an Environment Variable in Mac OS X - /etc/launchd.conf HowTo: Set an Environment Variable in Mac OS X - launchd.plist Posted by Eric Dowd 2011-12-14T06:40:00+00:00 howto set-environment-variables set-mac-os-x-environment-variables. Here's a bit more information specifically regarding the PATH variable in Lion OS 10.7.x: If you need to set the PATH globally, the PATH is built by the system in the following order: Parsing the contents of the file /private/etc/paths, one path per line; Parsing the contents of the folder /private/etc/paths.d. Each file in that folder can.

PEP:	540
Title:	Add a new UTF-8 Mode
Author:	Victor Stinner <vstinner at python.org>
BDFL-Delegate:	INADA Naoki
Status:	Final
Type:	Standards Track
Created:	5-January-2016
Python-Version:	3.7
Resolution:	https://mail.python.org/pipermail/python-dev/2017-December/151173.html

Jul 07, 2017 How to Setup the PATH Environment Variable in Mac OS (Episode 1). Getting a Python development environment set up on Mac OS X. Install Python 3 Git pip virtualenv on Mac OS. Jun 17, 2017 This post shows how to add an entry to the Mac OS X PATH variable - (1) for the current terminal session only, (2) permanently for the current user only and (3) permanently for all users on a Mac OS X system. Here, the Tomcat startup.sh executable is used as an example. Jul 18, 2013 This tutorial will show you how to set your environment variables for use by both terminal and GUI applications in Mac OS X. Crear una variable de entorno para Python - Duration: 4:23.

Contents

Rationale
Annex: Encodings And Error Handlers

Add a new 'UTF-8 Mode' to enhance Python's use of UTF-8. When UTF-8 Modeis active, Python will:

use the utf-8 encoding, regardless of the locale currently set bythe current platform, and
change the stdin and stdout error handlers tosurrogateescape.

This mode is off by default, but is automatically activated when usingthe 'POSIX' locale.

Add the -X utf8 command line option and PYTHONUTF8 environmentvariable to control UTF-8 Mode.

Locale encoding and UTF-8

Python 3.6 uses the locale encoding for filenames, environmentvariables, standard streams, etc. The locale encoding is inherited fromthe locale; the encoding and the locale are tightly coupled.

Many users inherit the ASCII encoding from the POSIX locale, aka the 'C'locale, but are unable change the locale for various reasons. Thisencoding is very limited in term of Unicode support: any non-ASCIIcharacter is likely to cause trouble.

It isn't always easy to get an accurate locale. Locales don't get theexact same name on different Linux distributions, FreeBSD, macOS, etc.And some locales, like the recent C.UTF-8 locale, are only supportedby a few platforms. The current locale can even vary on the sameplatform depending on context; for example, a SSH connection can use adifferent encoding than the filesystem or local terminal encoding on thesame machine.

On the flip side, Python 3.6 is already using UTF-8 by default on macOS,Android and Windows (PEP 529) for most functions -- althoughopen() is a notable exception here. UTF-8 is also the defaultencoding of Python scripts, XML and JSON file formats. The Goprogramming languageuses UTF-8 for all strings.

UTF-8 support is nearly ubiquitous for data read and written by modernplatforms. It also has excellent support in Python. The problem issimply that the locale is frequently misconfigured. An obvious solutionsuggests itself: ignore the locale encoding and use UTF-8.

Passthough for undecodable bytes: surrogateescape

When decoding bytes from UTF-8 using the default strict errorhandler, Python 3 raises a UnicodeDecodeError on the firstundecodable byte.

Unix command line tools like cat or grep and most Python 2applications simply do not have this class of bugs: they don't decodedata, but process data as a raw bytes sequence.

Python 3 already has a solution to behave like Unix tools and Python 2:the surrogateescape error handler (PEP 383). It allows processingdata as if it were bytes, but uses Unicode in practice; undecodablebytes are stored as surrogate characters.

UTF-8 Mode sets the surrogateescape error handler for stdinand stdout, since these streams as commonly associated to Unixcommand line tools.

However, users have a different expectation on files. Files are expectedto be properly encoded, and Python is expected to fail early whenopen() is called with the wrong options, like opening a JPEG picturein text mode. The open() default error handler remains strictfor these reasons.

No change by default for best backward compatibility

While UTF-8 is perfect in most cases, sometimes the locale encoding isactually the best encoding.

This PEP changes the behaviour for the POSIX locale since this locale isusually equivalent to the ASCII encoding, whereas UTF-8 is a much betterchoice. It does not change the behaviour for other locales to preventany risk or regression.

As users are responsible to enable explicitly the new UTF-8 Mode forthese other locales, they are responsible for any potential mojibakeissues caused by UTF-8 Mode.

Add a new UTF-8 Mode to use the UTF-8 encoding, ignore the localeencoding, and change stdin and stdout error handlers tosurrogateescape.

Add the new -X utf8 command line option and PYTHONUTF8environment variable. Users can explicitly activate UTF-8 Mode with thecommand-line option -X utf8 or by setting the environment variablePYTHONUTF8=1.

This mode is disabled by default and enabled by the POSIX locale. Userscan explicitly disable UTF-8 Mode with the command-line option -Xutf8=0 or by setting the environment variable PYTHONUTF8=0.

For standard streams, the PYTHONIOENCODING environment variable haspriority over UTF-8 Mode.

On Windows, the PYTHONLEGACYWINDOWSFSENCODING environment variable(PEP 529) has the priority over UTF-8 Mode.

Effects of UTF-8 Mode:

sys.getfilesystemencoding() returns 'UTF-8'.
locale.getpreferredencoding() returns UTF-8; itsdo_setlocale argument, and the locale encoding, are ignored.
sys.stdin and sys.stdout error handler is set tosurrogateescape.

Side effects:

open() uses the UTF-8 encoding by default. However, it stilluses the strict error handler by default.
os.fsdecode() and os.fsencode() use the UTF-8 encoding.
Command line arguments, environment variables and filenames use theUTF-8 encoding.

The POSIX locale enables the locale coercion (PEP 538) and the UTF-8mode (PEP 540). When the locale coercion is enabled, enabling theUTF-8 mode has no additional effect.

The UTF-8 Mode has the same effect as locale coercion:

sys.getfilesystemencoding() returns 'UTF-8',
locale.getpreferredencoding() returns UTF-8, and
the sys.stdin and sys.stdout error handlers are set tosurrogateescape.

These changes only affect Python code. But the locale coercion hasadditional effects: the LC_CTYPE environment variable and theLC_CTYPE locale are set to a UTF-8 locale like C.UTF-8. One sideeffect is that non-Python code is also impacted by the locale coercion.The two PEPs are complementary.

On platforms like Centos 7 where locale coercion is not supported, thePOSIX locale only enables UTF-8 Mode. In this case, Python code usesthe UTF-8 encoding and ignores the locale encoding, whereas non-Pythoncode uses the locale encoding, which is usually ASCII for the POSIXlocale.

While the UTF-8 Mode is supported on all platforms and can be enabledwith any locale, the locale coercion is not supported by all

Mac Os X Set Environment Variable For Python