Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Spyce v1.1.39 released 25 Aug 2002
Get it at:
After a long hiatus, a rather big release...
Biggest changes documented at:
Partial change log:
modified how filter module injects itself into output stream
added response.addFilter() to allow piped functionality
on the output stream, modules can insert write, writeStatic,
writeExpr, flush and clear handlers
added compress module for dynamic compression functionality
compress module documentation
renamed filter module to transform (name conflict with Python builtin)
sys.path forced to be absolute before changing directory in CGI mode
bugfix - spyce path trimmed to just filename when directory changed for
bugfix - spyce web server closes sockets
spyce can now run as a (proxy) web server
spyce -l [-p port] <server root>
spyceDone exception to stop spyce processing
raise spyceDone, see gif.spy, fileupload.spy examples
not needed with spyceDone functionality
cPickle used in session module
improved session serialization performance
redirect.externalRefresh now has url= in string
internal redirect fixed
bug fix - consecutive compact line removal now possible
examples added: hello2.spy, form.spy
handle ISINDEX CGI queries that have extra command-line parameters
Status CGI header used for spyce redirect return codes
bug - fixed cgi chdir in case of local directory
request - invoke spyce engine programmatically with spyce string
source tarball does not contain extra CVS junk
fixed apache config bug in windows installer
Here it is ! I started playing again with spyce !
I would like to have more information on the 'include' module.
it seems that the include directive diverge from the include module by that
the directive it interpreted at compile time, and the module at runtime (if
we can speak of runtime and compile time).
so, a script included by the include module seems not inherit the behavior
from it's parent: like a specified compression, a declared stdout module...
so, do I have to repeat the 'module' directives in the included file ?
btw, i used the compress module. it's fine, but missing one other function:
compress.lines(), to remove EOLs so that there is no more spaces. Rimon,
beware if you want to implement that, i think you will have to replace the
EOLs by a spaces, not only strip them (EOLs are whitespaces).
also, how does the compress module behave with <PRE> tags (and the compact
directive too) ? i think we will have to abandon any behavior with the PRE
tag, because of CSSs. there is a CSS selector called 'white-space' which if
set to the value 'pre' allows any html tag to bahave like PRE. so I don't
think you will be able to parse any css, because it would be a useless time
consuming operation. this have to be thought...