Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 10:17:27 +0100] rev 4397
should not raise KeyError if key's missing
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 10:00:58 +0100] rev 4396
choices function should now take the field as argument
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 10:00:35 +0100] rev 4395
cleanup
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 10:00:19 +0100] rev 4394
missing import
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:59:55 +0100] rev 4393
systematically call bool on BooleanField values
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:59:13 +0100] rev 4392
by default this is not the widget responsability to turn empty string into None,
move this behaviour to the field.
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:57:53 +0100] rev 4391
ensure we get a correct key
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:57:16 +0100] rev 4390
test fixes
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:56:58 +0100] rev 4389
useless, same as test_nonregr_eetype_etype_editing
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:56:16 +0100] rev 4388
[forms] propagate aguments given to .vocabulary to .choices if it's a callable.
So we can properly uses vocabulary(limit=xxx) in places where we used to call
.choices(limit), since field.choices is not meant to be accessed directly.
Also, document expected behaviour for custom choices method for relation fields.