On 9.02.2010 1:09, Karen Tracey wrote:
> On Mon, Feb 8, 2010 at 5:31 PM, Luc Saffre
> I personally won't insist
> further, especially since Luke knows Django better than me. May I
> suggest again to mark this ticket to something different than "duplicate
> of an invalid ticket"?
>
- Make email unique and username non-required on the model. That would
make implementing something that authenticated by email a lot
easier :)
On Feb 9, 1:34 am, Russell Keith-Magee wrote:
> On Tue, Feb 9, 2010 at 8:15 AM, Justin Lilly wrote:
> > To add another point, this doesn't mean that the
On 9 February 2010 09:09, Harro wrote:
> - Make email unique and username non-required on the model. That would
> make implementing something that authenticated by email a lot
> easier :)
Pff, move emails out entirely. Email-addresses may change. Usernames
shouldn't change. One may have more than
On Feb 8, 2:44 pm, Luke Plant wrote:
> What do people think?
+1 for everything which removes the magic from auto_adapt_to_methods.
Can't say much about the backwards incompatiblity issue, cause I don't
care ;) Of course it would be nice, but given the options I would just
document it and live with
On 9 February 2010 08:09, Harro wrote:
> - Make email unique and username non-required on the model. That would
> make implementing something that authenticated by email a lot
> easier :)
>
For reference there are some good points here[1] on this topic started
by Hanne Moa.
I think ideally the
I recently tried to use the recommended approach for custom user
profiles: http://docs.djangoproject.com/en/dev/topics/auth/#auth-profiles
and all the brick walls I hit were admin related. Whether these are
better fixed in contrib.auth or contrib.admin is hard to say:
1. I can show profile fields
On Tue, Feb 9, 2010 at 2:09 AM, Harro wrote:
> - Make email unique and username non-required on the model. That would
> make implementing something that authenticated by email a lot
> easier :)
1. It's *extremely* unlikely that changes will be considered which
require every Django install on the
On Tuesday 09 February 2010 02:40:03 Russell Keith-Magee wrote:
> >> What do people think?
> >
> > Ugh. Assuming no one can come up with a brilliant fix so that the
> > auto_adapt stuff can work when combined with arbitrary other
> > decorators (I can't), I favor switching to a system that require
On Tue, Feb 9, 2010 at 10:51 PM, Luke Plant wrote:
> On Tuesday 09 February 2010 02:40:03 Russell Keith-Magee wrote:
>
>> >> What do people think?
>> >
>> > Ugh. Assuming no one can come up with a brilliant fix so that the
>> > auto_adapt stuff can work when combined with arbitrary other
>> > deco
On Tue, Feb 9, 2010 at 3:02 AM, Luc Saffre wrote:
> "Closed" as "Invalid", as I understand it, means that this ticket is not
> worth to get more consideration and that further comments are not welcome.
>
> "Open" with a triage stage of "Someday/Maybe" would help people who
> stumble on this behav
Vitaly Babiy
On Tue, Feb 9, 2010 at 3:16 AM, James Bennett wrote:
> On Tue, Feb 9, 2010 at 2:09 AM, Harro wrote:
> > - Make email unique and username non-required on the model. That would
> > make implementing something that authenticated by email a lot
> > easier :)
>
> 1. It's *extremely* un
Hi all,
Is there any concept in python like .jar files in java. If anybody of you
know please reply me.
--
Thanks and regards,
chiranjeevi.muttoju
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django
On Tue, Feb 9, 2010 at 3:05 PM, chiranjeevi muttoju
wrote:
> Hi all,
> Is there any concept in python like .jar files in java. If anybody of you
> know please reply me.
>
> --
> Thanks and regards,
> chiranjeevi.muttoju
>
> --
> You received this message because you are subscribed to the Google Gr
On 21 Jan., 17:45, Andy McKay wrote:
> On 2010-01-21, at 9:15 AM, chris.moff...@gmail.com wrote:
>
> > I agree that managing settings gets to be a bit difficult in many
> > environments - even non Fortune 1000 environments.
Its also an issue for us that write and use portable apps. Luckily a
w
Maybe I can help Luc? I had similar questions once, because I started
learning Django while deploying with a legacy database.
On 8 fev, 20:31, Luc Saffre wrote:
> You cannot ask user code to not even look at invalid data. I'm
> not allergic to exceptions, but raising an exception when I ask for t
Hi list
Using David Cramer's really nice replacement devserver
(http://github.com/dcramer/django-devserver), I noticed a bunch of
huge queries in some table generation code. Example:
http://dpaste.com/156907/
This is from one of my smallest tables, bigger ones with 120+ish rows
can take multiple m
On Wed, Feb 10, 2010 at 3:11 PM, Jerome Leclanche wrote:
> Hi list
>
> Using David Cramer's really nice replacement devserver
> (http://github.com/dcramer/django-devserver), I noticed a bunch of
> huge queries in some table generation code. Example:
> http://dpaste.com/156907/
> This is from one o
Django version 1.2 alpha 1 SVN-12267
I'm not using select_related at all anywhere at the moment, I just
started database optimization. David's server is just a wrapper
django-toolbar-like and doesn't perform anything smart on the sql or
the like.
I haven't yet tested on a vanilla setup, but I sup
18 matches
Mail list logo
