Re: Virtualenvs and editing contrib stuff manually

It's mostly historical - the foreign key method was the *only* method
until about a week ago. :-)

The development docs contain a section about how to set up your own
User model, but that section isn't the 1.4 (current stable) docs. If
you can point me at a section in the dev docs that you think
recommends the foreign key method, it probably needs to be rewritten
or rephrased given the new features that have landed.

Yours,
Russ Magee %-)

On Fri, Oct 5, 2012 at 10:04 PM, Chris Pagnutti
<chris.pagnutti@gmail.com> wrote:
> Hey thanks Russell. That's a great explanation. Is there a particular
> reason that the docs tend to favour the foreign key method over subclassing?
>
>
> On Thursday, September 27, 2012 4:13:34 PM UTC-4, Tundebabzy wrote:
>>
>> No you won't be smitten.
>>
>> As for isolating your edited django, you can do that but then you
>> would have to be responsible for improving the code base by yourself.
>> Also, your edit might inadvertently break django or introduce bugs
>> that you might find difficult to trace and solve or that might change
>> some of the logic required to make django work.
>>
>> On 9/27/12, Chris Pagnutti <chris.p...@gmail.com> wrote:
>> > Hi. First-time poster here. Feel free to point out any rules I'm not
>> > following.
>> >
>> > I've been looking around for how to make the django.contrib.auth User
>> > classe's "email" field to be unique and required. There are bunches of
>> > ways to do it, but it's just soooo darn easy to go into the source and
>> > change how the field is defined.
>> > e.g. email = models.EmailField(_('email address'),unique=True)
>> >
>> > But in my searches, I've read warnings that you should not do this. The
>> > reason, if it is given, is that you'll break your app if you update the
>> > contrib packages. But what if I work in virtualenvs and just leave the
>> > django version and packages intact for that particular app in that
>> > particular environment? What are the other practical and philosophical
>> > reasons for NOT editing the contrib source? Will I be smitten from the
>> > django community if I do so?
>> >
>> > Thanks to all.
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Django users" group.
>> > To view this discussion on the web visit
>> > https://groups.google.com/d/msg/django-users/-/YX9X8u9mdbwJ.
>> > To post to this group, send email to django...@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > django-users...@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/django-users?hl=en.
>> >
>> >
>>
>> --
>> Sent from my mobile device
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-users/-/kgPJcEQC1vAJ.
>
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.