mirror of
https://github.com/python/cpython.git
synced 2025-08-09 19:38:42 +00:00
![]() This backports several PRs for gh-113993, making interned strings mortal so they can be garbage-collected when no longer needed. * Allow interned strings to be mortal, and fix related issues (GH-120520) * Add an InternalDocs file describing how interning should work and how to use it. * Add internal functions to *explicitly* request what kind of interning is done: - `_PyUnicode_InternMortal` - `_PyUnicode_InternImmortal` - `_PyUnicode_InternStatic` * Switch uses of `PyUnicode_InternInPlace` to those. * Disallow using `_Py_SetImmortal` on strings directly. You should use `_PyUnicode_InternImmortal` instead: - Strings should be interned before immortalization, otherwise you're possibly interning a immortalizing copy. - `_Py_SetImmortal` doesn't handle the `SSTATE_INTERNED_MORTAL` to `SSTATE_INTERNED_IMMORTAL` update, and those flags can't be changed in backports, as they are now part of public API and version-specific ABI. * Add private `_only_immortal` argument for `sys.getunicodeinternedsize`, used in refleak test machinery. Make sure the statically allocated string singletons are unique. This means these sets are now disjoint: - `_Py_ID` - `_Py_STR` (including the empty string) - one-character latin-1 singletons Now, when you intern a singleton, that exact singleton will be interned. * Add a `_Py_LATIN1_CHR` macro, use it instead of `_Py_ID`/`_Py_STR` for one-character latin-1 singletons everywhere (including Clinic). * Intern `_Py_STR` singletons at startup. * Beef up the tests. Cover internal details (marked with `@cpython_only`). * Add lots of assertions * Don't immortalize in PyUnicode_InternInPlace; keep immortalizing in other API (GH-121364) * Switch PyUnicode_InternInPlace to _PyUnicode_InternMortal, clarify docs * Document immortality in some functions that take `const char *` This is PyUnicode_InternFromString; PyDict_SetItemString, PyObject_SetAttrString; PyObject_DelAttrString; PyUnicode_InternFromString; and the PyModule_Add convenience functions. Always point out a non-immortalizing alternative. * Don't immortalize user-provided attr names in _ctypes * Immortalize names in code objects to avoid crash (GH-121903) * Intern latin-1 one-byte strings at startup (GH-122303) There are some 3.12-specific changes, mainly to allow statically allocated strings in deepfreeze. (In 3.13, deepfreeze switched to the general `_Py_ID`/`_Py_STR`.) Co-authored-by: Eric Snow <ericsnowcurrently@gmail.com> |
||
---|---|---|
.. | ||
clinic | ||
icons | ||
layout | ||
_msi.c | ||
_testconsole.c | ||
_wmimodule.cpp | ||
classicAppCompat.can.xml | ||
classicAppCompat.cat | ||
classicAppCompat.sccd | ||
config.c | ||
config_minimal.c | ||
crtlicense.txt | ||
dl_nt.c | ||
errmap.h | ||
frozen_dllmain.c | ||
invalid_parameter_handler.c | ||
launcher-usage.txt | ||
launcher.c | ||
launcher2.c | ||
msvcrtmodule.c | ||
pyconfig.h | ||
pylauncher.rc | ||
pyshellext.cpp | ||
pyshellext.def | ||
pyshellext.rc | ||
python.manifest | ||
python3dll.c | ||
python_exe.rc | ||
python_nt.rc | ||
python_uwp.cpp | ||
python_ver_rc.h | ||
pythonw_exe.rc | ||
readme.txt | ||
sqlite3.rc | ||
store_info.txt | ||
validate_ucrtbase.py | ||
WinMain.c | ||
winreg.c | ||
winsound.c |
Welcome to the "PC" subdirectory of the Python distribution *********************************************************** This "PC" subdirectory contains complete project files to make several older PC ports of Python, as well as all the PC-specific Python source files. It should be located in the root of the Python distribution, and there should be directories "Modules", "Objects", "Python", etc. in the parent directory of this "PC" subdirectory. Be sure to read the documentation in the Python distribution. Python requires library files such as string.py to be available in one or more library directories. The search path of libraries is set up when Python starts. To see the current Python library search path, start Python and enter "import sys" and "print sys.path". All PC ports use this scheme to try to set up a module search path: 1) The script location; the current directory without script. 2) The PYTHONPATH variable, if set. 3) Paths specified in the Registry. 4) Default directories lib, lib/win, lib/test, lib/tkinter; these are searched relative to the environment variable PYTHONHOME, if set, or relative to the executable and its ancestors, if a landmark file (Lib/string.py) is found , or the current directory (not useful). 5) The directory containing the executable. The best installation strategy is to put the Python executable and DLL in some convenient directory such as C:/python, and copy all library files and subdirectories (using XCOPY) to C:/python/lib. Then you don't need to set PYTHONPATH. Otherwise, set the environment variable PYTHONPATH to your Python search path. For example, set PYTHONPATH=.;d:\python\lib;d:\python\lib\win;d:\python\lib\dos-8x3 There are several add-in modules to build Python programs which use the native Windows operating environment. The ports here just make "QuickWin" and DOS Python versions which support a character-mode (console) environment. Look in www.python.org for Tkinter, PythonWin, WPY and wxPython. To make a Python port, start the Integrated Development Environment (IDE) of your compiler, and read in the native "project file" (or makefile) provided. This will enable you to change any source files or build settings so you can make custom builds. pyconfig.h An important configuration file specific to PC's. config.c The list of C modules to include in the Python PC version. Manually edit this file to add or remove Python modules. Additional files and subdirectories for 32-bit Windows ====================================================== python_nt.rc Resource compiler input for python15.dll. dl_nt.c Additional sources used for 32-bit Windows features. Note for Windows 3.x and DOS users ================================== Neither Windows 3.x nor DOS is supported any more. The last Python version that supported these was Python 1.5.2; the support files were present in Python 2.0 but weren't updated, and it is not our intention to support these platforms for Python 2.x.