Nice summary of things to think about, Russ.==
On Mon, 2006-03-06 at 14:30 +0800, Russell Keith-Magee wrote:
[...]
> 1) What should be the behaviour of __set__ for descriptors where
> multiple values are allowed (ForeignKey, ManyToManyField)?
>
> I propose that: 'Article.reporter_set = X' be all
Hi all,
A combination of recent tinkering with descriptors and a couple of
recent threads on mailing lists have collectively revealed a few
descriptor edge cases that do not appear to have been the subject of
any past discussion. This thread is an attempt to establish the
official behaviour for t
attached to the ticket :-)
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send emai
D'oh! - I should have picked *that* one up.
one thing - events[0].what.get_what_display() doesn't work, this does
;)
events[0].get_what_display()
thanks all!
Cheers,
Tone
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On 3/5/06, ChaosKCW <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> This worked. I take it Request User Middleware is now always required ?
Not necessarily, but if you ever plan on accessing request.user it is.
request.user should probably return None or raise a better error
(probably AttributeError, or ma
I think there is still a bug i this where the message.add() function
isn't defined (which get's tripped over when you use the generic
create view)
regards
Ian
On 3/6/06, Gary <[EMAIL PROTECTED]> wrote:
>
> For the time being.
>
>
>
>
--
[EMAIL PROTECTED] -- blog: http://feh.holsman.net/ -- PH:
tonecmd, maybe you need:
events[0].what.get_what_display()
for more information, see:
http://www.djangoproject.com/documentation/db_api/#get-foo-display
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django devel
Gary wrote:
> I also agree that the new home should be down a level, but again
> disagree with the 'auth' abbreviation. Perhaps django.authen?
Actually, I like the "everything should be an app" thinking. And if
that is the case, all apps should go in one directory (seems to be
/django/contrib).
Where is it ChaosKCW?
Cheers,
Tone
--~--~-~--~~~---~--~~
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 unsubscribe from this group,
Thanks for the info Malcolm, it sounds like this is more a 'not
completed yet', so I've gone to doing a workaround.
One thing though;
events[0]._meta.get_field('what').verbose_name
returns 'what'
It seems that ._meta. is only working on the field definitions, not the
value returned.
I
For the time being.
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to [E
Hi
This worked. I take it Request User Middleware is now always required ?
--~--~-~--~~~---~--~~
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@googlegro
Thbanks for the reply, will try it out.
--~--~-~--~~~---~--~~
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 unsubscribe from this gro
Joseph Kocherhans wrote:
> RequestUserMiddleware is a horribly ugly name, and in the latest diff
> attatched to http://code.djangoproject.com/ticket/1428 I've renamed it
> to MultiAuthMiddleware. I'm wondering if people think it would be
> worthwhile to add something else called AuthMiddleware tha
django.contrib.auth.middleware.MultiAuthMiddleware has been added to
MIDDLEWARE_CLASSES in django/conf/project_template/settings.py, but
that won't do anything for already-created projects i'm guessing.
--~--~-~--~~~---~--~~
You received this message because you a
ChaosKCW wrote:
> Any ideas before I being the huge debuggiong session ?
Maybe adding
django.contrib.auth.middleware.RequestUserMiddleware
to your MIDDLEWARE_CLASSES.
see..
http://code.djangoproject.com/changeset/2423
http://code.djangoproject.com/changeset/2425
http://code.djangoproject.com/cha
Hi
Added an attempt at Tut 4
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send e
Hello,
I just updated my MR branch and am getting the following error:
Request Method: GET
Request URL:http://127.0.0.1:8000/surveys/question/list/
Exception Type: AttributeError
Exception Value:'WSGIRequest' object has no attribute '_user_source'
Exception Location:
Hello everyone, Shannon (whom I’m CC-ing this message to),
In his recent “Django-palooza” blog post Shannon was mentioning
having a fix for not having to restart the webserver at each code
change under mod_python.
http://jjinux.blogspot.com/2006/02/python-django-palooza.html
I’d be intere
Was there any discussion at PyCon about validation-aware models?
When Adrian posted his thoughts about it earlier this year [1] there was
a lot of discussion, some of which raised valid points (needing to be
able to have a temporarily invalid model whilst updating dependent field
or incrementally
On Sun, 2006-03-05 at 02:26 -0800, tonemcd wrote:
[...]
>
> However, I can't get the verbose_name of the 'what' field, eg
>
> In [79]: events = Event.objects.all()
>
> In [80]: events
> Out[80]: [Engaging with Interprofessional Healthcare Education in the
> North East, Tea Time]
>
> In [81]: e
Hi,
I have this model;
class Event(models.Model):
EVENTTYPE = (
('Meet','Meeting'),
('Conf1', 'Conference Announcement'),
('Conf2', 'Conference Announcement and Call for Papers'),
('Adv', 'Advisory Board'),
('Diss','Dissemination Event')
Thanks for this Jeremy - it's very helpful! (and shows how much cleaner
django is going to be with magic removal in place) I'm still getting my
head around magic-removal (I'll be posting a question shortly) so I may
have missed the obvious, but I think there are some oversights:
375 & 441: >>> Po
Hi.
So i am in the midst of porting my forum application over to the
magic-removal branch, and also cleaning up the code a bit to make use
of the new features along the way.
One of the things I have in my model is the 'site' which is a foreign
key to the Site model.
now I'd like this field to b
24 matches
Mail list logo
