A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-September/048744.html below:

[Python-Dev] Install-on-first-use vs. optional extensions

[Python-Dev] Install-on-first-use vs. optional extensions"Martin v. Löwis" martin at v.loewis.de
Thu Sep 9 20:29:26 CEST 2004
Garth wrote:
> Couldn't you conditionally run  RegisterExtensionInfo?

This is what I currently do (see msi.py:build_database).
Unfortunately, it doesn't work: Installer then unconditionally
runs UnregisterExtensionInfo first, which removes any old
extension information before installing a new one.

Now, this could also be made conditional, although defining
the condition is difficult: If the user changes the extension
from "installed" to "absent", UnregisterExtensionInfo *should*
run. In any case, uninstalling the entire package (i.e.
executing the toplevel REMOVE action) doesn't run the
InstallExecuteSequence (I believe), which further complicates
issues.

I've played with a number of options, and could not make it
to work. I have given up now, but if you find a solution,
please let me know.

Regards,
Martin
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4