Re: API for introspecting models

2011-09-27 Thread Mathieu AGOPIAN
Hello (again), seems my previous message got eaten up, so I'll try a repost : I've done a small app that I use to inspect models, it lives here: https://github.com/magopian/django-inspect-model I'm afraid this isn't rocket science, and is probably very ugly. I'm using the "inspect" module

Re: API for introspecting models

2011-09-26 Thread Mathieu AGOPIAN
(That's when somebody jumps into the conversation and feel as if he's half naked wearing dirty underwear) Hello, just FYI, I've hacked a few lines of code that I use to have a simple way to access all the fields on a model (including m2m): https://github.com/magopian/django-inspect-model

Re : [GSoC form rendering] Weekly check-in -1.0

2011-05-13 Thread Mathieu AGOPIAN
Hello Gregor, just FYI, one of the guy from django-cms created django-sekizai, which is used just for that (injecting stuff in template blocks) : https://github.com/ojii/django-sekizai Mathieu -- You received this message because you are subscribed to the Google Groups "Django developers"

Re : Re: #1342 Allow customization of MAX_SHOW_ALL_ALLOWED. Reopen or new ticket?

2011-05-11 Thread Mathieu AGOPIAN
Just to make sure i've understood the topic here: you need to change MAX_SHOW_ALL_ALLOWED, but only for a specific model? Otherwise you could just add something like that to, say, the root urlconf: from django.contrib.admin.views import main as admin_views_main

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

2011-05-01 Thread Mathieu AGOPIAN
you think there would be much chance in having these two field types > included in the core? If so, should I create a patch for fields.py and > submit?? > > As for the MySQL strict mode, I'll submit a documentation patch, and see if > it gets accepted :) > > On Sun, May 1,

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

2011-05-01 Thread Mathieu AGOPIAN
; out entry in the settings.py file that allows you to set strict mode for all > SQL connections? Or, perhaps a documentation change, which explains easily > to the user how to do it (Kinda like the storage_engine thing > onhttp://docs.djangoproject.com/en/dev/ref/databases/#creating-your-tables) .

Re : Validate that IntegerField is a valid Signed value

2011-04-30 Thread Mathieu AGOPIAN
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

2011-04-30 Thread Mathieu AGOPIAN
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)

5-1 offer

2011-04-24 Thread Mathieu AGOPIAN
I'm pretty sure my precedent message got lost :/ I've reviewed the tickets #15833, #15885, #15886, #15887, #15891 and #15889. The latter (#15889) is my very first contribution of a patch+tests+docs, and i'd like it to be reviewed please! Thanks Mathieu

Re: Review request

2011-04-24 Thread Mathieu Agopian
My turn! I have reviewed #15885, #15886 (then closed as duplicate), #15887, #15891, and #15889. The latter, #15889 is my first code+patch+doc contribution, and i'd like it to be reviewed please. Thanks! Mathieu On Apr 22, 2:13 pm, Jacob Kaplan-Moss wrote: > On Fri, Apr