It doesn't have modern logicįor finding the Python 2.7 toolchain.
Py2exe's setup.py doesn't use setuptools. Path ,īuild files will be placed in ``build_dir``. manifest' % version ),ĭef build ( source_dir : pathlib. Print ( 'found candidate VC runtime: %s ' % p )
environ ) / 'WinSxS'Ĭandidates = sorted ( p for p in os. """Finds Visual C++ Runtime DLLs to include in distribution.""" Import platform, sys print("%s:%d" % (platform.architecture(), sys.version_info))ĭef find_vc_runtime_files ( 圆4 = False ): # This script automates the building of the Inno MSI installer for Mercurial. # GNU General Public License version 2 or any later version.
# This software may be used and distributed according to the terms of the # build.py - Inno installer build script. The readme.txt file has been renamed to readme.rst and overhauled Python projects should be using Python 2 in 2019 if they have
It is brand new and independent code and I don't believe new The new script and support code is written in Python 3 because The set of files is small and their presence should be harmless.
We include the docutils package (it is getting picked up as a dependency somehow).We include a different set of files for the distutils package.I'm not sure why these aren't present in the existing installers. We include the urllib3 and win32ctypes packages (which are dependencies of dulwich and pywin32, respectively).pyc files (I'm not sure why these are missing from the existing installers). pyc files for dulwich, keyring, and pygments due to us using the latest versions of each. kernelbase.dll and msasn1.dll are missing.The set of api-ms-win-core-* DLLs is different (I suspect this is due to me using a different UCRT / Windows version).add_path.exe is missing (this was removed a few changesets ago).The produced installer creates a Mercurial installation withĪ handful of differences from the existing 4.9 installers Python and ISCC binary and it takes care of the rest. You don't need any additional configįiles: just launch the script, pointing it at an existing The script takes care of downloading all the Pythonĭependencies in a secure manner and manages the buildĮnvironment for you.
Windows 10 SDK, and Inno tools) installed, it "just works." With all the proper system dependencies (the VC++ toolchain,
When run from a fresh Mercurial source checkout Visual C++ environment configured) takes care of producing an The new script (which must be run from an environment with the Largely automate the building of the installer. Of the Inno installer by introducing a Python script to This commit attempts to improve the state of reproducibility The official Inno installer build process is poorly documented.Īnd attempting to reproduce behavior of the installer uploaded