I thought it was silly at first, but then found it easier on the eyes and
quicker to confirm what's enabled. Still, requesting a change to the core
language/library through additional code (with the inevitable introduction
of more bugs) in order to support some syntactic sugar that really doesn't
hi everyone,
I would like to participate in GSoC 2013 and was thinking about taking part
in the NotAliens development and SQLAlchemy Colander projects. Is there any
simple bugs that a novice to python like me would be able to fix so that I
can get a better understanding about the code base
he
--
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To unsubscribe from this group and stop receiving emails from it, send an email
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to
:) I'd imagine we all do, but that brings up an interesting point. This
would obviously be most seen in .py files. One can just imagine projects
w/ various libraries from different third parties with different coding
standards with check marks in some modules or even in some functions in the
same
:) I'd imagine we all do, but that brings up an interesting point. This
would obviously be most seen in .py files. One can just imagine
projects w/ various libraries from different third parties with
different coding standards with check marks in some modules or even in
some functions in the
On 04/18/2013 09:05 PM, Chris Rossi wrote:
Well, the card_num schema node is going to be a child, most likely, of a
mapping schema node. You could put the validator there.
Chris
Something like this maybe:
class CreditCardSchema(colander.Schema):
card_num =
That's exactly what I needed! Thanks guys!
On Apr 18, 2013 5:23 PM, Mariano Mara mariano.m...@gmail.com wrote:
On 04/18/2013 09:05 PM, Chris Rossi wrote:
Well, the card_num schema node is going to be a child, most likely, of a
mapping schema node. You could put the validator there.
Chris
