Re: A setting that skips tests for thirdparty applications

2010-07-02 Thread lakin
> Thanks for the ticket and patch.  However, I for one am struggling to > understand why it is so painful to do: > >   ./manage.py test app1 app2 app3 app4 As someone who works on quite a few projects, it's painful to have to remember the exact app names for all 10 projects that I frequently work

Re: A setting that skips tests for thirdparty applications

2010-07-02 Thread John-Scott Atlakson
On Jul 2, 2010, at 7:14 PM, Luke Plant wrote: > On Fri, 2010-07-02 at 14:48 -0700, lakin wrote: >> http://code.djangoproject.com/ticket/13873 >> >> As part of a normal testing routine, I find it annoying that django >> tests ALL of the applications listed in INSTALLED_APPS. While I do >> want it

automatic model registration on contrib.admin

2010-07-02 Thread Michael Cetrulo
hi guys, I find a bit too annoying to keep my admin.py synchronized with the models in my apps and for that I've created myself a simple helper[1] which takes app names and registers all models found on each. with this I'm able to update my models when I'm developing and have them automatically ad

Re: A setting that skips tests for thirdparty applications

2010-07-02 Thread Luke Plant
On Fri, 2010-07-02 at 14:48 -0700, lakin wrote: > http://code.djangoproject.com/ticket/13873 > > As part of a normal testing routine, I find it annoying that django > tests ALL of the applications listed in INSTALLED_APPS. While I do > want it to test most of them, I rarely want it to test third

A setting that skips tests for thirdparty applications

2010-07-02 Thread lakin
http://code.djangoproject.com/ticket/13873 As part of a normal testing routine, I find it annoying that django tests ALL of the applications listed in INSTALLED_APPS. While I do want it to test most of them, I rarely want it to test third party applications. This ticket has a patch that adds a T

Re: contrib.admin:list_editable - ForeignKey Performance is O(m*n)?

2010-07-02 Thread chadc
Alright. I filed it as #13871 under contrib.admin because I do not understand the larger issue, but please update it as you see fit. Thanks, Jeremy. Ticket Link: http://code.djangoproject.com/ticket/13871 -- You received this message because you are subscribed to the Google Groups "Django deve

Re: Django and the Eyjafjallajökull eruption

2010-07-02 Thread Gregor Müllegger
By coincidence I blogged last night right about read permissions how you need them [1]. My solution is like what you explain as "dirty hack" ;) It provides this functionality: * Every user with is_staff=True can read all objects in the admin. * View permission means: You can see the usual change

Re: Django and the Eyjafjallajökull eruption

2010-07-02 Thread Josh Ourisman
All of this stuff is absolutely doable, and in fact I've implemented much of it myself. I don't know if it will cover everything you want, but I've written up some of my most similar Django Admin hacks (I've done quite a bit over the years...) on my blog here: http://joshourisman.com/2009/10/15/dja

Re: Django and the Eyjafjallajökull eruption

2010-07-02 Thread Ramsey D'silva
I believe all the things you mentioned, can be done! It's just a matter of finding a competent developer. Cheers! On 2-Jul-10, at 7:03 AM, Helgi Borg wrote: Remember the Eyjafjallajökull eruption that stopped air traffic over parts of Europe? The staff at the Icelandic Meterological Office

Django and the Eyjafjallajökull eruption

2010-07-02 Thread Helgi Borg
Remember the Eyjafjallajökull eruption that stopped air traffic over parts of Europe? The staff at the Icelandic Meterological Office had a seriously busy time the first days of the eruption. When I arrived at work the first morning, I quickly realized that we needed a simple msg-software so the t

Re: Cleanup Signal

2010-07-02 Thread Gregor Müllegger
On 2 July 2010 05:44, hcarvalhoalves wrote: > Besides that, I don't see the need for anything to integrate inside a > single "clean" command. It's not like the management commands provided > by Django are hooks, you can and should be making yours for each > specific need. My intention was to make

Re: Cleanup Signal

2010-07-02 Thread Dougal Matthews
On 2 July 2010 05:44, hcarvalhoalves wrote: > Besides that, I don't see the need for anything to integrate inside a > single "clean" command. It's not like the management commands provided > by Django are hooks, you can and should be making yours for each > specific need. I agree with this. Ma