On 7/22/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> Underlying behavior? So, is it basically safe to use a OneToOneField
> and the API, though not guaranteed to be consistent, is likely to
> just require tweaking? In other words, while underlying behavior
> might change, it'll look roughly equiv
On Jul 22, 2006, at 7:18 PM, James Bennett wrote:
>
> On 7/22/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
>> What is the current wisdom on OneToOne? Will it be finalized soon?
>> Ever?
>
> As I understand it from a conversation I had the other day, nothing
> whatsoever will happen until subcla
Rather than watch the "inherit from User" thread go round and round,
maybe I should give people something more concrete to think about.
This is a follow-up to the mail I sent late on Friday. It describes the
area where we need API additions or some kind of semi-major change to
incorporate model i
Hi,
http://code.djangoproject.com/ticket/2401
"strings escaping translation"
The strings that stay in english aren't in the tamil .po file. I think
the .po files might be out of sync with the source tree and that
bin/make-messages.py needs to be rerun over the source. Maybe a job for
a post
The only framework that I've seen sufficiently tackle this whole user
extension problem is asp.net 2.0 with their provider model. The
provider model allows users to extend or "plug" in their own
implementation of a feature. This is useful when the given schema
doesn't meet your needs, such as a
The humanize middleware should probably handle pretty-printing dates as
well. It should also reflect I18N, if possible. I started a thread in
that group regarding this.
http://groups.google.com/group/Django-I18N/browse_thread/thread/f33c087fc57fb2bc
Are there any opinions about how to best abstr
On 7/22/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> What is the current wisdom on OneToOne? Will it be finalized soon? Ever?
As I understand it from a conversation I had the other day, nothing
whatsoever will happen until subclassing is straightened out. At that
point we'll move to recommending
On Jul 22, 2006, at 2:59 AM, Ivan Sagalaev wrote:
>
> Again, having the solution with OneToOne relation scares newbies away
> because it's become a kind of common wisdom that OneToOne will be
> changed very drastically very soon and "all your code would burn".
What is the current wisdom on OneToO
Hi all,
I just start using Django for a week, and i'm really impressive, great
project !
I'm getting in trouble with ImageField and upload directory.
I'd like to set a ImageField with an upload_to parameter depending on
instance attributes.
I found a first solution with the #1994 patch
(http://
