logging

Guys, Just starting using 1.3 and I have a tiny problem with logging. Too much of it! I'm running with DEBUG, but I don't want to see database queries. Quick way to mute that (not DEBUG+1 please)? Thanks What is the django way of swithing off the logging on DEBUG from the database -- You recei

RE:FW: v--.

I have a good information to share with you. A while ago,a trading company attractive to me, the price is very competitive advantage, so I bought some products. It is very exciting,very pleased when I got and saw my goods. I think you can go to see: focost.com you'll save more money in there. $--.

Re: from django import forms

http://github.com/lsbardel/django/commit/9215082052b5d0ea0d0116ddeb08345452ae5358 As I said, not great but it works. On 23 October 2010 15:26, Luca Sbardella wrote: > ups. > > the settings import is also in django.forms.models > > from django.db import connections > > I

Re: from django import forms

ups. the settings import is also in django.forms.models from django.db import connections I still strongly think django.forms should be import django.conf free at module level. I'll come up with an idea. On 23 October 2010 13:29, Luca Sbardella wrote: > I left it vague on purpo

Re: from django import forms

so, a guideline on how not to do it. The quickest way would be to put the import in the function and throw the same ImportError when accessing it without settings file available. Not nice but it would work. ciao On 23 October 2010 12:36, Luke Plant wrote: > On Sat, 2010-10-23 at 12:07 +01

from django import forms

ImportError: Settings cannot be imported, because environment variable DJANGO_SETTINGS_MODULE is undefined Hi guys, nothing to do with 1.3 awesome new features... but I'm trying to use django forms outside django (why not!). Not possible because of the above. The settings is imported in django.fo

Re: Proposal - ChoiceField.choices need to accept callable, not only list or tuple

Hi there, I've used a different approach to solve the problem. If of interest, here is the snippet http://gist.github.com/232372 for solving the the problem of a run-time ChoiceField. The choices argument is a generator (or the usual list of tuples). On 24 March 2010 06:48, Ivan Sagalaev wrote:

Re: media in ModelAdmin

Now I know the best practice. I leave it as it is. Thanks On 20 Mar, 11:49, Russell Keith-Magee wrote: > On Sat, Mar 20, 2010 at 6:43 PM, Simon Meers wrote: > >> As documented here [1], the ticket is closed when the code is > > >> committed to SVN. If you think you've met all the requirements fo

Re: media in ModelAdmin

Hi Russell, I made a couple of changes to forms.widgets in relation to your comments. Tests passed. Shall I close the ticket? (not sure about best practice) Thanks Luca On 19 Mar, 00:55, Russell Keith-Magee wrote: > On Thu, Mar 18, 2010 at 9:57 PM, Luca Sbardella > > >

media in ModelAdmin

Currently, the media object is converted to safe string in both "add_view" and "change_view" when added to the context dictionary while in "changelist_view" is not (the correct approach). Converting media to string means you cannot split css from js in templates. What I'd like to do is ... {% for

problem in modeladmin response_action

Hi there, I just switch from 1.2 beta 1 to svn version and the ModelAdmin.response_action is not working as before. For example it does not delete objects when confirming a bulk deletion. The problem seems to be in the beginning of the function if 'index' not in request.POST: return None By