+1. Incorporating useful features from Cornice into the Pyramid core is a VASTLY superior option than having to pip install a pseudo-platform like Cornice. Pyramid should be able to stand on its own...it should not need a layer of any sort on top of it.
My view on validation: To have the most concise and efficient validation system possible, you must be able to use the same system to validate and serialize/deserialize the entire stack: view -> controller -> model (in our case, JSON requests -> Python objects -> database entries/nodes/docs/whatever). This means that your method of validation should be tailored (to some degree) to, or flexible enough to consider, what database you're using. Your validation and modelling should be quite different depending on whether you're using NoSQL or SQL, for example. I'm in the process of creating a validation system which extends Voluptous<https://github.com/alecthomas/voluptuous>to create a super concise, easy to use, extensible validation and modelling template to use with MongoDB. It's custom designed for NoSQL, which means it embraces such concepts as *informal schemas* and *lightweight validation*. I mention this because many validation systems, such as Pyramids built-in system, don't really take model philosophies into consideration, and have many conventions which are holdovers from traditional database modeling. In summary, your validation system should depend on what modeling philosophy/db you're using. -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
