Dear All:
After reading this discussion I see that my fears were misplaced. I can now
see that schema migrations are not necessary to stop using the AUTH_PROFILE
stuff thanks to the explanations from Russ and Carl. Had I done a bit more
investigating I probably would have realized this. Sorry f
On Thu, Jan 23, 2014 at 11:25 PM, Carl Meyer wrote:
> Hi Ryan,
>
> On 01/23/2014 09:50 PM, Ryan Hiebert wrote:
> > Assuming that the changes from the deprecation policy are in trunk now
> > that the alpha has landed, any use of the AUTH_PROFILE_MODULE must be
> > eliminated _before_ moving to 1.7
If you look at the following example:
https://docs.djangoproject.com/en/1.4/topics/auth/#storing-additional-information-about-users
With `AUTH_PROFILE_MODULE = ’accounts.UserProfile’`: 'accounts' is a standard
application that you add to your INSTALLED_APPS setting, and just like any
other appl
Hi Ryan,
On 01/23/2014 09:50 PM, Ryan Hiebert wrote:
> Assuming that the changes from the deprecation policy are in trunk now
> that the alpha has landed, any use of the AUTH_PROFILE_MODULE must be
> eliminated _before_ moving to 1.7, since they are not just deprecated,
> but _removed_ in 1.7. Mig
Sorry to jump in here, please ignore me if I make no sense.
Allowing one more release before AUTH_PROFILE_MODULE is removed would allow
> him to use the new migration system to create a custom migration to migrate
> away from using the profiles. Otherwise, he'd need to use South or go
> through
On Fri, Jan 24, 2014 at 12:50 PM, Ryan Hiebert wrote:
> On Thu, Jan 23, 2014 at 10:30 PM, Russell Keith-Magee <
> russ...@keith-magee.com> wrote:
>
> On Fri, Jan 24, 2014 at 9:05 AM, Brian Neal wrote:
>>
>>> Hello,
>>>
>>> The deprecation timeline says this about Django 1.7:
>>
On Thu, Jan 23, 2014 at 10:30 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
On Fri, Jan 24, 2014 at 9:05 AM, Brian Neal wrote:
>
>> Hello,
>>
>> The deprecation timeline says this about Django 1.7:
>>
>> "The AUTH_PROFILE_MODULE setting, and the get_profile() m
On Fri, Jan 24, 2014 at 12:07 PM, Ryan Hiebert wrote:
>
>
> On Thu, Jan 23, 2014 at 7:42 PM, Russell Keith-Magee <
> russ...@keith-magee.com> wrote:
>
>>
>>
>> On Fri, Jan 24, 2014 at 9:33 AM, Ryan Hiebert wrote:
>>
>>>
>>>
>>>
>>> On Thu, Jan 23, 2014 at 7:24 PM, Russell Keith-Magee <
>>> russ...
On Thu, Jan 23, 2014 at 7:42 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
>
>
> On Fri, Jan 24, 2014 at 9:33 AM, Ryan Hiebert wrote:
>
>>
>>
>>
>> On Thu, Jan 23, 2014 at 7:24 PM, Russell Keith-Magee <
>> russ...@keith-magee.com> wrote:
>>
>>>
>>> On Fri, Jan 24, 2014 at 9:05 AM, Bria
On Fri, Jan 24, 2014 at 9:33 AM, Ryan Hiebert wrote:
>
>
>
> On Thu, Jan 23, 2014 at 7:24 PM, Russell Keith-Magee <
> russ...@keith-magee.com> wrote:
>
>>
>> On Fri, Jan 24, 2014 at 9:05 AM, Brian Neal wrote:
>>
>>> Hello,
>>>
>>> The deprecation timeline says this about Django 1.7:
>>>
>>> "The
On Thu, Jan 23, 2014 at 7:24 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
>
> On Fri, Jan 24, 2014 at 9:05 AM, Brian Neal wrote:
>
>> Hello,
>>
>> The deprecation timeline says this about Django 1.7:
>>
>> "The AUTH_PROFILE_MODULE setting, and the get_profile() method on the
>> User
On Fri, Jan 24, 2014 at 9:05 AM, Brian Neal wrote:
> Hello,
>
> The deprecation timeline says this about Django 1.7:
>
> "The AUTH_PROFILE_MODULE setting, and the get_profile() method on the
> User model, will be removed."
>
> The dev 1.7 release notes say that the new schema migration is schedul
Hello,
The deprecation timeline says this about Django 1.7:
"The AUTH_PROFILE_MODULE setting, and the get_profile() method on the User
model, will be removed."
The dev 1.7 release notes say that the new schema migration is scheduled to
land in 1.7.
Does this mean we cannot use the new schema
13 matches
Mail list logo
