On Fri, Jun 25, 2010 at 12:40 PM, Wichert Akkerman wich...@wiggy.net wrote:
On 6/25/10 16:50 , Lukasz Szybalski wrote:
django-lazysignup 0.1.2
django-lockdown 0.1.1
django-paranoid-sessions 0.2.0
grokproject 2.0.1
So unfortunately the
Topic :: Internet :: WWW/HTTP :: WSGI :: Middleware
On Wed, Jun 23, 2010 at 10:40 PM, Chris McDonough chr...@plope.com wrote:
On Wed, 2010-06-23 at 22:28 -0500, Lukasz Szybalski wrote:
repoze.what-pylons shows up under turbogears category. If it was
changed to turbogears2 then it would show up under tg2? Not sure if it
actually works with tg1?
I think this is maybe a little backwards.
Many, many repoze things will work in turbogears 2 (almost all repoze
middleware such as repoze.who and repoze.tm2 as well as libraries such
as deform, colander, venusian, etc). But they'll also work fine in any
other WSGI framework too, so there's
Wichert said:
Are we already using the Topic :: Internet :: WWW/HTTP :: WSGI ::
Middleware classifier? Everything in that category should work fine
with turbogears and the classifier is nicely generic.
+1.
If someone creates a WSGI-related library whose target is TG, they should add
the
repoze.what-pylons shows up under turbogears category. If it was
changed to turbogears2 then it would show up under tg2? Not sure if it
actually works with tg1? I'm only using keywords.
If you say that all repoze projects will work with tg2, then I could
add repoze to one of the categories.
Let
