Re: Bug introduced at changeset 4500

2007-02-19 Thread Rudolph
On Feb 19, 5:20 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > After a fair bit of head scratching and chasing code paths, I think I > managed to fix this in the correct way. The update is in revision r4542. > The problem hadn't ever shown up before because we weren't correctly > handling min

Re: reopened tickets should reset stage to unreviewed

2007-02-19 Thread Michael Radziej
Gary Wilson: > As an example, ticket 3123 was re-opened and the stage remained ready > for checkin. I think it would be better if the stage was reset to > unreviewed when the ticket gets reopened. Thoughts? +1 -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-93

[SECURITY] logout() doesn't delete session data while docs state so

2007-02-19 Thread Boris Erdmann
In current django >= 0.95 logout() simply removes the user object id from a running session. Thus, if the browser stays open and somebody else log in, they get access to all session bound data of the previous user. http://www.djangoproject.com/documentation/sessions/#clearing-the-session-table s

Creating an independent auth/permission-framework, separate the models (Was: Adding support for replacing the auth User model to fit custom needs)

2007-02-19 Thread David Danier
I'll pick this topic up for some changes I think Django needs. Please read the summary between the "="-line, if you don't have the time to read the whole mail. Perhaps it will get you interested in reading the rest. ;-) As far as I can see there are different approaches to improve this (which hav

newforms with auto_now

2007-02-19 Thread Jeff Triplett
Are the auto_now / auto_now_add fields going to be supported in newforms? I was working with the form_for_instance this morning and I noticed that both these fields and the editable=False still displayed in my form rendered with the form as_table() method. Since there has been quite a bit of dis

Re: Proposal: Root view

2007-02-19 Thread Thomas Steinacher
Hello, What is the current status of the ROOT_VIEW setting? Are there any plans to implement this? I am +1 on this, because it would allow me to use one Django instance for multiple subdomains, without wasting system ressources. Also, this is more flexible than e.g. a HostURLResolver (see h

Re: Proposal: Root view

2007-02-19 Thread Lakin Wecker
I am +! on this as well. Lakin On 2/19/07, Thomas Steinacher <[EMAIL PROTECTED]> wrote: > > > Hello, > > What is the current status of the ROOT_VIEW setting? > > Are there any plans to implement this? > > I am +1 on this, because it would allow me to use one Django instance > for multiple subdoma

proposal: expand save() to force update/insert to avoid race conditions

2007-02-19 Thread Jimmy Scott
Hello developers, To be aware of the background, it started with ticket #3507. What I define to be the problem is: if you roll your own public key, you have a chance that someone else also gets or chooses the same value as a public key. There is a very very small chance while using session

Re: proposal: expand save() to force update/insert to avoid race conditions

2007-02-19 Thread Jimmy Scott
replace 'public key' with 'primary key' .. what the h* I was thinking about... On 19 Feb 2007, at 21:16, Jimmy Scott wrote > > Hello developers, > > To be aware of the background, it started with ticket #3507. > > What I define to be the problem is: if you roll your own public key, > you have

Re: proposal: expand save() to force update/insert to avoid race conditions

2007-02-19 Thread Honza Král
On 2/19/07, Jimmy Scott <[EMAIL PROTECTED]> wrote: > > Hello developers, > > To be aware of the background, it started with ticket #3507. > > What I define to be the problem is: if you roll your own public key, > you have a chance that someone else also gets or chooses the same > value as a public

Re: proposal: expand save() to force update/insert to avoid race conditions

2007-02-19 Thread Jimmy Scott
On 19 Feb 2007, at 21:29, Honza Král wrote: > On 2/19/07, Jimmy Scott <[EMAIL PROTECTED]> wrote: >> >> Hello developers, >> >> To be aware of the background, it started with ticket #3507. >> >> What I define to be the problem is: if you roll your own public key, >> you have a chance that someone

Re: UserManger Class question

2007-02-19 Thread voltron
Thanks a lot for the answers guys. I´m still trying to wrap my head around it though. The last thing for me to get is at what point is the class variable/attribute model declared and when it gets assigned, I sort of assumed what it was doing but really did not get how, I took a look at the "base"

Re: Proposal: Root view

2007-02-19 Thread Marc Fargas Esteve
+1, just leave the "urls.py" thing as the default for newcomers. --~--~-~--~~~---~--~~ 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 un

Re: Proposal: Root view

2007-02-19 Thread Malcolm Tredinnick
On Mon, 2007-02-19 at 20:18 +0100, Thomas Steinacher wrote: > Hello, > > What is the current status of the ROOT_VIEW setting? > > Are there any plans to implement this? > > I am +1 on this, because it would allow me to use one Django instance > for multiple subdomains, without wasting system

Re: newforms with auto_now

2007-02-19 Thread Jeff Triplett
One of my co-workers found this ticket which a few patches to fix the issue: http://code.djangoproject.com/ticket/3247 On Feb 19, 10:52 am, "Jeff Triplett" <[EMAIL PROTECTED]> wrote: > Are the auto_now / auto_now_add fields going to be supported in > newforms? I was working with the form_for_in

Re: reopened tickets should reset stage to unreviewed

2007-02-19 Thread Adrian Holovaty
On 2/16/07, Gary Wilson <[EMAIL PROTECTED]> wrote: > As an example, ticket 3123 was re-opened and the stage remained ready > for checkin. I think it would be better if the stage was reset to > unreviewed when the ticket gets reopened. Thoughts? That would be a great improvement. If anybody know

MEDIA_URL - feedback pls on ticket 1278

2007-02-19 Thread sime
Hi all - interested to hear feedback on a minor but I feel important addition to allow MEDIA_URL and other selected constants to be accessible from templates -- http://code.djangoproject.com/ticket/1278#comment:6 Particularly important for new users (like me a couple days back). I was scratching

Re: MEDIA_URL - feedback pls on ticket 1278

2007-02-19 Thread SmileyChris
It does seem a bit strange that Adrian says he's never needed to use this. Apart from hard-coding links to your media, am I missing something obvious? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django develope

Re: MEDIA_URL - feedback pls on ticket 1278

2007-02-19 Thread Ivan Sagalaev
sime wrote: > Adrian seems to think it's feature creep. But how else are we supposed > to link media without access to MEDIA_URL? To answer directly: by using get_FIELD_url() methods of models. Media directory is primarily intended to keep files that are uploaded into FileFields and automatical

Re: MEDIA_URL - feedback pls on ticket 1278

2007-02-19 Thread sime
On Feb 20, 11:30 am, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > But I suppose that you are talking about using MEDIA_URL to access CSS > and JS files, right? If yes then it's not what everyone does. Many > people keep CSS and JS under source control in a place that has nothing > to do with a direc

newforms DateTimeFiels issue?

2007-02-19 Thread juampa
I have noticed the following situation and I suspect it may be a problem: If you have a model class with a date_added = models.DateTimeField(auto_now_add=True) field and you use a newform to create a new entry of this model in the database (leaving the date_added form field blank) the date_adde

Re: MEDIA_URL - feedback pls on ticket 1278

2007-02-19 Thread SmileyChris
On Feb 20, 2:30 pm, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > But I suppose that you are talking about using MEDIA_URL to access CSS > and JS files, right? If yes then it's not what everyone does. Many > people keep CSS and JS under source control in a place that has nothing > to do with a direct