Re: Dallas Django sprint 4/18 - 4/19 at CoHabitat

Count me in... G On Apr 7, 10:54 am, Jeremy Dunck wrote: > We've firmed up the Dallas Django sprint plans: > > Django 1.1 is around the corner, but there are lots of bugs left to > squash. Come meet the other Django people around Dallas and check out > Cohabitat, the great coworking spot in upt

Re: Test integration with coverage

On 4/7/2009 11:25 AM, Kevin Kubasik wrote: > I actually proposed this as part of my GSoC project. I think there is > enough interest that basic coverage support could be seen in core. I agree and have had some quick emails with Jacob about this. I think there's a way to make this a stand-alone pa

Re: Test integration with coverage

Absolutely! I actually proposed this as part of my GSoC project. I think there is enough interest that basic coverage support could be seen in core. My research turned up figleaf, which seemed like a better fit (but its an external dependency, and I'm not sure of the django policy on this, especial

Test integration with coverage

I did a fair amount of work last week with ``coverage.py``. I came up with a pretty flexible system which suited my own development needs but is probably useful to a lot of people out there. I noticed there's already a ticket open for this: I've commented there as well. I was able to run ``runt

Re: i18n for permissions names in auth

On Tue, Apr 7, 2009 at 8:55 AM, Vinicius Mendes wrote: > I was thinking that it would be a good feature if the names of the auth > permissions could be internationalizated. For example, instead of storing > 'Can add user' in database, can store something like 'Can add > %(model_verbose_name)s'. A

Dallas Django sprint 4/18 - 4/19 at CoHabitat

We've firmed up the Dallas Django sprint plans: Django 1.1 is around the corner, but there are lots of bugs left to squash. Come meet the other Django people around Dallas and check out Cohabitat, the great coworking spot in uptown. We'll start Saturday, April 18, 2009 at 9:00am through Sunday,

i18n for permissions names in auth

I was thinking that it would be a good feature if the names of the auth permissions could be internationalizated. For example, instead of storing 'Can add user' in database, can store something like 'Can add %(model_verbose_name)s'. And then internationalize it for the user and put the model name i

Re: FileField truncation/exception on path string overflow (#9893)

On Tuesday 07 April 2009 11:45:54 akaihola wrote: > Continuing the discussion from http://code.djangoproject.com/ticket/9893 > here. > > Summary: FileField and ImageField have a problem when the length of > the file path relative to MEDIA_ROOT exceeds 100 characters (or the > overridden max_length

Re: add_constraint=False on relation fields

On Tuesday 07 April 2009 05:52:22 Richard Smith wrote (edited to correct top-posting): > On Mon, Apr 6, 2009 at 6:15 PM, Malcolm Tredinnick wrote: > > > > On Mon, 2009-04-06 at 04:53 -0700, Adys wrote: > > > I made a small patch for my local Django install to be able to precise > > > add_constrai

FileField truncation/exception on path string overflow (#9893)

Continuing the discussion from http://code.djangoproject.com/ticket/9893 here. Summary: FileField and ImageField have a problem when the length of the file path relative to MEDIA_ROOT exceeds 100 characters (or the overridden max_length). I get a 500 server error (with PostgreSQL) and the origina

Re: A bunch of little fixes

Malcolm Tredinnick wrote: > I just did a random sampling of four tickets and #10504 is a feature > addition, it can wait until 1.2 (and maybe even then isn't actually > something to do, since render_to_response is a *shortcut*, not a > complete replacement). true, not really a problem here > #106