On Nov 19, 7:32 pm, Mike Orr <sluggos...@gmail.com> wrote: > We can clone django-forms, but we definitely can't depend on Django. > That would make poor Noah throw himself off one of the Northern > California cliffs.
Ha! It'd be a good exercise to pull out django forms, if for no other reason than so that I don't have to require django in its entirety in my own projects. I was actually contacted a couple of days ago by someone who wanted to use that django-pylons forms adapter with AppEngine, but he couldn't because AppEngine has a file limit and he didn't have enough room to include Django outright. If such a fork turns out to be useful beyond that, that's a bonus. If not, nothing's lost. Maybe tomorrow I'll try to yank out django.forms and see how much Django code gets pulled along with it. (I haven't seen anyone do this yet, but I'm surprised if no one has. I don't see anything on github or mercurial at first glance though.) I think Ben's thoughts on depreciating @validate would be the best for pylons in the long run. I think it'd be fruitless to try to fix it at this point. Marcus -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=.
