Re: spyce development

Jonathan Ellis wrote:
> Well, if Spyce 2.1 does everything you want, then you're all set. But
> you're probably mailing because it does not. :)

You are right! :)

Like I can see on the 2.1 version, it has some bugs (remember my emails
for session and compression?) that break some old code and introduce
some problems on my new projects (especially that on the session)

> 
> 2.2 is mostly finished but needs more polishing to be something I'm 
> not embarassed about releasing, and I don't have the time to do the 
> polishing.  And the changes are deep enough that trying to only port 
> bug fixes back to the 2.1 branch would also take a day or two that I 
> don't have.
> 

So, if I understand correctly, some bugs are solved and also that I'm
talking about? I'll look in the next few days for see if I can send you
some patch(s) for the old version.

> I'm happy to help anyone understand the Spyce code by email or IRC (I
>  hang out on freenode #utahpython and often #sqlalchemy), but I don't
>  really have time to work on Spyce myself anymore

this is a very bad news :(
I like spyce because he has no "invasions" and doesn't teach to the
developer on how he has to wrote the code. He simple abstract and
simplify the communication+html layer that no one (first I'm here! :) )
want to know and deal with, but on the other hand, add some helps like
sessions, pool and response. Something like php (ok, don't kill me :) )
does!

> so unless someone wants to take over carrying the torch you might 
> want to consider moving to Pylons or Django.
> 

Django, for the above affirmations, it's not for me.
Pylons seem better than Django. I'll take a look, but first, I'll try
with spyce!

Ciao,
Michele

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/