Django 1.4 beta 1 released

[James Bennett]

Hot off the presses, it's the first Django 1.4 beta! Blog post with
more information is here:
https://www.djangoproject.com/weblog/2012/feb/15/14-beta-1/


-- 
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: auth.User usernames

[Tai Lee]

I created a generic `accounts` app which has (among other things) it's
own `Profile` model with a username field and a OneToOneField pointing
at `User`. I added an authentication backend to my settings that
checks usernames from my model. Of course there are other supporting
components, forms, signals, etc., but this has removed any Django
username limitations for me pretty easily.

This might be a little inconvenient, but it works well here and I
still have a `User` for every `Profile` so I can hook into Django
sessions and groups. If you are having trouble with `User.username`
right now or anticipate issues in the near future, I suggest you
implement something similar yourself, or find an open source generic
app that does it for you, as I think it will likely be a very long
time until this is resolved in Django.

Cheers.
Tai.


On Feb 16, 9:57 am, Donald Stufft  wrote:
> On Wednesday, February 15, 2012 at 5:49 PM, James Bennett wrote:
> > On Wed, Feb 15, 2012 at 4:37 PM, Donald Stufft  > (mailto:donald.stu...@gmail.com)> wrote:
> > > I know this has been discussed before, but I wanted to bring it up again 
> > > in
> > > light of the oncoming Djnago 1.4 beta.
>
> > So, here's the thing: you're asking for a fairly significant,
> > massively backwards-incompatible change which requires every Django
> > install on the planet to do a schema migration... about four hours
> > before we feature-freeze 1.4. There is simply no way this is going to
> > get in on that time scale; 1.5, maybe, if the inherent problems can
> > get ironed out, and if you're strongly interested in making this
> > happen I'd invite you to help out with that.
>
> > But 1.4 beta -- and thus feature freeze -- happens tonight, and it's
> > flat impossible to land something of this magnitude before that
> > happens.
>
> 1.5 would work as well ;) Sorry I sometimes speak before I think things 
> through,
> thoroughly. django.auth in general is something that i'm interested in and I 
> want
> to try and improve to be more flexible, I just hadn't though of a general 
> solution yet
> and a "easy" (code wise) fix appealed in a shorter term "provide some 
> improvement"
> sort of way.
>
>
>
>
>
>
>
> > --
> > "Bureaucrat Conrad, you are technically correct -- the best kind of 
> > correct."
>
> > --
> > 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 
> > (mailto:django-developers@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > django-developers+unsubscr...@googlegroups.com 
> > (mailto:django-developers+unsubscr...@googlegroups.com).
> > For more options, visit this group 
> > athttp://groups.google.com/group/django-developers?hl=en.

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: auth.User usernames

[Łukasz Rekucki]

On 15 February 2012 23:57, Donald Stufft  wrote:
>
> 1.5 would work as well ;) Sorry I sometimes speak before I think things
> through,
> thoroughly. django.auth in general is something that i'm interested in and I
> want
> to try and improve to be more flexible, I just hadn't though of a general
> solution yet
> and a "easy" (code wise) fix appealed in a shorter term "provide some
> improvement"
> sort of way.
>

AFAIR, the last consensus was to get some basic schema alternation API
into Django (see the last GSOC), so that we can fix things like that.
So the general solution would be doing that ;). Just changing it,
helps new installations, but breaks old ones.

PS. Since Facebook started generating fake addresses, 75 characters on
the email field is also no good, so matching that doesn't solve
anything ;)

-- 
Łukasz Rekucki

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: auth.User usernames

[Max Thayer]

I and some folks in my area (Boston/Cambridge, MA) are thinking of ways to
provide a solution to this problem that neither requires schema migration
nor breaks backwards compatibility. David, if you (or anyone on this
mailing list) is interested, email me and let's coordinate our efforts.

Alternatively, if all you need is a longer username, this monkey patch
works nicely: https://github.com/GoodCloud/django-longer-username

Best regards,
Max

On Wed, Feb 15, 2012 at 5:57 PM, Donald Stufft wrote:

