CINXE.COM

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta name="color-scheme" content="light dark"> <title>PEP 514 – Python registration in the Windows registry | peps.python.org</title> <link rel="shortcut icon" href="../_static/py.png"> <link rel="canonical" href="https://peps.python.org/pep-0514/"> <link rel="stylesheet" href="../_static/style.css" type="text/css"> <link rel="stylesheet" href="../_static/mq.css" type="text/css"> <link rel="stylesheet" href="../_static/pygments.css" type="text/css" media="(prefers-color-scheme: light)" id="pyg-light"> <link rel="stylesheet" href="../_static/pygments_dark.css" type="text/css" media="(prefers-color-scheme: dark)" id="pyg-dark"> <link rel="alternate" type="application/rss+xml" title="Latest PEPs" href="https://peps.python.org/peps.rss"> <meta property="og:title" content='PEP 514 – Python registration in the Windows registry | peps.python.org'> <meta property="og:description" content="This PEP defines a schema for the Python registry key to allow third-party installers to register their installation, and to allow tools and applications to detect and correctly display all Python environments on a user’s machine. No implementation chan..."> <meta property="og:type" content="website"> <meta property="og:url" content="https://peps.python.org/pep-0514/"> <meta property="og:site_name" content="Python Enhancement Proposals (PEPs)"> <meta property="og:image" content="https://peps.python.org/_static/og-image.png"> <meta property="og:image:alt" content="Python PEPs"> <meta property="og:image:width" content="200"> <meta property="og:image:height" content="200"> <meta name="description" content="This PEP defines a schema for the Python registry key to allow third-party installers to register their installation, and to allow tools and applications to detect and correctly display all Python environments on a user’s machine. No implementation chan..."> <meta name="theme-color" content="#3776ab"> </head> <body> <svg xmlns="http://www.w3.org/2000/svg" style="display: none;"> <symbol id="svg-sun-half" viewBox="0 0 24 24" pointer-events="all"> <title>Following system colour scheme</title> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"> <circle cx="12" cy="12" r="9"></circle> <path d="M12 3v18m0-12l4.65-4.65M12 14.3l7.37-7.37M12 19.6l8.85-8.85"></path> </svg> </symbol> <symbol id="svg-moon" viewBox="0 0 24 24" pointer-events="all"> <title>Selected dark colour scheme</title> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"> <path stroke="none" d="M0 0h24v24H0z" fill="none"></path> <path d="M12 3c.132 0 .263 0 .393 0a7.5 7.5 0 0 0 7.92 12.446a9 9 0 1 1 -8.313 -12.454z"></path> </svg> </symbol> <symbol id="svg-sun" viewBox="0 0 24 24" pointer-events="all"> <title>Selected light colour scheme</title> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"> <circle cx="12" cy="12" r="5"></circle> <line x1="12" y1="1" x2="12" y2="3"></line> <line x1="12" y1="21" x2="12" y2="23"></line> <line x1="4.22" y1="4.22" x2="5.64" y2="5.64"></line> <line x1="18.36" y1="18.36" x2="19.78" y2="19.78"></line> <line x1="1" y1="12" x2="3" y2="12"></line> <line x1="21" y1="12" x2="23" y2="12"></line> <line x1="4.22" y1="19.78" x2="5.64" y2="18.36"></line> <line x1="18.36" y1="5.64" x2="19.78" y2="4.22"></line> </svg> </symbol> </svg> <script> document.documentElement.dataset.colour_scheme = localStorage.getItem("colour_scheme") || "auto" </script> <section id="pep-page-section"> <header> <h1>Python Enhancement Proposals</h1> <ul class="breadcrumbs"> <li><a href="https://www.python.org/" title="The Python Programming Language">Python</a> » </li> <li><a href="../pep-0000/">PEP Index</a> » </li> <li>PEP 514</li> </ul> <button id="colour-scheme-cycler" onClick="setColourScheme(nextColourScheme())"> <svg aria-hidden="true" class="colour-scheme-icon-when-auto"><use href="#svg-sun-half"></use></svg> <svg aria-hidden="true" class="colour-scheme-icon-when-dark"><use href="#svg-moon"></use></svg> <svg aria-hidden="true" class="colour-scheme-icon-when-light"><use href="#svg-sun"></use></svg> Toggle light / dark / auto colour theme </button> </header> <article> <section id="pep-content"> <h1 class="page-title">PEP 514 – Python registration in the Windows registry</h1> <dl class="rfc2822 field-list simple"> <dt class="field-odd">Author:</dt> <dd class="field-odd">Steve Dower <steve.dower at python.org></dd> <dt class="field-even">BDFL-Delegate:</dt> <dd class="field-even">Paul Moore <p.f.moore at gmail.com></dd> <dt class="field-odd">Status:</dt> <dd class="field-odd"><abbr title="Currently valid informational guidance, or an in-use process">Active</abbr></dd> <dt class="field-even">Type:</dt> <dd class="field-even"><abbr title="Non-normative PEP containing background, guidelines or other information relevant to the Python ecosystem">Informational</abbr></dd> <dt class="field-odd">Created:</dt> <dd class="field-odd">02-Feb-2016</dd> <dt class="field-even">Post-History:</dt> <dd class="field-even">02-Feb-2016, 01-Mar-2016, 18-Jul-2016</dd> <dt class="field-odd">Resolution:</dt> <dd class="field-odd"><a class="reference external" href="https://mail.python.org/pipermail/python-dev/2016-July/145697.html">Python-Dev message</a></dd> </dl> <hr class="docutils" /> <section id="contents"> <details><summary>Table of Contents</summary><ul class="simple"> <li><a class="reference internal" href="#abstract">Abstract</a></li> <li><a class="reference internal" href="#motivation">Motivation</a></li> <li><a class="reference internal" href="#definitions">Definitions</a></li> <li><a class="reference internal" href="#structure">Structure</a><ul> <li><a class="reference internal" href="#backwards-compatibility">Backwards Compatibility</a></li> <li><a class="reference internal" href="#company">Company</a></li> <li><a class="reference internal" href="#tag">Tag</a></li> <li><a class="reference internal" href="#installpath">InstallPath</a></li> <li><a class="reference internal" href="#help">Help</a></li> <li><a class="reference internal" href="#other-keys">Other Keys</a></li> </ul> </li> <li><a class="reference internal" href="#sample-code">Sample Code</a></li> <li><a class="reference internal" href="#references">References</a></li> <li><a class="reference internal" href="#copyright">Copyright</a></li> </ul> </details></section> <section id="abstract"> <h2><a class="toc-backref" href="#abstract" role="doc-backlink">Abstract</a></h2> This PEP defines a schema for the Python registry key to allow third-party installers to register their installation, and to allow tools and applications to detect and correctly display all Python environments on a user’s machine. No implementation changes to Python are proposed with this PEP. Python environments are not required to be registered unless they want to be automatically discoverable by external tools. As this relates to Windows only, these tools are expected to be predominantly GUI applications. However, console applications may also make use of the registered information. This PEP covers the information that may be made available, but the actual presentation and use of this information is left to the tool designers. The schema matches the registry values that have been used by the official installer since at least Python 2.5, and the resolution behaviour matches the behaviour of the official Python releases. Some backwards compatibility rules are provided to ensure tools can correctly detect versions of CPython that do not register full information. </section> <section id="motivation"> <h2><a class="toc-backref" href="#motivation" role="doc-backlink">Motivation</a></h2> When installed on Windows, the official Python installer creates a registry key for discovery and detection by other applications. This allows tools such as installers or IDEs to automatically detect and display a user’s Python installations. For example, the <a class="pep reference internal" href="../pep-0397/" title="PEP 397 – Python launcher for Windows">PEP 397</a> <code class="docutils literal notranslate">py.exe</code> launcher and editors such as PyCharm and Visual Studio already make use of this information. Third-party installers, such as those used by distributions, typically create identical keys for the same purpose. Most tools that use the registry to detect Python installations only inspect the keys used by the official installer. As a result, third-party installations that wish to be discoverable will overwrite these values, often causing users to “lose” their original Python installation. By describing a layout for registry keys that allows third-party installations to register themselves uniquely, as well as providing tool developers guidance for discovering all available Python installations, these collisions should be prevented. We also take the opportunity to add some well-known metadata so that more information can be presented to users. </section> <section id="definitions"> <h2><a class="toc-backref" href="#definitions" role="doc-backlink">Definitions</a></h2> A “registry key” is the equivalent of a file-system path into the registry. Each key may contain “subkeys” (keys nested within keys) and “values” (named and typed attributes attached to a key). These are used on Windows to store settings in much the same way that directories containing configuration files would work. <code class="docutils literal notranslate">HKEY_CURRENT_USER</code> is the root of settings for the currently logged-in user, and this user can generally read and write all settings under this root. <code class="docutils literal notranslate">HKEY_LOCAL_MACHINE</code> is the root of settings for all users. Generally, any user can read these settings but only administrators can modify them. It is typical for values under <code class="docutils literal notranslate">HKEY_CURRENT_USER</code> to take precedence over those in <code class="docutils literal notranslate">HKEY_LOCAL_MACHINE</code>. On 64-bit Windows, <code class="docutils literal notranslate">HKEY_LOCAL_MACHINE\Software\Wow6432Node</code> is a special key that 32-bit processes transparently read and write to rather than accessing the <code class="docutils literal notranslate">Software</code> key directly. Further documentation regarding registry redirection on Windows is available from the MSDN Library <a class="footnote-reference brackets" href="#id2" id="id1">[1]</a>. </section> <section id="structure"> <h2><a class="toc-backref" href="#structure" role="doc-backlink">Structure</a></h2> We consider there to be a single collection of Python environments on a machine, where the collection may be different for each user of the machine. There are three potential registry locations where the collection may be stored based on the installation options of each environment: <div class="highlight-default notranslate"><div class="highlight"><pre>HKEY_CURRENT_USER\Software\Python\<Company>\<Tag> HKEY_LOCAL_MACHINE\Software\Python\<Company>\<Tag> HKEY_LOCAL_MACHINE\Software\Wow6432Node\Python\<Company>\<Tag> </pre></div> </div> Official Python releases use <code class="docutils literal notranslate">PythonCore</code> for Company, and the value of <code class="docutils literal notranslate">sys.winver</code> for Tag. The Company <code class="docutils literal notranslate">PyLauncher</code> is reserved. Other registered environments may use any values for Company and Tag. Recommendations are made later in this document. Company-Tag pairs are case-insensitive, and uniquely identify each environment. Depending on the purpose and intended use of a tool, there are two suggested approaches for resolving conflicts between Company-Tag pairs. Tools that list every installed environment may choose to include those even where the Company-Tag pairs match. They should ensure users can easily identify whether the registration was per-user or per-machine, and which registration has the higher priority. Tools that aim to select a single installed environment from all registered environments based on the Company-Tag pair, such as the <code class="docutils literal notranslate">py.exe</code> launcher, should always select the environment registered in <code class="docutils literal notranslate">HKEY_CURRENT_USER</code> when than the matching one in <code class="docutils literal notranslate">HKEY_LOCAL_MACHINE</code>. Conflicts between <code class="docutils literal notranslate">HKEY_LOCAL_MACHINE\Software\Python</code> and <code class="docutils literal notranslate">HKEY_LOCAL_MACHINE\Software\Wow6432Node\Python</code> should only occur when both 64-bit and 32-bit versions of an interpreter have the same Tag. In this case, the tool should select whichever is more appropriate for its use. If a tool is able to determine from the provided information (or lack thereof) that it cannot use a registered environment, there is no obligation to present it to users. Except as discussed in the section on backwards compatibility, Company and Tag values are considered opaque to tools, and no information about the interpreter should be inferred from the text. However, some tools may display the Company and Tag values to users, so ideally the Tag will be able to help users identify the associated environment. Python environments are not required to register themselves unless they want to be automatically discoverable by external tools. <section id="backwards-compatibility"> <h3><a class="toc-backref" href="#backwards-compatibility" role="doc-backlink">Backwards Compatibility</a></h3> Python 3.4 and earlier did not distinguish between 32-bit and 64-bit builds in <code class="docutils literal notranslate">sys.winver</code>. As a result, it is not possible to have valid side-by-side installations of both 32-bit and 64-bit interpreters under this scheme since it would result in duplicate Tags. To ensure backwards compatibility, applications should treat environments listed under the following two registry keys as distinct, even when the Tag matches: <div class="highlight-default notranslate"><div class="highlight"><pre>HKEY_LOCAL_MACHINE\Software\Python\PythonCore\<Tag> HKEY_LOCAL_MACHINE\Software\Wow6432Node\Python\PythonCore\<Tag> </pre></div> </div> Environments listed under <code class="docutils literal notranslate">HKEY_CURRENT_USER</code> may be treated as distinct from both of the above keys, potentially resulting in three environments discovered using the same Tag. Alternatively, a tool may determine whether the per-user environment is 64-bit or 32-bit and give it priority over the per-machine environment, resulting in a maximum of two discovered environments. It is not possible to detect side-by-side installations of both 64-bit and 32-bit versions of Python prior to 3.5 when they have been installed for the current user. Python 3.5 and later always uses different Tags for 64-bit and 32-bit versions. The following section describe user-visible information that may be registered. For Python 3.5 and earlier, none of this information is available, but alternative defaults are specified for the <code class="docutils literal notranslate">PythonCore</code> key. Environments registered under other Company names have no backward compatibility requirements and must use distinct Tags to support side-by-side installations. Tools consuming these registrations are not required to disambiguate tags other than by preferring the user’s setting. </section> <section id="company"> <h3><a class="toc-backref" href="#company" role="doc-backlink">Company</a></h3> The Company part of the key is intended to group related environments and to ensure that Tags are namespaced appropriately. The key name should be alphanumeric without spaces and likely to be unique. For example, a trademarked name (preferred), a hostname, or as a last resort, a UUID would be appropriate: <div class="highlight-default notranslate"><div class="highlight"><pre>HKEY_CURRENT_USER\Software\Python\ExampleCorp HKEY_CURRENT_USER\Software\Python\www.example.com HKEY_CURRENT_USER\Software\Python\6C465E66-5A8C-4942-9E6A-D29159480C60 </pre></div> </div> The company name <code class="docutils literal notranslate">PyLauncher</code> is reserved for the <a class="pep reference internal" href="../pep-0397/" title="PEP 397 – Python launcher for Windows">PEP 397</a> launcher (<code class="docutils literal notranslate">py.exe</code>). It does not follow this convention and should be ignored by tools. If a string value named <code class="docutils literal notranslate">DisplayName</code> exists, it should be used to identify the environment manufacturer/developer/distributor to users. Otherwise, the name of the key should be used. (For <code class="docutils literal notranslate">PythonCore</code>, the default display name is “Python Software Foundation”.) If a string value named <code class="docutils literal notranslate">SupportUrl</code> exists, it may be displayed or otherwise used to direct users to a web site related to the environment. (For <code class="docutils literal notranslate">PythonCore</code>, the default support URL is “<a class="reference external" href="http://www.python.org/">http://www.python.org/</a>”.) A complete example may look like: <div class="highlight-default notranslate"><div class="highlight"><pre>HKEY_CURRENT_USER\Software\Python\ExampleCorp (Default) = (value not set) DisplayName = "Example Corp" SupportUrl = "http://www.example.com" </pre></div> </div> </section> <section id="tag"> <h3><a class="toc-backref" href="#tag" role="doc-backlink">Tag</a></h3> The Tag part of the key is intended to uniquely identify an environment within those provided by a single company. The key name should be alphanumeric without spaces and stable across installations. For example, the Python language version, a UUID or a partial/complete hash would be appropriate, while a Tag based on the install directory or some aspect of the current machine may not. For example: <div class="highlight-default notranslate"><div class="highlight"><pre>HKEY_CURRENT_USER\Software\Python\ExampleCorp\examplepy HKEY_CURRENT_USER\Software\Python\ExampleCorp\3.6 HKEY_CURRENT_USER\Software\Python\ExampleCorp\6C465E66 </pre></div> </div> It is expected that some tools will require users to type the Tag into a command line, and that the Company may be optional provided the Tag is unique across all Python installations. Short, human-readable and easy to type Tags are recommended, and if possible, select a value likely to be unique across all other Companies. If a string value named <code class="docutils literal notranslate">DisplayName</code> exists, it should be used to identify the environment to users. Otherwise, the name of the key should be used. (For <code class="docutils literal notranslate">PythonCore</code>, the default is “Python “ followed by the Tag.) If a string value named <code class="docutils literal notranslate">SupportUrl</code> exists, it may be displayed or otherwise used to direct users to a web site related to the environment. (For <code class="docutils literal notranslate">PythonCore</code>, the default is “<a class="reference external" href="http://www.python.org/">http://www.python.org/</a>”.) If a string value named <code class="docutils literal notranslate">Version</code> exists, it should be used to identify the version of the environment. This is independent from the version of Python implemented by the environment. (For <code class="docutils literal notranslate">PythonCore</code>, the default is the first three characters of the Tag.) If a string value named <code class="docutils literal notranslate">SysVersion</code> exists, it must be in <code class="docutils literal notranslate">x.y</code> or <code class="docutils literal notranslate">x.y.z</code> format matching the version returned by <code class="docutils literal notranslate">sys.version_info</code> in the interpreter. If omitted, the Python version is unknown. (For <code class="docutils literal notranslate">PythonCore</code>, the default is the first three characters of the Tag.) If a string value named <code class="docutils literal notranslate">SysArchitecture</code> exists, it must match the first element of the tuple returned by <code class="docutils literal notranslate">platform.architecture()</code>. Typically, this will be “32bit” or “64bit”. If omitted, the architecture is unknown. (For <code class="docutils literal notranslate">PythonCore</code>, the architecture is “32bit” when registered under <code class="docutils literal notranslate">HKEY_LOCAL_MACHINE\Software\Wow6432Node\Python</code> or anywhere on a 32-bit operating system, “64bit” when registered under <code class="docutils literal notranslate">HKEY_LOCAL_MACHINE\Software\Python</code> on a 64-bit machine, and unknown when registered under <code class="docutils literal notranslate">HKEY_CURRENT_USER</code>.) Note that each of these values is recommended, but optional. Omitting <code class="docutils literal notranslate">SysVersion</code> or <code class="docutils literal notranslate">SysArchitecture</code> may prevent some tools from correctly supporting the environment. A complete example may look like this: <div class="highlight-default notranslate"><div class="highlight"><pre>HKEY_CURRENT_USER\Software\Python\ExampleCorp\examplepy (Default) = (value not set) DisplayName = "Example Py Distro 3" SupportUrl = "http://www.example.com/distro-3" Version = "3.0.12345.0" SysVersion = "3.6.0" SysArchitecture = "64bit" </pre></div> </div> </section> <section id="installpath"> <h3><a class="toc-backref" href="#installpath" role="doc-backlink">InstallPath</a></h3> Beneath the environment key, an <code class="docutils literal notranslate">InstallPath</code> key must be created. This key is always named <code class="docutils literal notranslate">InstallPath</code>, and the default value must match <code class="docutils literal notranslate">sys.prefix</code>: <div class="highlight-default notranslate"><div class="highlight"><pre>HKEY_CURRENT_USER\Software\Python\ExampleCorp\3.6\InstallPath (Default) = "C:\ExampleCorpPy36" </pre></div> </div> If a string value named <code class="docutils literal notranslate">ExecutablePath</code> exists, it must be the full path to the <code class="docutils literal notranslate">python.exe</code> (or equivalent) executable. If omitted, the environment is not executable. (For <code class="docutils literal notranslate">PythonCore</code>, the default is the <code class="docutils literal notranslate">python.exe</code> file in the directory referenced by the <code class="docutils literal notranslate">(Default)</code> value.) If a string value named <code class="docutils literal notranslate">ExecutableArguments</code> exists, tools should use the value as the first arguments when executing <code class="docutils literal notranslate">ExecutablePath</code>. Tools may add other arguments following these, and will reasonably expect standard Python command line options to be available. If a string value named <code class="docutils literal notranslate">WindowedExecutablePath</code> exists, it must be a path to the <code class="docutils literal notranslate">pythonw.exe</code> (or equivalent) executable. If omitted, the default is the value of <code class="docutils literal notranslate">ExecutablePath</code>, and if that is omitted the environment is not executable. (For <code class="docutils literal notranslate">PythonCore</code>, the default is the <code class="docutils literal notranslate">pythonw.exe</code> file in the directory referenced by the <code class="docutils literal notranslate">(Default)</code> value.) If a string value named <code class="docutils literal notranslate">WindowedExecutableArguments</code> exists, tools should use the value as the first arguments when executing <code class="docutils literal notranslate">WindowedExecutablePath</code>. Tools may add other arguments following these, and will reasonably expect standard Python command line options to be available. A complete example may look like: <div class="highlight-default notranslate"><div class="highlight"><pre>HKEY_CURRENT_USER\Software\Python\ExampleCorp\examplepy\InstallPath (Default) = "C:\ExampleDistro30" ExecutablePath = "C:\ExampleDistro30\ex_python.exe" ExecutableArguments = "--arg1" WindowedExecutablePath = "C:\ExampleDistro30\ex_pythonw.exe" WindowedExecutableArguments = "--arg1" </pre></div> </div> </section> <section id="help"> <h3><a class="toc-backref" href="#help" role="doc-backlink">Help</a></h3> Beneath the environment key, a <code class="docutils literal notranslate">Help</code> key may be created. This key is always named <code class="docutils literal notranslate">Help</code> if present and has no default value. Each subkey of <code class="docutils literal notranslate">Help</code> specifies a documentation file, tool, or URL associated with the environment. The subkey may have any name, and the default value is a string appropriate for passing to <code class="docutils literal notranslate">os.startfile</code> or equivalent. If a string value named <code class="docutils literal notranslate">DisplayName</code> exists, it should be used to identify the help file to users. Otherwise, the key name should be used. A complete example may look like: <div class="highlight-default notranslate"><div class="highlight"><pre>HKEY_CURRENT_USER\Software\Python\ExampleCorp\6C465E66\Help Python\ (Default) = "C:\ExampleDistro30\python36.chm" DisplayName = "Python Documentation" Extras\ (Default) = "http://www.example.com/tutorial" DisplayName = "Example Distro Online Tutorial" </pre></div> </div> </section> <section id="other-keys"> <h3><a class="toc-backref" href="#other-keys" role="doc-backlink">Other Keys</a></h3> All other subkeys under a Company-Tag pair are available for private use. Official CPython releases have traditionally used certain keys in this space to determine the location of the Python standard library and other installed modules. This behaviour is retained primarily for backward compatibility. However, as the code that reads these values is embedded into the interpreter, third-party distributions may be affected by values written into <code class="docutils literal notranslate">PythonCore</code> if using an unmodified interpreter. </section> </section> <section id="sample-code"> <h2><a class="toc-backref" href="#sample-code" role="doc-backlink">Sample Code</a></h2> This sample code enumerates the registry and displays the available Company-Tag pairs that could be used to launch an environment and the target executable. It only shows the most-preferred target for the tag. Backwards-compatible handling of <code class="docutils literal notranslate">PythonCore</code> is omitted but shown in a later example: <div class="highlight-default notranslate"><div class="highlight"><pre># Display most-preferred environments. # Assumes a 64-bit operating system # Does not correctly handle PythonCore compatibility import winreg def enum_keys(key): i = 0 while True: try: yield winreg.EnumKey(key, i) except OSError: break i += 1 def get_value(key, value_name): try: return winreg.QueryValue(key, value_name) except FileNotFoundError: return None seen = set() for hive, key, flags in [ (winreg.HKEY_CURRENT_USER, r'Software\Python', 0), (winreg.HKEY_LOCAL_MACHINE, r'Software\Python', winreg.KEY_WOW64_64KEY), (winreg.HKEY_LOCAL_MACHINE, r'Software\Python', winreg.KEY_WOW64_32KEY), ]: with winreg.OpenKeyEx(hive, key, access=winreg.KEY_READ | flags) as root_key: for company in enum_keys(root_key): if company == 'PyLauncher': continue with winreg.OpenKey(root_key, company) as company_key: for tag in enum_keys(company_key): if (company, tag) in seen: if company == 'PythonCore': # TODO: Backwards compatibility handling pass continue seen.add((company, tag)) try: with winreg.OpenKey(company_key, tag + r'\InstallPath') as ip_key: exec_path = get_value(ip_key, 'ExecutablePath') exec_args = get_value(ip_key, 'ExecutableArguments') if company == 'PythonCore' and not exec_path: # TODO: Backwards compatibility handling pass except OSError: exec_path, exec_args = None, None if exec_path: print('{}\\{} - {} {}'.format(company, tag, exec_path, exec_args or '')) else: print('{}\\{} - (not executable)'.format(company, tag)) </pre></div> </div> This example only scans <code class="docutils literal notranslate">PythonCore</code> entries for the current user. Where data is missing, the defaults as described earlier in the PEP are substituted. Note that these defaults are only for use under <code class="docutils literal notranslate">PythonCore</code>; other registrations do not have any default values: <div class="highlight-default notranslate"><div class="highlight"><pre># Only lists per-user PythonCore registrations # Uses fallback values as described in PEP 514 import os import winreg def enum_keys(key): i = 0 while True: try: yield winreg.EnumKey(key, i) except OSError: break i += 1 def get_value(key, value_name): try: return winreg.QueryValue(key, value_name) except FileNotFoundError: return None with winreg.OpenKey(winreg.HKEY_CURRENT_USER, r"Software\Python\PythonCore") as company_key: print('Company:', get_value(company_key, 'DisplayName') or 'Python Software Foundation') print('Support:', get_value(company_key, 'SupportUrl') or 'http://www.python.org/') print() for tag in enum_keys(company_key): with winreg.OpenKey(company_key, tag) as tag_key: print('PythonCore\\' + tag) print('Name:', get_value(tag_key, 'DisplayName') or ('Python ' + tag)) print('Support:', get_value(tag_key, 'SupportUrl') or 'http://www.python.org/') print('Version:', get_value(tag_key, 'Version') or tag[:3]) print('SysVersion:', get_value(tag_key, 'SysVersion') or tag[:3]) # Architecture is unknown because we are in HKCU # Tools may use alternate approaches to determine architecture when # the registration does not specify it. print('SysArchitecture:', get_value(tag_key, 'SysArchitecture') or '(unknown)') try: ip_key = winreg.OpenKey(company_key, tag + '\\InstallPath') except FileNotFoundError: pass else: with ip_key: ip = get_value(ip_key, None) exe = get_value(ip_key, 'ExecutablePath') or os.path.join(ip, 'python.exe') exew = get_value(ip_key, 'WindowedExecutablePath') or os.path.join(ip, 'python.exe') print('InstallPath:', ip) print('ExecutablePath:', exe) print('WindowedExecutablePath:', exew) print() </pre></div> </div> This example shows a subset of the registration that will be created by a just-for-me install of 64-bit Python 3.6.0. Other keys may also be created: <div class="highlight-default notranslate"><div class="highlight"><pre>HKEY_CURRENT_USER\Software\Python\PythonCore (Default) = (value not set) DisplayName = "Python Software Foundation" SupportUrl = "http://www.python.org/" HKEY_CURRENT_USER\Software\Python\PythonCore\3.6 (Default) = (value not set) DisplayName = "Python 3.6 (64-bit)" SupportUrl = "http://www.python.org/" Version = "3.6.0" SysVersion = "3.6" SysArchitecture = "64bit" HKEY_CURRENT_USER\Software\Python\PythonCore\3.6\Help\Main Python Documentation (Default) = "C:\Users\Me\AppData\Local\Programs\Python\Python36\Doc\python360.chm" DisplayName = "Python 3.6.0 Documentation" HKEY_CURRENT_USER\Software\Python\PythonCore\3.6\InstallPath (Default) = "C:\Users\Me\AppData\Local\Programs\Python\Python36\" ExecutablePath = "C:\Users\Me\AppData\Local\Programs\Python\Python36\python.exe" WindowedExecutablePath = "C:\Users\Me\AppData\Local\Programs\Python\Python36\pythonw.exe" </pre></div> </div> </section> <section id="references"> <h2><a class="toc-backref" href="#references" role="doc-backlink">References</a></h2> <aside class="footnote-list brackets"> <aside class="footnote brackets" id="id2" role="doc-footnote"> <dt class="label" id="id2">[<a href="#id1">1</a>]</dt> <dd>Registry Redirector (Windows) (<a class="reference external" href="https://msdn.microsoft.com/en-us/library/windows/desktop/aa384232.aspx">https://msdn.microsoft.com/en-us/library/windows/desktop/aa384232.aspx</a>)</aside> </aside> </section> <section id="copyright"> <h2><a class="toc-backref" href="#copyright" role="doc-backlink">Copyright</a></h2> This document has been placed in the public domain. </section> </section> <hr class="docutils" /> Source: <a class="reference external" href="https://github.com/python/peps/blob/main/peps/pep-0514.rst">https://github.com/python/peps/blob/main/peps/pep-0514.rst</a> Last modified: <a class="reference external" href="https://github.com/python/peps/commits/main/peps/pep-0514.rst">2025-02-01 08:59:27 GMT</a> </article> <nav id="pep-sidebar"> <h2>Contents</h2> <ul> <li><a class="reference internal" href="#abstract">Abstract</a></li> <li><a class="reference internal" href="#motivation">Motivation</a></li> <li><a class="reference internal" href="#definitions">Definitions</a></li> <li><a class="reference internal" href="#structure">Structure</a><ul> <li><a class="reference internal" href="#backwards-compatibility">Backwards Compatibility</a></li> <li><a class="reference internal" href="#company">Company</a></li> <li><a class="reference internal" href="#tag">Tag</a></li> <li><a class="reference internal" href="#installpath">InstallPath</a></li> <li><a class="reference internal" href="#help">Help</a></li> <li><a class="reference internal" href="#other-keys">Other Keys</a></li> </ul> </li> <li><a class="reference internal" href="#sample-code">Sample Code</a></li> <li><a class="reference internal" href="#references">References</a></li> <li><a class="reference internal" href="#copyright">Copyright</a></li> </ul> <a id="source" href="https://github.com/python/peps/blob/main/peps/pep-0514.rst">Page Source (GitHub)</a> </nav> </section> <script src="../_static/colour_scheme.js"></script> <script src="../_static/wrap_tables.js"></script> <script src="../_static/sticky_banner.js"></script> </body> </html>