Re: Changing django.contrib.auth to make passwords optional

# Blog post here: http://www.buriy.com/2007/may/12/django-openid-users/ # Download here: http://www.buriy.com/media/openid-solution.zip For anyone interested, the OpenID 2 release of our python OpenID library[1] will include a Django app with an example consumer and server, in addition to the exa

Re: Changing django.contrib.auth to make passwords optional

Blog post here: http://www.buriy.com/2007/may/12/django-openid-users/ Download here: http://www.buriy.com/media/openid-solution.zip --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post

Re: Uploading pictures problem

On 2007-05-11 14:09:06 -0600, Martin Tomov <[EMAIL PROTECTED]> said: > > I am making a photo gallery as a project from school and I got stuck > on the uploading picture part of it. Initially I started with the > oldforms and I successfully uploaded pictures. But I have 2 questions. > So I have

Uploading pictures problem

I am making a photo gallery as a project from school and I got stuck on the uploading picture part of it. Initially I started with the oldforms and I successfully uploaded pictures. But I have 2 questions. So I have this code: if request.method == 'POST': # If data was POSTed, we're tryin

Re: database connection user - newbie question

I am surely guilty of muddling the conversation from the specific case of multi-DB to the more general and more perilous case of dynamic connections. In fact I'm using the multi-db branch now for a non- critical app and it works just dandy. Also I know of someone who is working on updating that

Re: database connection user - newbie question

On May 11, 6:32 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > user: Hi I'd like to be able to connect to multiple databases and/or > specify connections dynamically for my Django app. > That wasn't what the original poster said: "I'm managing a programming team that's developing a web

Re: database connection user - newbie question

I think we have reached the dead horse phase of this discussion. Since it has become so lengthy and confusing for some (at least for me it has), I wanted to summarize what was accomplished. Thank you all for your responses. I feel like I have a much better sense of Django's current intended targ

Re: Changing django.contrib.auth to make passwords optional

Sorry, I misunderstood. The last association is only deleted when the password is set. Got it. Regards, Max --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send ema

Re: database connection user - newbie question

Hey Waylan, "What you seem to be missing is that the core devs are not questioning that." Ok, I think what's happening here is that one or more of us needs to improve our communication skills - present company potentially included. If you got that impression than I did not make my thoughts clea

Re: Changing django.contrib.auth to make passwords optional

> The problem with using a random password is that you can't answer the > question "does this account have a password set?". I need to be able > to answer that question because my OpenID implementation allows users > to associate mupltiple OpenIDs with a single account. I want to let > them delete

Re: Question for Oracle Boulder sprinters

On May 11, 8:37 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > ... > So should the Oracle branch be ignoring the null attribute when > blank=True and assuming null=True in that case? I think that's reasonable. It may mean a couple of unit tests fail, so we can either modify them or at leas

Re: Changing django.contrib.auth to make passwords optional

On May 11, 4:23 pm, Niels <[EMAIL PROTECTED]> wrote: > > Or you could use the traditional > > Unix password invalidator -- "!" -- which might be more mnemonic for > > some people and is easier to pick out of a data dump than a space (and > > will also never be a valid string, since we use '$' as a

Re: Changing django.contrib.auth to make passwords optional

On Fri, 2007-05-11 at 08:23 -0700, Niels wrote: > On May 11, 5:07 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> > wrote: > > > > So does that mean that I should store a single blank space in the > > > password field to represent "no password set"? > > > > The purists will be breaking out the pitchfo

Re: Changing django.contrib.auth to make passwords optional

On May 11, 5:07 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > So does that mean that I should store a single blank space in the > > password field to represent "no password set"? > > The purists will be breaking out the pitchforks and flaming torches > ( :-) ), but that would be a backwar

Re: South American Developers

I'm from Colombia, but currently living in US. On May 10, 9:19 am, "Ronit Araujo" <[EMAIL PROTECTED]> wrote: > Hi, im from Chile, from Santiago ! Graphic designer... > > 2007/5/10, Mi Reflejo <[EMAIL PROTECTED]>: > > > > > > > Yes, there are. At least one, but not in Chile. I'm in Argentina.

Re: Changing django.contrib.auth to make passwords optional

On Fri, 2007-05-11 at 14:51 +, Simon Willison wrote: > On May 11, 3:40 pm, Martin Winkler <[EMAIL PROTECTED]> wrote: > > > Certainly Oracle treats them empty string as equal to NULL. But does > > > that mean you can't put an empty string in a "not NULL" column in > > > Oracle? > > > > Exactly.