> On Wednesday, February 15, 2012 at 5:49 PM, James Bennett wrote:
>
> On Wed, Feb 15, 2012 at 4:37 PM, Donald Stufft 
> wrote:
>
> I know this has been discussed before, but I wanted to bring it up again in
> light of the oncoming Djnago 1.4 beta.
>
>
> So, here's the thing: you're asking for a fairly significant,
> massively backwards-incompatible change which requires every Django
> install on the planet to do a schema migration... about four hours
> before we feature-freeze 1.4. There is simply no way this is going to
> get in on that time scale; 1.5, maybe, if the inherent problems can
> get ironed out, and if you're strongly interested in making this
> happen I'd invite you to help out with that.
>
> But 1.4 beta -- and thus feature freeze -- happens tonight, and it's
> flat impossible to land something of this magnitude before that
> happens.
>
>
> 1.5 would work as well ;) Sorry I sometimes speak before I think things
> through,
> thoroughly. django.auth in general is something that i'm interested in and
> I want
> to try and improve to be more flexible, I just hadn't though of a general
> solution yet
> and a "easy" (code wise) fix appealed in a shorter term "provide some
> improvement"
> sort of way.
>
> --
> "Bureaucrat Conrad, you are technically correct -- the best kind of
> correct."
>
> --
> 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
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>
>  --
> 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
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: auth.User usernames

[Donald Stufft]

On Wednesday, February 15, 2012 at 5:49 PM, James Bennett wrote:
> On Wed, Feb 15, 2012 at 4:37 PM, Donald Stufft  (mailto:donald.stu...@gmail.com)> wrote:
> > I know this has been discussed before, but I wanted to bring it up again in
> > light of the oncoming Djnago 1.4 beta.
> > 
> 
> 
> So, here's the thing: you're asking for a fairly significant,
> massively backwards-incompatible change which requires every Django
> install on the planet to do a schema migration... about four hours
> before we feature-freeze 1.4. There is simply no way this is going to
> get in on that time scale; 1.5, maybe, if the inherent problems can
> get ironed out, and if you're strongly interested in making this
> happen I'd invite you to help out with that.
> 
> But 1.4 beta -- and thus feature freeze -- happens tonight, and it's
> flat impossible to land something of this magnitude before that
> happens.
> 
> 
1.5 would work as well ;) Sorry I sometimes speak before I think things through,
thoroughly. django.auth in general is something that i'm interested in and I 
want
to try and improve to be more flexible, I just hadn't though of a general 
solution yet
and a "easy" (code wise) fix appealed in a shorter term "provide some 
improvement"
sort of way. 

> -- 
> "Bureaucrat Conrad, you are technically correct -- the best kind of correct."
> 
> -- 
> 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 
> (mailto:django-developers@googlegroups.com).
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com 
> (mailto:django-developers+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
> 
> 


-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: auth.User usernames

[James Bennett]

On Wed, Feb 15, 2012 at 4:37 PM, Donald Stufft  wrote:
> I know this has been discussed before, but I wanted to bring it up again in
> light of the oncoming Djnago 1.4 beta.

So, here's the thing: you're asking for a fairly significant,
massively backwards-incompatible change which requires every Django
install on the planet to do a schema migration... about four hours
before we feature-freeze 1.4. There is simply no way this is going to
get in on that time scale; 1.5, maybe, if the inherent problems can
get ironed out, and if you're strongly interested in making this
happen I'd invite you to help out with that.

But 1.4 beta -- and thus feature freeze -- happens tonight, and it's
flat impossible to land something of this magnitude before that
happens.


-- 
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

auth.User usernames

[Donald Stufft]

I know this has been discussed before, but I wanted to bring it up again in
light of the oncoming Djnago 1.4 beta. 

Can we increase the length of the username field in auth.User? It is a common
pattern for emails to be used instead of usernames for a site, and 30 characters
makes it difficult to follow that pattern. There are work arounds but they are 
all
a lot less elegant than increasing the length of the username field. I think 
that
a max_length of 75 (to match the default EmailField) would allow developers
a lot more breathing room with regards to what they use as the value for 
username.
75 Would support most emails, usernames, UUIDs, etc. If 75 is too long for the
"username" case you could set the max_length of the form to 30 still, allowing
developers who want to use a longer value the ability to either subclass the 
form
or provide their own form, which they can easily do, while still using the 
auth.User
model which replacing is not something that is particularly easy or clean to do.

Obviously there the overall problem of contrib.auth being inflexible to the 
differing
requirements of varying problems but I don't think we should let a possible
future improvement stop a small improvement that can be made today, in
other words don't let the best be the enemy of good.


-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Fieldsets in forms - ready to check-in

[Mikołaj Siedlarek]

Ok, so there's this feature I've made - commonly long-anticipated fieldsets 
definition in Form declaration.
I beg some core developer to review and check it in ASAP, because every little 
change in trunk forms requires me to resolve conflicts to keep patch up to date 
and one of these days I'll just stop doing that.

https://code.djangoproject.com/ticket/17301

Any comments or critique appreciated.

Thanks,
Mikołaj Siedlarek

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.