Issue 935091: bdist_winist post-install script fails on non-admin Python (original) (raw)

Issue935091

Created on 2004-04-14 17:54 by davidhandy, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg20506 - (view)	Author: David R. Handy (davidhandy)	Date: 2004-04-14 17:54
Python version 2.3.3 Windows 98 If you install Python on Windows, and you selected a "Non Admin" install, then later on when you run any distutils-created installer that has a post-install script, the post-install script will not run. This in turn causes shortcuts to not be created, skips additional install steps, etc. The reason for this is pretty simple: a non-admin install of Python puts python23.dll in the C:\Python23 directory instead of in C:\WINDOWS\SYSTEM (or the equivalent on your version of windows). The extractor stub used by bdist_wininst does a simple LoadLibrary(), with no path information, to get python23.dll. This only looks in the current directory or in the PATH. What the extractor stub program ought to do in this case is a LoadLibrary() giving the full path (i.e. C:\Python23\python23.dll) since the Python installation directory is known.
msg20507 - (view)	Author: Thomas Heller (theller) *	Date: 2004-05-11 15:16
Logged In: YES user_id=11105 This is already fixed in the release23-maint branch, so it should be fixed in Python 2.3.4. I will port this to the trunk later.
msg20508 - (view)	Author: Mark Hammond (mhammond) *	Date: 2004-07-01 23:52
Logged In: YES user_id=14198 I can't repro this on the trunk at the moment - a non-admin install of Python allowed my non-admin user to correctly install an extension with a post-install script. The log of install.c shows Thomas did it in revision 1.4, so I'm closing this as fixed.