##// END OF EJS Templates
dispatch: do not close stdout and stderr, just flush() instead...
dispatch: do not close stdout and stderr, just flush() instead Since 3a4c0905f357 "util: always force line buffered stdout when stdout is a tty", we have two file objects attached to the same STDOUT_FILENO. If one is closed, the underlying file descriptor is also closed, and writing to the other file object would crash the Python interpreter in a hard way, at least on Windows. So, it seems safer to not close the standard streams. This also matches the behavior of the default sys.stdout/stderr.close(), which never close the FILE* streams in C layer. https://hg.python.org/cpython/file/v2.7.13/Python/sysmodule.c#l1401

File last commit:

r17251:98166640 stable
r32687:12941a78 default
Show More
README.txt
31 lines | 1.4 KiB | text/plain | TextLexer
Steve Borho
Add WiX installer scripts to contrib/wix
r10502 WiX installer source files
==========================
The files in this folder are used by the thg-winbuild [1] package
building architecture to create a Mercurial MSI installer. These files
are versioned within the Mercurial source tree because the WXS files
must kept up to date with distribution changes within their branch. In
other words, the default branch WXS files are expected to diverge from
the stable branch WXS files. Storing them within the same repository is
Mads Kiilerich
help: fix some instances of 'the the'
r17251 the only sane way to keep the source tree and the installer in sync.
Steve Borho
Add WiX installer scripts to contrib/wix
r10502
The MSI installer builder uses only the mercurial.ini file from the
contrib/win32 folder, the contents of which have been historically used
to create an InnoSetup based installer. The rest of the files there are
ignored.
The MSI packages built by thg-winbuild require elevated (admin)
privileges to be installed due to the installation of MSVC CRT libraries
Adrian Buehlmann
contrib/wix: MSVC CRT libraries are installed in WinSxS...
r10503 under the C:\WINDOWS\WinSxS folder. Thus the InnoSetup installers may
still be useful to some users.
Steve Borho
Add WiX installer scripts to contrib/wix
r10502
To build your own MSI packages, clone the thg-winbuild [1] repository
and follow the README.txt [2] instructions closely. There are fewer
prerequisites for a WiX [3] installer than an InnoSetup installer, but
they are more specific.
Direct questions or comments to Steve Borho <steve@borho.org>
[1] http://bitbucket.org/tortoisehg/thg-winbuild
[2] http://bitbucket.org/tortoisehg/thg-winbuild/src/tip/README.txt
[3] http://wix.sourceforge.net/