[PEAK] Breaking up PEAK

[Phillip J. Eby]

At 11:44 AM 5/30/2005 +0300, Niki Spahiev wrote:
>>Primary Frameworks
>>------------------
>>PyProtocols - dispatch, protocols
>>PEAK-Components - All of the core, including binding, naming, config, 
>>model, and util (dependencies=PyProtocols)
>>PEAK-Running - running (dependencies = PEAK-Components
>>PEAK-Events - events (dependencies = PEAK-Running, ZConfig (for EventDriven))
>
>IMHO PEAK-Events should be usable without PEAK-Running.
>Quick grep shows that only twisted_support really uses peak.running.
>Can this dependence be inverted?

Eggs can have optional dependencies, so we could make it so that you have 
to request 'PEAK-Events[Twisted]' in order for the dependency to Running to 
apply.  There will probably be lots of such optional dependencies in the 
overall system.