[Distutils] Script processing plugins?

[Phillip J. Eby]

At 11:53 PM 5/17/2006 -0500, Ian Bicking wrote:
>Phillip J. Eby wrote:
>>Okay, so after today's discussions I'm still not really clear on how path 
>>freezing (baking, whatever) should work for standalone setuptools.
>>Would it solve the problem for your use cases if I provided an option 
>>like "--script-wrappers=plugin1,plugin2,...", where the plugin names are 
>>entry points that would get a chance to modify the contents of generated 
>>scripts?  That way, you guys could experiment freely with your 
>>script-wrapping strategies without having to monkeypatch.  And any tools 
>>that you build which wrap easy_install can simply add the necessary 
>>setting(s) to an appropriate .cfg file.
>
>It seems weird to modify the contents of the scripts.  Can't they just get 
>passed the name of the egg and entry point, and return the full script?

No.  :)  The idea is to allow you to have *wrappers*, not to completely 
redo script generation.


>   You couldn't have multiple wrappers, but compatible wrappers seem 
> unlikely anyway.

I can envision uses for stacked wrappers rather easily, actually, since 
someone might want to write something that freezes other environment 
variables besides (effectively) PYTHONPATH, and they might want to use that 
along with one of your freezing plugins.  So, it seems wise to follow the 
"diversity rule" of Eclipse contributions, i.e. "extension points accept 
multiple extensions".