Re: Type coercion in Django

On May 11, 10:06 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > My understanding of this whole thread is that the initial resistance was > because we really do want to understand the use-cases before making any > architecture change. [...] So if we > can make that use-case possible without ne

Re: Changing django.contrib.auth to make passwords optional

On May 11, 3:40 pm, Martin Winkler <[EMAIL PROTECTED]> wrote: > > Certainly Oracle treats them empty string as equal to NULL. But does > > that mean you can't put an empty string in a "not NULL" column in > > Oracle? > > Exactly. If you want to insert something meaningless into a column that > has

Wonderful Idea

ShortIntroduction Well, cut short, Shortcut takes you to those ultimate, hand picked, genuine sites that add bucks to your pocket, without any strings attached! What you will find here: Links

Re: Changing django.contrib.auth to make passwords optional

> Certainly Oracle treats them empty string as equal to NULL. But does > that mean you can't put an empty string in a "not NULL" column in > Oracle? Exactly. If you want to insert something meaningless into a column that has a NOT NULL constraint in oracle, then you have to put at least one space

Question for Oracle Boulder sprinters

Given the observation that Martin Winkler made in a recent thread ([1]), pointing out Oracles '' = NULL addiction, it made me think of something related: there are a lot of models that have fields with blank=True and null=False, even in Django core. However, this is kind of nonsensical in Oracle-l

Re: Changing django.contrib.auth to make passwords optional

Simon Willison wrote: > The problem with using a random password is that you can't answer the > question "does this account have a password set?". I need to be able > to answer that question because my OpenID implementation allows users > to associate mupltiple OpenIDs with a single account. I wan

Re: Type coercion in Django

On Fri, 2007-05-11 at 06:46 -0700, Gulopine wrote: [...] > Given the resistance I've had so far with the coercion patch, I've > starting working on a signal-based approach instead, to see if I can > possibly get DurationField working without any patches to other bits > of Django's core. My unders

Re: Changing django.contrib.auth to make passwords optional

On May 11, 7:50 am, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > At the moment, django.contrib.auth does not support creating a user > > account without setting a password. > > Why not generate a random one? It won't break an ability to authenticate > using OpenID or any other backend for that mat

Re: Type coercion in Django

I'll be the first to admit that I don't know all the internals of Django, and I especially don't know why certain decisions were made in the past. But I appreciate knowing that you understand my reasoning, and from some your rephrasings, it's clear to me that you really do. I'm also glad to hear I

Re: Changing django.contrib.auth to make passwords optional

Twas brillig at 16:02:43 11.05.2007 UTC+04 when Ivan Sagalaev did gyre and gimble: IS> A comment in my code is about username part, not password :-). That means that your code lacks the comment required for understanding your intent. IS> I would indeed be glad to have some generalized metho

Re: Changing django.contrib.auth to make passwords optional

On May 11, 5:30 am, Simon Willison <[EMAIL PROTECTED]> wrote: > I'm working on a new component for my Django OpenID package which will > provide support for associating one or more OpenIDs with a > django.contrib.auth User. As part of this, I want to include the > ability to register for a new use

Re: Changing django.contrib.auth to make passwords optional

Mikhail Gusarov wrote: > Because generation of random password is an ugly workaround. Your solution > requires long comment which explains to the reader of code, why do random > password is needed in first place. A comment in my code is about username part, not password :-). I would indeed be gl

Re: Changing django.contrib.auth to make passwords optional

On Fri, 2007-05-11 at 09:50 +0200, Michael van der Westhuizen wrote: > Hi Simon, > > On 5/11/07, Simon Willison <[EMAIL PROTECTED]> wrote: > > > [snip] > > 1. The 'password' field in the User model should be altered to have > > blank=True. > > > > This would allow us to set blank passwords as an

Re: Changing django.contrib.auth to make passwords optional

Hi Simon, On 5/11/07, Simon Willison <[EMAIL PROTECTED]> wrote: > [snip] > 1. The 'password' field in the User model should be altered to have > blank=True. > > This would allow us to set blank passwords as an empty string. It > would not require existing installations to make any schema changes

Re: Changing django.contrib.auth to make passwords optional

Twas brillig at 10:50:57 11.05.2007 UTC+04 when Ivan Sagalaev did gyre and gimble: >> At the moment, django.contrib.auth does not support creating a user account >> without setting a password. IS> Why not generate a random one? It won't break an ability to authenticate IS> using OpenID or