Having talked to several people at DjangoCon about this, I would like
to start a formal discussion here. It was asked of the Django Core Dev
panel, why had the project not yet moved to a distributed version
control system? My interpretation of the answer was that there is
little incentive for the
DATABASE_ENGINE = 'mysql'
DATABASE_NAME = 'projectname'
DATABASE_USER = 'root'
DATABASE_PASSWORD = ''
else:
...
On Jun 18, 3:00 pm, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> On 6/18/07, Jared Kuolt <[EMAIL PROTECTED]> wrote:
I have a common set of extra bits that I put in my settings.py files
and re-input them each time I create a project. I would like to have a
directory like ~/.django_skeletons/project that houses my customized
settings.py (and perhaps others).
It seems to me this would be a fairly simple undertaki
On May 26, 10:17 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> I would assume the the mechanism for exposing this would allow it to
> be done anywhere in the template, so that CSS/JS could be pulled in as
> part of the of the resulting (X)HTML document (in the case of
> CSS, to remain valid, i
This gets a little complicated: tags are only allowed inside
tags, otherwise you have invalid (X)HTML. The javascript
portion seems fine, however I would see media as a class, not as a
method, ala a model's Meta class:
class MyWidget(Widget):
...
class Media:
js = ('/path/to/js'
I submitted a patch to extend both get_object_or_404 and
get_list_or_404 to accept QuerySets.
Current usage:
get_object_or_404(Poll, pk=1)
get_object_or_404(Poll.my_objects, pk=1)
New usage:
get_object_or_404(Poll.objects.live(), pk=1)
Tests and docs were added to the patch. Does this need a de
Forgot the link:
http://code.djangoproject.com/ticket/4373
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubs
Joe wrote:
> It does bring up the general sort of question - is there a mechanism by
> which individuals can get "whitelisted" or otherwise allowed access to
> the wiki to post up code, patches, etc?
I put some thought into this but couldn't figure out a way to make this
feasible. This would almo
I forgot to mention that I attempted to put this in the Wiki again and
askimet failed me.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develo
Thanks, Joe. I've actually updated it to this:
from django.conf import settings
from django.contrib.auth.views import login
from django.http import HttpResponseRedirect
class RequireLoginMiddleware(object):
"""
Require Login middleware. If enabled, each Django-powered page will
require
I'd like to add a Middleware class that I wrote to the Wiki, but I keep
getting rejected by askimet.
The class requires an authenticated user for every view. This is
beneficial for any closed project. Does anyone suppose something like
this is beneficial enough to make it into the Django source?
I haven't been able to submit anything. And I like to think I
contribute quality material!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-devel
12 matches
Mail list logo
