[tg-trunk] Re: SelectionField.options called in ctor (backward-incompatible with 0.9a6)

2006-07-29 Thread Max Ischenko
On Jul 28, 2006, at 4:11 PM, Max Ischenko wrote: Looks like I stumbled upon another backward-incompatibility issue in 0.9a8: if options is callable it gets called at ctor time (it was not called before, unless no validator was also given). This is because it tries to guess a validator

[tg-trunk] Re: SelectionField.options called in ctor (backward-incompatible with 0.9a6)

2006-07-29 Thread Jorge Godoy
Alberto Valverde [EMAIL PROTECTED] writes: I think the best solution for this would be to avoid guessing altogether as it'll will follow the In the face of ambiguity, avoid the temptation to guess PyZen principle and make this validator default to a String if no one is given. However,

[tg-trunk] Re: SelectionField.options called in ctor (backward-incompatible with 0.9a6)

2006-07-29 Thread Alberto Valverde
On Jul 29, 2006, at 12:29 PM, Alberto Valverde wrote:I think the best solution for this would be to avoid guessing   altogether as it'll will follow the "In the face of ambiguity, avoid   the temptation to guess" PyZen principle and make this validator   default to a String if no one is given.

[tg-trunk] Re: SelectionField.options called in ctor (backward-incompatible with 0.9a6)

2006-07-29 Thread Michele Cella
Alberto Valverde wrote: On Jul 29, 2006, at 12:29 PM, Alberto Valverde wrote: I think the best solution for this would be to avoid guessing altogether as it'll will follow the In the face of ambiguity, avoid the temptation to guess PyZen principle and make this validator default to a

[tg-trunk] Re: SelectionField.options called in ctor (backward-incompatible with 0.9a6)

2006-07-29 Thread Jason Chu
On Sat, 29 Jul 2006 12:29:13 +0200 Alberto Valverde [EMAIL PROTECTED] wrote: I think the best solution for this would be to avoid guessing altogether as it'll will follow the In the face of ambiguity, avoid the temptation to guess PyZen principle and make this validator default to a