shenleiandClaude Opus 5
5fad769ee8
The embedded 40250 script layer needs its own interpreter on five platforms. 2.7 is end-of-life, so nothing can be fetched from the target SDKs and the source is vendored (official 2.7.18 tarball, trimmed to 25MB; Lib/ stays for step 3's python27.zip). cpython-2.7.18/CMakeLists.txt builds one `mtpython` static library from exactly the 133 objects the reference libpython2.7.a contains, off by default behind -DMTGODOT_EMBED_PYTHON=ON. The source list and the built-in module table (config/config.c, 39 entries) are shared; pyconfig.h is a probe result and is not, so each platform keeps its own under config/<platform>/, regenerated by tools/py_embed/gen_pyconfig.sh and checked against the shared table. Three vendor patches, documented in docs/THIRD-PARTY.md: configure/configure.ac learn arm64 on macOS, and posixmodule.c undefines the process-control calls it hard-defines past pyconfig.h when building for iOS. macOS (ctest python.embed: every builtin imports, codecs and pickle work off the vendored Lib/), Android arm64 and iOS arm64 build. Linux needs a Linux host and Windows needs a MinGW-vs-MSVC decision; both are noted for step 4. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
49 lines
1.6 KiB
Python
49 lines
1.6 KiB
Python
"""Hook to allow user-specified customization code to run.
|
|
|
|
As a policy, Python doesn't run user-specified code on startup of
|
|
Python programs (interactive sessions execute the script specified in
|
|
the PYTHONSTARTUP environment variable if it exists).
|
|
|
|
However, some programs or sites may find it convenient to allow users
|
|
to have a standard customization file, which gets run when a program
|
|
requests it. This module implements such a mechanism. A program
|
|
that wishes to use the mechanism must execute the statement
|
|
|
|
import user
|
|
|
|
The user module looks for a file .pythonrc.py in the user's home
|
|
directory and if it can be opened, execfile()s it in its own global
|
|
namespace. Errors during this phase are not caught; that's up to the
|
|
program that imports the user module, if it wishes.
|
|
|
|
The user's .pythonrc.py could conceivably test for sys.version if it
|
|
wishes to do different things depending on the Python version.
|
|
|
|
"""
|
|
from warnings import warnpy3k
|
|
warnpy3k("the user module has been removed in Python 3.0", stacklevel=2)
|
|
del warnpy3k
|
|
|
|
import os
|
|
|
|
home = os.curdir # Default
|
|
if 'HOME' in os.environ:
|
|
home = os.environ['HOME']
|
|
elif os.name == 'posix':
|
|
home = os.path.expanduser("~/")
|
|
elif os.name == 'nt': # Contributed by Jeff Bauer
|
|
if 'HOMEPATH' in os.environ:
|
|
if 'HOMEDRIVE' in os.environ:
|
|
home = os.environ['HOMEDRIVE'] + os.environ['HOMEPATH']
|
|
else:
|
|
home = os.environ['HOMEPATH']
|
|
|
|
pythonrc = os.path.join(home, ".pythonrc.py")
|
|
try:
|
|
f = open(pythonrc)
|
|
except IOError:
|
|
pass
|
|
else:
|
|
f.close()
|
|
execfile(pythonrc)
|