Re: Re : Validate that IntegerField is a valid Signed value

Hey Mathieu, Thanks for taking the time to reply. I'm starting to see now why the core devs are reluctant to modify IntegerField. I'm wondering if maybe Django should have a SignedIntegerField and UnsignedIntegerField as part of the core (for those that wish to have enforced 32-bit integers),

Re : Validate that IntegerField is a valid Signed value

Hello, I'm afraid there isn't such a thing as "a valid signed value", if we're still talking about "size wise". For django (python), the integer you gave in the ticket is perfectly valid. Here's a way for you to check that : >>> s = '351760125423456632454565345363453423453465345453' >>> int(s)

Re : Validate that IntegerField is a valid Signed value

Hello, I'm afraid there isn't such a thing as "a valid signed value", if we're still talking about "size wise". For django (python), the integer you gave in the ticket is perfectly valid. Here's a way for you to check that : >>> s = '351760125423456632454565345363453423453465345453' >>> int(s)

Validate that IntegerField is a valid Signed value

http://code.djangoproject.com/ticket/15923#comment:13 Currently, Django doesn't validate if a value on an IntegerField is indeed a valid signed value. Could someone please confirm (in others such as CharField) if value validation is left for the database to decide (for example, string length,

Re: [5-for-1] Review request

Hello, I would like a core dev's opinion on #11555. The tickets I reviewed are listed here: http://myks.org/stuff/django_5-for-1.txt Thanks, -- Aymeric Augustin. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group,

Re: Feature request: log capture during testing

Have you tried Nose ? http://somethingaboutorange.com/mrl/projects/nose/1.0.0/ https://github.com/jbalogh/django-nose/commits/master I think it captures the logs quite well ... On Apr 29, 10:20 pm, Jody McIntyre wrote: > Now that Django has logging support using the