This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mhammond
Recipients mhammond
Date 2009-01-27.06:02:21
SpamBayes Score 2.6574576e-09
Marked as misclassified No
Message-id <1233036195.14.0.569948424976.issue5076@psf.upfronthosting.co.za>
In-reply-to
Content
bdist_wininst installers created by py3k fail due to PySys_SetArgv and
Py_SetProgramName both being passed 'char *' strings instead of wide
strings.

The patch is against the svn trunk as currently Python 2.x and 3.x share
the same bdist_wininst stub.  The patch doesn't change the behaviour on
Python 2.x, and continues to allow the same executable stub to be
shared, as the appropriate signature is determined at runtime based on
the Python version.

The patch does not include the 2 new stub executables required
(wininst-9.0.exe and wininst-9.0-amd64.exe), but the patch *and* the new
stub executables should be merged into whatever py3k branches are
appropriate.  I've tested (pywin32) installers based on the new stub on
python 2.6 32bit, and python 3.0 32 and 64bit.
History
Date User Action Args
2009-01-27 06:03:19mhammondsetrecipients: + mhammond
2009-01-27 06:03:15mhammondsetmessageid: <1233036195.14.0.569948424976.issue5076@psf.upfronthosting.co.za>
2009-01-27 06:03:12mhammondlinkissue5076 messages
2009-01-27 06:02:25mhammondcreate