Agree. And we don't even need to port TG as a whole at the beginning. Porting SQLObject to Jython could deliver value to Java/Jython  community and attract enough attention.

Just my $0.02.

On 11/18/06, Frank Wierzbicki <> wrote:
> It's sounding like TG might be the better option. You guys are the
> pythonistas, so obviously you'd know better than me. I'd definitely say
> making the target something webby and CRUDdy would be the best focus,
> and I'll reiterate why:
I think this is a very good idea, at least for 2.3 development (2.2
should stilll concentrate exclusively on releasing since it is so
close).  I think TG probably is the easiest, since it is more easily
developed incrementally.  We might also consider Twisted (using Alan
Kennedy's select implementation )

And of course Django is a nice target as well.  We probably don't have
to target just one app.  I'm pretty sure TG uses SqlObject, and about a year ago a tried SQLObject with
Jython and had some success with simple CRUD.


Take Surveys. Earn Cash. Influence the Future of IT
Join 's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
Jython-dev mailing list