Re: dbsettings, and user configurable app settings

For PyLucid i have made http://code.google.com/p/django-dbpreferences/ """ A django app defines a form with initial values. The form cleaned data dict would be stored serialized into the database. The app can easy get the current preference dict and the user can easy edit the values in the django

Manage CSS/JS files in admin views.

I notice that jQuery comes into django with http://code.djangoproject.com/changeset/12297 In my own project i already have jQuery saved in my own media dir and i added in my own /admin/base_site.html file. So in some admin views i have two jQuery included. That's not really good. Managing

Re: double {{ media }} in admin templates...

I created a ticket: http://code.djangoproject.com/ticket/12726 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to

double {{ media }} in admin templates...

I have double media files in some admin panel views. See: http://paste.pocoo.org/show/171364/ There is two times {{ media }} in the file contrib/admin/templates/ admin/change_list.html ince Changeset 12298 [1] One in {% block extrastyle %} and one in {% block extrahead %} This is a bug, isn't

Re: Why not datetime.utcnow() in auto_now/auto_now_add

On 25 Nov., 00:36, Russell Keith-Magee wrote: > Why would it be? A datetime field isn't necessarily stored in UTC. It > uses datetime.now() because that will return the same time as > settings.TIME_ZONE. To improve my understanding: What if the server changed and the time

Why not datetime.utcnow() in auto_now/auto_now_add

DateTimeField "auto_now" and "auto_now_add" used datetime.now(). But why this? IMHO it's better to use datetime.utcnow(), isn't it? Mfg. Jens Diemer -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

cache middleware on multi sites...

There exist some "intersection" on multi site installation, if i use django.middleware.cache.UpdateCacheMiddleware and django.middleware.cache.FetchFromCacheMiddleware Problem: The cache key would be only generated based on the url without the domain name. So if the page /foobar/ exist on site A

myuser.user_permissions.add("whoops, a string here?!?")

Hi... If i made this: myuser.user_permissions.add("whoops, a string here?!?") I get no Traceback, why? Is this a Bug or something for: http://code.djangoproject.com/wiki/BetterErrorMessages Mfg. Jens --~--~-~--~~~---~--~~ You received this message

List of Backwards-compatible changes...

There exist the gread wiki page: http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges I think it would be nice if there is the same list for Backwards- compatible changes, too. Sometimes i find some parte in the documentation and wonder, woops this must be new. OK, on the main

Re: routing to a log file when daemonizing a fastcgi process

On 29 Feb., 21:38, tamas kemenczy <[EMAIL PROTECTED]> wrote: > Recently at work I've encountered a need to be able to redirect the > stdout/stderr of a daemonized fastcgi Django process to a log file > (something other than /dev/null). This is very interesting for me, too. Can you post you

Re: Pluggable filestorage [was Heads-up: doing a bit of triage work]

On 17 Sep., 18:13, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote: > On 9/17/07, jedie <[EMAIL PROTECTED]> wrote: > > > What's about a FTP backend? ;) > > I'd be -1 on including one with Django for the simple reason that FTP > is dangerously insecure.

Re: Pluggable filestorage [was Heads-up: doing a bit of triage work]

On 17 Sep., 15:38, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote: > In general, more backends is better, of course :) I'd be +1 on just > including all of 'em (though SVN is a bit marginal), but if others > feel differently I'd love to hear about it. What's about a FTP backend? ;)

Re: manage.py idea?

On 15 Aug., 19:30, Rob Hudson <[EMAIL PROTECTED]> wrote: > Would it be worthwhile to add a way to purge unused content types via > manage.py? It could look at INSTALLED_APPS and anything not installed > it removes? I have started a tread in django-users a long time ago:

Re: Documentation should never show non-working examples. - was: "@cache_page" bug...

On 5 Jul., 09:41, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Thu, 2007-07-05 at 00:39 -0700, jedie wrote: > > The documentation philosophy is relevant for me: The documentation > > should really never show non-working examples. > > Unsurprisingl

Documentation should never show non-working examples. - was: "@cache_page" bug...

On 4 Jul., 09:51, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Wed, 2007-07-04 at 00:30 -0700, jedie wrote: > > "shortly"... But my "change docu" ticket is opened 2 weeks ago: > >http://code.djangoproject.com/ticket/4649 > > > The real bug

Re: Bug: Underscores in primary keys and quote/unquote...

On 26 Jun., 13:53, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Since the bug is crash inside change_stage() in the same file, try to > work out what why the wrong string is being passed in there. This should > be just pieces of input captured from the URL (via admin/urls.py), so > this

Bug: Underscores in primary keys and quote/unquote...

I have a model class like this: class PagesInternal(models.Model): name = models.CharField(primary_key=True, maxlength=150) ... And my names (the primary

"@cache_page" bug...

In the docu there ware two syntax for a "per-view cache": """ def my_cool_view(request): # cool processing slashdot_this = cache_page(slashdot_this, 60 * 15) """ or """ @cache_page(60 * 15) def my_cool_view(request): # cool processing """ see:

Re: UnicodeError with newforms.form_for_model()...

On 25 Mai, 01:03, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Thu, 2007-05-24 at 07:50 -0700, jedie wrote: > > I found a UnicodeError with newforms.form_for_model() and > > LANGUAGE_CODE = 'de': > > However, this is (a) a known bug and (b) fixed on the Unicode b

UnicodeError with newforms.form_for_model()...

I found a UnicodeError with newforms.form_for_model() and LANGUAGE_CODE = 'de': Traceback (most recent call last): File "/home/jens/workspace/PyLucid0.8(django)/PyLucid/dev/ local_test2.py", line 29, in html_code = form.as_p() File

Re: #3527 - better debug traceback with code executing...

Whats about INTERNAL_IPS [1] ? The special debugger is only available if... ...settings.DEBUG is ON (or a seperate Variable) and ...the request IP is in INTERNAL_IPS [1] http://www.djangoproject.com/documentation/settings/#internal-ips --~--~-~--~~~---~--~~ You

syncdb should cleanup tables?!?!

I have Problems with old entries in "django_content_type". I described it here: http://groups.google.com/group/django-users/browse_thread/thread/4f74fc5a98f7c8fe/1b542eff91614ab8 I get the error "ContentType matching query does not exist." if i create a new user group. The Problem is: I had

Re: Version 1.0 feature???

Sorry, this should be related to the discussion here: http://groups.google.com/group/django-developers/browse_thread/thread/cca45aa7c9106b88 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers"

Version 1.0 feature???

Is there any change, that the interactive traceback debugger is a feature for django v1.0 ??? http://code.djangoproject.com/wiki/VersionOneFeatures?action=diff=67 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: empty PATH_INFO env var

On May 3, 7:18 pm, Brian Rosner <[EMAIL PROTECTED]> wrote: > I wanted to bring up some discussion here about an empty PATH_INFO > value. The ticket #3414 also reports this problem. There is the same problem with CGI. Please look at: http://code.djangoproject.com/ticket/2407

Re: The locmem patch and development progress

On Apr 25, 9:50 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > use a kernel or gcc-like terminology for the branches. +1 User can use a stable SVN version (with bugfix state) and there exist a heavy dev branch for experimentals. This branch can have a "feature freeze state". In this time

#3527 - better debug traceback with code executing...

Why has django not a interactive AJAX traceback debugger? Using a interactive debugger you can play with objects at any point in the error traceback. I known, a web shell is a open security hole. But the interactive debugger should only running with the development Web server and if debugging