[issue4918] Windows installer created with Python X.Y does not work with Python X.Y+1

[Mark Lawrence]

Mark Lawrence added the comment:

Can this be closed as history with so many changes having been made to the 
installer for 3.5?

--
nosy: +BreamoreBoy, paul.moore, steve.dower, tim.golden, zach.ware
versions: +Python 3.6 -Python 2.7, Python 3.4

___
Python tracker 

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

[issue4918] Windows installer created with Python X.Y does not work with Python X.Y+1

[eryksun]

eryksun added the comment:

There haven't been any fundamental changes to bdist_wininst in years, and 
bdist_wheel has mostly replaced it nowadays. 

I'm fairly certain this issue was fixed by Mark Hammond's fix for issue 4566. 
Just to be certain, I updated the code to use print as a function and used 3.4 
to build "Simple-Python 3.4.3.win-amd64.exe". I installed this to 3.5, and the 
post-install script ran successfully. So I'm re-tagging this issue for versions 
2.7 and 3.2 and closing it as a duplicate.

In summary, Python built with VS 2008 needs an activation context for the CRT 
assembly, which is required to load msvcr90.dll. Normally this comes from the 
application executable, such as python.exe. But when Python is embedded, it may 
be the case that the application lacks the required activation context (e.g. a 
bdist_wininst installer created by Python 2.5). Mark Hammond's fix works around 
this problem by saving and reusing the activation context from when the Python 
DLL was loaded. This activation context is based on the DLL's resource #2 
manifest, which includes the CRT assembly.

One remaining problem for embedding Python 2.7 is accessing msvcr90.dll via 
ctypes. But it's ctypes! Just dynamically create an activation context.

--
nosy: +eryksun
resolution:  -> duplicate
status: open -> closed
superseder:  -> 2.6.1 breaks many applications that embed Python on Windows
versions: +Python 2.7, Python 3.2 -Python 3.5, Python 3.6

___
Python tracker 

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

[issue4918] Windows installer created with Python X.Y does not work with Python X.Y+1

[Mark Lawrence]

Changes by Mark Lawrence breamore...@yahoo.co.uk:


--
components:  -Distutils2
nosy: +dstufft
versions: +Python 3.4, Python 3.5 -3rd party, Python 3.2, Python 3.3

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

[issue4918] Windows installer created with Python X.Y does not work with Python X.Y+1

[Éric Araujo]

Éric Araujo mer...@netwok.org added the comment:

Thanks, keeping it open.  If I manage to get a VM set up I will see if this is 
reproducible.

--
components: +Distutils2
nosy: +alexis
title: Windows installer created with Python 2.5 does not work with Python 
2.6.1 - Windows installer created with Python X.Y does not work with Python 
X.Y+1
versions: +3rd party, Python 2.7, Python 3.2, Python 3.3

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