windows standard [was: PEP 365 (Adding the pkg_resources module)]
Terry Reedy
The standard (and to me, preferable) way of dealing with such things is to have an 'installation manager' that can reinstall as well as delete and that has a check box for various things to delete. This is what Python needs.
Paul Moore:
I'd dispute strongly that this is a "standard". It may be preferable, but I'm not sure where you see evidence of it being a standard.
When I install a large program (such as developer tools, or python itself) on Windows, I expect a choice of "default" or "custom". When I choose custom, I expect a list of components, which can be chosen, not chosen, or mixed (meaning that it has subcomponents, only some of which are chosen). The whole thing only shows up once in Add/Remove programs. If I select it, I do get options to Change or Repair. These let me change my mind on which subcomponents are installed. If I install python and then separately install Zope, it may or may not make sense for Zope to be listed separately as a "program" to Add or Remove. It does not make sense (to me anyhow) have several individual packages within Zope each listed independently at the Windows level. (Though, to be fair, many (non-python) applications *do* make more than one entry.) -jJ
"Jim Jewett"
On 24/03/2008, Terry Reedy
| If I install python and then separately install Zope, it may or may | not make sense for Zope to be listed separately as a "program" to Add | or Remove.
Neither Paul nor I defined 'add-on', but I would be willing to call Zope/Plone something more than that, preferably with its own multi-option entry.
Fair comment. I'd agree that Zope/Plone are probably more than an add-on. Actually, we agree - *if* you accept that my definition of "add-on" excludes anything you download separately, which has its own installer - which is what a bdist_wininst exe is. Of course, conversely, if all Python packages are add-ons (and so have their own "internal" means of installing - easy_install, for argument's sake - and listing/uninstalling - the mythical "new" package manager) then they shouldn't have add/remove program entries (any more than each MS Office option should). The purist in me says you can't have it both ways. But practicality says it's not a major issue (as long as there's *one* option that covers everything, no matter how it's installed). Personally, my only concern is having a single tool that can manage *all* of my non-core Python packages. (One ring to rule them all, and all that :-)) I have that at the moment, by refusing to use easy_install and eggs. But it's getting harder to do that, so this thread, for me, is about finding a better option. Paul.
participants (3)
-
Jim Jewett -
Paul Moore -
Terry Reedy