On Sep 9, 2010, at 12:34 PM, Michael van Tellingen wrote: > I've been using pylons for a few years now and never had the need (or wish) > to use either webhelpers or formencode. (To be honest the only need for > webhelpers sometimes is the paginate module, which is imo unfortunately moved > to the webhelpers package). Looking through the source of pylons it should be > relatively easy to drop the dependencies on both of the modules. The > reasoning behind this is that it makes pylons a bit leaner and deployment > easier. If you do actually need them they are easily installable via pip > install, right ? :-) > > My proposal is to move the formencode decorators in pylons.decorators to the > webhelpers module. > > I would like to do the work but I first want to know if there are any > objections to it
The main issue is the amount of dependencies on the @validate decorator in Pylons. I think moving it to webhelpers.pylonslib would make sense, and I can put a try/except around importing it back from there in Pylons, so that if you do have webhelpers installed, its still there. But that way the webhelpers dependency can be removed. The plan for the next release of Pylons is that integration with formencode would be done by another package, an official Pylons extension package that provides helpers specifically for using formencode with Pylons. This would also pave the way for extensions that integrate other solutions with Pylons better, like a deform/wtforms/etc integration library. Cheers, Ben -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-disc...@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
