➜
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.
Created on 2012-03-06 18:18 by vinay.sajip, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Messages (4) | |||
|---|---|---|---|
| msg155030 - (view) | Author: Vinay Sajip (vinay.sajip) *  |
Date: 2012-03-06 18:18 | |
I built an MSI for Python 3.3 on Windows 7 and installed from it - the resulting installation seems to work OK in that it passes all tests except test_tcl (intermittent failure). However, when I uninstall, python33.dll is left behind in System32. If I rebuild Python and the MSI after some changes and reinstall, the old python33.dll is not overwritten with the new one. |
|||
| msg155038 - (view) | Author: Martin v. Löwis (loewis) * |
Date: 2012-03-06 21:55 | |
I guess this is a misconfiguration for your system. This DLL is reference-counted, and you must have arranged the reference count to be >1 somehow. Inspect the MSI log for details. |
|||
| msg155040 - (view) | Author: Vinay Sajip (vinay.sajip) * |
Date: 2012-03-06 22:36 | |
Yes, the refcount was 1 after uninstallation - possibly it's been like that for a long time. I'll close the issue, but one thing occurs to me - isn't the DLL's version resource updated when you rebuild? Why wouldn't the newer version in an MSI being installed overwrite the older one in Windows\System32? |
|||
| msg155041 - (view) | Author: Martin v. Löwis (loewis) * |
Date: 2012-03-06 23:32 | |
The version number is not changed on every rebuild, only when patchlevel.h changes. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:27 | admin | set | github: 58421 |
| 2012-03-06 23:32:35 | loewis | set | messages: + msg155041 |
| 2012-03-06 22:36:44 | vinay.sajip | set | status: open -> closed resolution: not a bug messages: + msg155040 |
| 2012-03-06 21:55:12 | loewis | set | messages: + msg155038 |
| 2012-03-06 18:18:35 | vinay.sajip | create | |