> CP filters is one area where we knew there would be breakage. It may
> be possible to make a CP3 tool that emulates the filter interface.
> That is the kind of thing that is best driven by someone who needs
> that backwards compatibility.
I think what we can offer is a very simple way to upgrade your filters
to tools. You can even use the same code most of the time.
Here's the ultra-brief description of how to do it from the cherrypy 3 docs:
Rewriting filters as tools is a fairly straightforward operation. If
your filter only has one method, pull it out of the class and rename
it to say what it *really* does (like "gzip" or "staticfile"). Then,
make a Tool for it like so: cherrypy.tools.mytool =
cherrypy.Tool('before_handler', mymodule.myfunc).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---
