Ticket #133 (defect)
Opened 4 years ago
Last modified 3 years ago
Upgrade XyaptuFilter to CherryPy-2.1
Status: closed (fixed)
| Reported by: | rboerma | Assigned to: | rboerma |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | CherryPy code | Keywords: | filters |
| Cc: |
Actually, I agree with lawouach: this shouldn't be packaged with CP. Changing the title of this ticket and removing it from "cherrypy-2.1" milestone.
Change History
06/10/05 20:14:02: Modified by fumanchu
06/11/05 18:15:28: Modified by lawouach
I am not at all for adding templating filters into the standard set of filters. No offense remco ;)
The problem is that if we start packaging CP with a tamplating filter, people might believe this is the official choice of the CP team.
This is not good. CP has always been templating ltool independant and should stay like that.
06/13/05 12:24:42: Modified by JosYule
- keywords set to filters.
I'm nutral on including it in CP, but i would like to see a version that works with 2.1.
06/20/05 06:12:37: Modified by rdelon
- summary changed from Include XyaptuFilter in the distribution to Upgrade XyaptuFilter to CherryPy-2.1.
- description changed.
- milestone deleted.
06/23/05 10:41:05: Modified by rboerma
Lawouch, i'll rest my case on the inclusion and do whatever a meeting wants ;)
Can anyone please write a bug report here?
08/21/05 12:10:06: Modified by rboerma
- status changed from new to closed.
- resolution set to fixed.
fixed, see XyaptuFilter? and the 1.0.0 version attached.
As noted, this version works with cp2.1, but doesn't use the new config stuff.
It needs to be upgraded to 2.1 now. Several people have requested that on IRC.