[TIP] twill spring (Re: Everybody wants a pony!)

[C. Titus Brown]

On Wed, Apr 01, 2009 at 07:48:15AM -0500, Olemis Lang wrote:
-> On Tue, Mar 31, 2009 at 10:58 PM, C. Titus Brown <ctb at msu.edu> wrote:
-> > On Tue, Mar 31, 2009 at 12:37:59PM -0500, Olemis Lang wrote:
-> > -> On Tue, Mar 31, 2009 at 11:39 AM, C. Titus Brown <ctb at msu.edu> wrote:
-> > -> > On Tue, Mar 31, 2009 at 11:15:32AM -0500, Olemis Lang wrote:
-> > -> >
-> > -> > -> there are plans
-> > -> > -> to remove wsgi_intercept ...
-> > -> >
-> > -> > wsgi-intercept is now a separate package on Google Code,
-> > -> >
-> > -> > ? ? ? ?code.google.com/p/wsgi-intercept
-> > -> >
-> > -> > maintained by Kumar.
-> > ->
-> > -> Well ... I'll be waiting the first release ...
-> >
-> > Sorry, I should have said: that takeover happened a while ago, and Kumar
-> > has fixed bugs while keeping the interface the same -- so I feel
-> > comfortable letting twill just import it. ?So we're making that change
-> > for twill 0.9.2.
-> >
-> 
-> Which means that wsgi_intercept will still be there (as a dependency
-> ... isnt it ? ) but is distributed separately so that people
-> interested on using it can install it instead of the whole twill
-> functionality ...

Yes.

-> PD: This reminds me a recent discussion in pydev list about apps |
-> libs | frameworks packaged in pieces vs ?all in one? distribution ...
-> IMHO this is an example where splitting wsgi_intercept makes sense ...

I think a good split is, packages that are explicitly for hardcore
developers (what the heck are you doing using wsgi_intercept if not? ;)
can rely on a package manager.

-> BTW ... I also think that a mechanism to put multiple pks into a
-> single one would be beneficial for Py ... similar to e.g. JARs inside
-> EARs, WARs for Java ... ;) ... or better ... more Py-super-Tonic ...
-> :o)

I'm Not Getting Involved.  No Comment.

;)

cheers,
--titus