[Python-Dev] Adding Python scripts to PATHEXT on Windows (original) (raw)

"Martin v. Löwis" martin at v.loewis.de
Tue Jul 30 19:24:49 CEST 2013

Am 28.07.13 00:36, schrieb Paul Moore:

On 27 July 2013 21:14, Steve Dower <Steve.Dower at microsoft.com_ _<mailto:Steve.Dower at microsoft.com>> wrote:

Any chance of this being made optional when installing? It provides no benefit for people who prefer to associate scripts with an editor and may be a source of confusion/complaints.

Personally, I don't know how to do this so someone else would have to -

It seems that this was settled as fine as-is; if you ever wanted to allow this to be specifically enabled, you'd have to do three things

  1. create a new "feature" in the feature tree. Your patch currently uses the "Extensions" feature (child of the default feature); you could make your feature a subfeature of Extensions.
  2. create a new "component". This should work similar to REGISTRY.path.
  3. Add a "FeatureComponents" entry saying that the "REGISTRY.pathext" component (say) belongs to the "PathExt" feature (say).

Instead of hooking the environment variable to the REGISTRY.def component, it should then go to the REGISTRY.pathext component.

The nice thing about this feature tree is that it allows convenient user configuration yet powerful scripted installation, see

http://msdn.microsoft.com/en-us/library/windows/desktop/aa368585(v=vs.85).aspx

For example, you could set the msidbFeatureAttributesFollowParent flag, which would make it be selected/unselected if the parent feature is, yet still allow it to be independent of the parent for people who really want to.

Regards, Martin

More information about the Python-Dev mailing list