[issue4636] bdist_wininst installer with install script raises exception

[STINNER Victor]

STINNER Victor  added the comment:

The distutils bdist_wininst command has been removed in Python 3.10: see 
bpo-42802.

--
nosy: +vstinner
resolution:  -> wont fix
stage: test needed -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4636] bdist_wininst installer with install script raises exception

[Dan Nicholson]

Dan Nicholson added the comment:

Right, that's what makes this difficult. If the stub exe of the target python 
was used, then it wouldn't need to care about compatibility. However, what 
you're running is the stub of the build python. So, when I distribute a 
bdist_wininst exe, it's running the stub from my python on the user's machine. 
That introduces a few compatibility issues.

1. The exe needs the same CRT version installed on the target that it was built 
with. It would fail to run immediately in this case. This does make having the 
built python be newer than the target python a little difficult.

2. The exe loads the python dll on the target machine. This requires the python 
dll to have enough compatibility for the usage of the python API in the exe of 
the build version.

3. After loading the python dll, python code is run in the target python. This 
is the problem I'm trying to solve here. The python code is embedded in the exe 
of the installer, so the compatibility with the target python has to be 
considered at build time.

The situation you're describing where the wininst of the target is run could 
maybe be made to work, but it would be a larger project.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4636] bdist_wininst installer with install script raises exception

[Éric Araujo]

Éric Araujo added the comment:

I think the exe files are specific to one Python version, so the version check 
would not be necessary.  I may be wrong though, as I’m not a windows dev or 
user, so I’m adding Mark to this issue.

--
nosy: +mhammond

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4636] bdist_wininst installer with install script raises exception

[Dan Nicholson]

Changes by Dan Nicholson :


Added file: http://bugs.python.org/file31717/wininst-9.0-compat-2.7.exe

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4636] bdist_wininst installer with install script raises exception

[Dan Nicholson]

Changes by Dan Nicholson :


Added file: http://bugs.python.org/file31715/wininst-compat-2.7.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4636] bdist_wininst installer with install script raises exception

[Dan Nicholson]

Changes by Dan Nicholson :


Added file: http://bugs.python.org/file31716/wininst-10.0-compat.exe

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4636] bdist_wininst installer with install script raises exception

[Dan Nicholson]

Dan Nicholson added the comment:

It turns out this is pretty easy to fix by just changing the stub to import 
builtins or __builtin__ depending on the python install version. Attached are 
patches that fix this for both the default and 2.7 branches.

My test case is a pure python module with an install script. I've rebuilt the 
wininst stub for both default (3.3) with VS2010 Express and 2.7 with VS2008 
Express. I then built installers and ran them in both directions: installer 
created with python-2.7 and installed into python-3.3, and an installer created 
with python-3.3 and installed into python-2.7. Both worked fine with no 
warnings.

I've attached the stubs I built in case they're helpful. 
wininst-10.0-compat.exe is the 32 bit stub for default/3.3. 
wininst-9.0-compat-2.7.exe is the 32 bit stub for 2.7.

--
keywords: +patch
nosy: +dbn
Added file: http://bugs.python.org/file31714/wininst-compat.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4636] bdist_wininst installer with install script raises exception

[Matt Wilkie]

Matt Wilkie added the comment:

I confirm this is happening with 3.2.4 from an installer generated in 2.7.4 
(64bit Win7, 32bit python): 
https://pypi.python.org/pypi/leo/4.11.devel-build-5802

--
nosy: +Matt.Wilkie

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4636] bdist_wininst installer with install script raises exception

[Éric Araujo]

Éric Araujo  added the comment:

The crash message is the same as the one in #4918; it looks like bdist_wininst 
need better error reporting.

--
assignee: tarek -> eric.araujo
stage:  -> test needed
versions:  -Python 3.0

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4636] bdist_wininst installer with install script raises exception

[Éric Araujo]

Éric Araujo  added the comment:

Can you still reproduce in 3.1 and 3.2?

--
nosy: +merwok

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4636] bdist_wininst installer with install script raises exception

[Tarek Ziadé]

Changes by Tarek Ziadé :


--
assignee:  -> tarek
nosy: +tarek

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4636] bdist_wininst installer with install script raises exception

[Thomas Heller]

New submission from Thomas Heller :

Running a bdist_wininst installer that contains a install script, with
python 3, raises an exception. This is displayed in the gui:
ImportError: No module named __builtin__
*** run_installscript: internal error 0x ***

This is probably because the bdist_wininst installer stubs (in the
Lib/distutils/command subdirectory) have not been recompiled after
changing the sources.

--
components: Distutils
messages: 77631
nosy: theller
severity: normal
status: open
title: bdist_wininst installer with install script raises exception
versions: Python 3.0

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com