Larry
I saw that after I sent it and thought .. just as well I signed my name
after the apology.
Mike
On 4/04/2016 11:15 PM, Larry Martell wrote:
On Sun, Apr 3, 2016 at 7:31 PM, Mike Dewhirst wrote:
On 4/04/2016 12:58 AM, Larry Martell wrote:
I import models in the top level of each app
On Sun, Apr 3, 2016 at 7:31 PM, Mike Dewhirst wrote:
> On 4/04/2016 12:58 AM, Larry Martell wrote:
>>>
>>> I import models in the top level of each app so I can say "from app
>>> import
>>> >this, that, other" and it works fine. Django 1.8.
Please watch your attribution. I did not write that, you
On 4/04/2016 12:58 AM, Larry Martell wrote:
I import models in the top level of each app so I can say "from app import
>this, that, other" and it works fine. Django 1.8.
The above is wrong. I don't import models at the top level of each app.
In fact I import them at the top of each models modu
On Sun, Apr 3, 2016 at 2:52 AM, Mike Dewhirst wrote:
> On 3/04/2016 11:01 AM, Larry Martell wrote:
>>
>> On Wed, Mar 30, 2016 at 10:07 AM, Fred Stluka wrote:
>>>
>>> Roger,
>>>
>>> Yeah, I too have a large project that I'll hopefully be migrating
>>> from 1.4 to 1.9 soon.
>>>
>>> It's about 3.5 y
On 3/04/2016 11:01 AM, Larry Martell wrote:
On Wed, Mar 30, 2016 at 10:07 AM, Fred Stluka wrote:
Roger,
Yeah, I too have a large project that I'll hopefully be migrating
from 1.4 to 1.9 soon.
It's about 3.5 years worth of work, over 200,000 lines of code
in about 1000 Python source file and D
On Wed, Mar 30, 2016 at 10:07 AM, Fred Stluka wrote:
> Roger,
>
> Yeah, I too have a large project that I'll hopefully be migrating
> from 1.4 to 1.9 soon.
>
> It's about 3.5 years worth of work, over 200,000 lines of code
> in about 1000 Python source file and Django template files.
>
> So any ti
As stated above, take small steps. Take the time to read the release notes
for each minor version. Most of the minor versions are bug fixes and you
can scan through them.
Pay close attention to migrations if using South. In Django 1.7 South is
not used. Django incorporated migrations into
Wednesday, March 30, 2016 1:06:45 PM
Subject: Re: Migrating older 1.4 project to 1.9
I have already suggested this approach to someone with a similar problem:
upgrade one version at a time. I’m sure it is possible to find older versions;
1. upgrade to the next minor release (1.4 => 1.5, et
I have already suggested this approach to someone with a similar problem:
upgrade one version at a time. I’m sure it is possible to find older
versions; 1. upgrade to the next minor release (1.4 => 1.5, etc), 2. do the
necessary adjustments, 3. goto 1.
It may be a lot of work, but at the end of th
Roger,
Yeah, I too have a large project that I'll hopefully be migrating
from 1.4 to 1.9 soon.
It's about 3.5 years worth of work, over 200,000 lines of code
in about 1000 Python source file and Django template files.
So any tips you come up with will be invaluable. Please post
anything you le
We feel your pain. If you do it, and write down how it goes, we would be
grateful.
https://github.com/valnet/valuenetwork
On Tuesday, March 29, 2016 at 4:19:59 PM UTC-5, Roger Dunn wrote:
>
> I've inherited a moderately large project written 2 years ago using Django
> 1.4, and wondering if it is
We recommend going one major version at a time:
https://docs.djangoproject.com/en/stable/howto/upgrade-version/
On Tuesday, March 29, 2016 at 5:19:59 PM UTC-4, Roger Dunn wrote:
>
> I've inherited a moderately large project written 2 years ago using Django
> 1.4, and wondering if it is worth cre
I've inherited a moderately large project written 2 years ago using Django
1.4, and wondering if it is worth creating a fresh 1.9 project and porting
in the old code, or doing an in-place upgrade to 1.9?
I have it running on 1.4 'as is' but if I run* python manage.py migrate* it
comes unglued a
13 matches
Mail list logo
