According the documentation, migrations should be backwards compatible, see
https://docs.djangoproject.com/en/1.9/topics/migrations/#supporting-multiple-django-versions.
Hence there shouldn't be any reason to make different versions of any
application for different versions of Django. A
>
>>> Vlastimil
>>>
>>> Dne středa 19. října 2016 1:57:25 UTC+2 Tim Graham napsal(a):
>>>>
>>>> Assuming the problem is makemigrations generating different migrations
>>>> based on the Django version, conditionally adding operations in m
gt;>>
>>> Assuming the problem is makemigrations generating different migrations
>>> based on the Django version, conditionally adding operations in migrations
>>> with some django.VERSION checks may help.
>>>
>>> On Tuesday, October 18, 2016 at 7:1
ations in migrations
>> with some django.VERSION checks may help.
>>
>> On Tuesday, October 18, 2016 at 7:12:02 AM UTC-4, Vlastimil Zíma wrote:
>>>
>>> Hi everyone,
>>>
>>> we are trying in our application to support multiple Django versions,
&
lp.
>
> On Tuesday, October 18, 2016 at 7:12:02 AM UTC-4, Vlastimil Zíma wrote:
>>
>> Hi everyone,
>>
>> we are trying in our application to support multiple Django versions,
>> specifically 1.7 to 1.9. But we encountered a problem with
>> `User.last_l
> based on the Django version, conditionally adding operations in migrations
> with some django.VERSION checks may help.
>
> On Tuesday, October 18, 2016 at 7:12:02 AM UTC-4, Vlastimil Zíma wrote:
>>
>> Hi everyone,
>>
>> we are trying in our application to sup
e are trying in our application to support multiple Django versions,
> specifically 1.7 to 1.9. But we encountered a problem with
> `User.last_login` field. We use custom User model based on
> `AbstractBaseUser` as specified by the documentation. Everything was fine
> in Django 1.7,
Hi everyone,
we are trying in our application to support multiple Django versions,
specifically 1.7 to 1.9. But we encountered a problem with
`User.last_login` field. We use custom User model based on
`AbstractBaseUser` as specified by the documentation. Everything was fine
in Django 1.7, but
virtualenv can be used with mod_wsgi, we are doing so on our
production servers.
see http://code.google.com/p/modwsgi/wiki/VirtualEnvironments for more
information
Cheers,
Dan
On May 3, 8:26 am, Stodge wrote:
> I am aware of virtualenv, but can it be used with mod_wsgi. Time to do
> some readi
I am aware of virtualenv, but can it be used with mod_wsgi. Time to do
some reading. I have minimal control of the target cluster - I don't
know yet if I'm allowed to have a user account; I doubt it. I think I
hand off an RPM to the maintainers and they install it for me. Though
the RPM is allowed
On Monday 03 May 2010 5:33:36 pm Stodge wrote:
> We're about to deploy our Django app on our production Redhat cluster
> using mod_wsgi, earlier than expected. We developed the app using
> Django 1.2b1 because we wanted the multiple database support.
> Unfortunately, the cluster uses Django 1.1.x.
On May 3, 1:03 pm, Stodge wrote:
> We're about to deploy our Django app on our production Redhat cluster
> using mod_wsgi, earlier than expected. We developed the app using
> Django 1.2b1 because we wanted the multiple database support.
> Unfortunately, the cluster uses Django 1.1.x. What are th
We're about to deploy our Django app on our production Redhat cluster
using mod_wsgi, earlier than expected. We developed the app using
Django 1.2b1 because we wanted the multiple database support.
Unfortunately, the cluster uses Django 1.1.x. What are the options for
running two versions on Django
On Wed, Jun 10, 2009 at 4:21 PM, El Marto wrote:
>
> Hi all!
>
> I m trying to run my django app using wsgi, The default django
> installed in the server is 0.97-pre-SVN-6978 and I want to use the
> development one. I inserted the development django path in the wsgi
> file:
> --
> import
Hi all!
I m trying to run my django app using wsgi, The default django
installed in the server is 0.97-pre-SVN-6978 and I want to use the
development one. I inserted the development django path in the wsgi
file:
--
import os, sys
import django.core.handlers.wsgi
sys.path.insert(0, '/home
On Saturday 30 May 2009 17:23:01 Kenneth Gonsalves wrote:
> this problem may not be django related at all, but maybe someone here could
> tell me how to debug it.
>
> I have a VPS on Gandi with several .90 django sites and some running on
> latest trunk. I had set up virtualenv to run the sites on
hi,
this problem may not be django related at all, but maybe someone here could
tell me how to debug it.
I have a VPS on Gandi with several .90 django sites and some running on latest
trunk. I had set up virtualenv to run the sites on trunk. The sites on trunk
run perfectly. The .90 sites als
Thanks for your help I fixed the problem by switching to mod_wsgi (I
should have done that sooner) and by using virtualenv.
And the tutorial here:
http://lethain.com/entry/2009/feb/13/the-django-and-ubuntu-intrepid-almanac/
On 4 apr, 18:56, Karen Tracey wrote:
> On Sat, Apr 4, 2009 at 10:57 AM,
On Sat, Apr 4, 2009 at 10:57 AM, pault wrote:
>
> I have one version 1.02 installed in /var/lib/python-support/
> python2.5/django/ (i am on a debian machine)
> and one version 0.96 in the folder of my project.
Specifics of exactly where you have Django 0.96 installed would have been
helpful
2009/4/4 pault :
>
> I have one version 1.02 installed in /var/lib/python-support/
> python2.5/django/ (i am on a debian machine)
> and one version 0.96 in the folder of my project.
>
> I read the post from Graham but it doesn't seem to work for me it uses
> the 1.02 version.
> http://groups.goo
I have one version 1.02 installed in /var/lib/python-support/
python2.5/django/ (i am on a debian machine)
and one version 0.96 in the folder of my project.
I read the post from Graham but it doesn't seem to work for me it uses
the 1.02 version.
http://groups.google.com/group/django-users/brows
you can add
import sys
sys.path.insert(0, '/your/django-svn/path')
in the 2 line of manage.py file.
2007/12/24, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>
>
> Hi i have 2 projects which one of them uses the svn version of the django
> and
> another uses 0.96.1
>
> How should i handle that situatio
On Dec 24, 9:36 am, [EMAIL PROTECTED] wrote:
> Hi i have 2 projects which one of them uses the svn version of the django and
> another uses 0.96.1
>
> How should i handle that situation. Currently i checouted the svn version and
> created a ln -s to my site-packages version?
>
> How can i have the
Hi i have 2 projects which one of them uses the svn version of the django and
another uses 0.96.1
How should i handle that situation. Currently i checouted the svn version and
created a ln -s to my site-packages version?
How can i have the 0.96.1 when i work with my site and to have svn when i
> In short, a C extension module may cache data from one sub interpreter
> and then use it in the context of a different sub interpreter causing
> incorrect or errornous behaviour. The problem with Decimal support in
> pyscopg falls into this category. It is entirely possible that the OP
> may hav
On 7/20/07, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
>
> For the record, the description which was given to you whereby "if the
> first request served by a thread used the old version of Django, that
> was the version that was used for all subsequent requests on that
> thread" is nonsense. Ther
On Jul 19, 2:07 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On 7/19/07, oggie rob <[EMAIL PROTECTED]> wrote:
>
> > Please, if you've seen the same issue or have any helpful ideas to try
> > to stop the error, let me know.
>
> I think I've seen the same problem (or, at least, an analogou
Thanks for the tip, Niels. I tried that and it didn't work either.
I got to thinking about how likely it would be that mod_python &
interpreters were causing problems. I've used multiple interpreters
for some time and haven't noticed any other strange behaviour. A
little test by printing out the a
In case the problem lies in manipulating the python path inside a
section, perhaps you could play another trick to load the
different versions of django. I am doing as follows, though, not with
Location tags but in VirtualHost sections, and it works for me:
Somewhere on the python path, there is
Thanks for your help, Russ. I updated mod_python (which was probably
overdue anyway), but that didn't fix the problem. I've been looking
for other signs but nothing has surfaced yet.
If anybody else can recall a similar experience, please let me know!
-rob
On Jul 18, 9:07 pm, "Russell Keith-Mag
On 7/19/07, oggie rob <[EMAIL PROTECTED]> wrote:
>
> Please, if you've seen the same issue or have any helpful ideas to try
> to stop the error, let me know.
I think I've seen the same problem (or, at least, an analogous one).
Unfortunately, I can't provide much by way of helpful debug or
solutio
I've run into a problem that appears to be caused by multiple django
versions running on the same server. I have a preforked mod_python
installation and the problem I'm seeing is this: after using the trunk-
based application, I try to use the 0.91-based application and get a
500 error
orestis <[EMAIL PROTECTED]> writes:
> Hello,
>
> I think this will be easy to do, but I just want to check:
>
> Is it possible to have different Django versions on the same host, and
> point my sites to different versions ?
>
> I'd like to use bleedi
On Mon, 2007-05-14 at 11:09 +, orestis wrote:
> Hello,
>
> I think this will be easy to do, but I just want to check:
>
> Is it possible to have different Django versions on the same host, and
> point my sites to different versions ?
>
> I'd like to use ble
orestis wrote:
> Hello,
>
> I think this will be easy to do, but I just want to check:
>
> Is it possible to have different Django versions on the same host, and
> point my sites to different versions ?
>
> I'd like to use bleeding edge for personal stuff (yay f
Hello,
I think this will be easy to do, but I just want to check:
Is it possible to have different Django versions on the same host, and
point my sites to different versions ?
I'd like to use bleeding edge for personal stuff (yay for
experimentation) but for any work-related material, I
Thanks everyone for the suggestion.
-Rob
--~--~-~--~~~---~--~~
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
James Bennett wrote:
> On 9/15/06, Rob Hudson <[EMAIL PROTECTED]> wrote:
>> We have an active project we're coding against 0.95. Fast forward to 6
>> months or so after 1.0 is released and we have a few projects underway
>> based on 1.0. We have no time or money to bring the old project up to
>>
On 9/15/06, Rob Hudson <[EMAIL PROTECTED]> wrote:
> We have an active project we're coding against 0.95. Fast forward to 6
> months or so after 1.0 is released and we have a few projects underway
> based on 1.0. We have no time or money to bring the old project up to
> 1.0 support. Is there a w
On 9/15/06, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> Here's something I realized we're going to have to face one day as I
> read the post on the new Forms and Manipulators...
>
> We have an active project we're coding against 0.95. Fast forward to 6
> months or so after 1.0 is released and we ha
Here's something I realized we're going to have to face one day as I
read the post on the new Forms and Manipulators...
We have an active project we're coding against 0.95. Fast forward to 6
months or so after 1.0 is released and we have a few projects underway
based on 1.0. We have no time or
True, but I have found it forces me to look at django code more, which
helps me learn it more. Guess its not for everyone.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group,
On Fri, Feb 24, 2006 at 01:04:31PM -, ChaosKCW wrote:
> So if your starting from scratch like
> me, and your willilng to put up with a few bugs, the magic removal is
> the way to go.
The problem I see with the m-r path for a newbie is that all the
docs, tutorials, and examples are pre-m-r ..
On Saturday 25 Feb 2006 6:44 am, oggie rob wrote:
> If you plan to deploy anytime in the next month or two (yes, this
> is a real possibility with Django!),
month or two? you mean there are people out there who take up to a
*month* to deploy a django app??
--
regards
kg
http://www.livejournal
On 2/24/06, Michal <[EMAIL PROTECTED]> wrote:
> Hello,
> I would like start with Django, but I don't know which version I should
> to download:
> - stable 0.91?
> - latest development from trunk?
> - magic-removal branch?
Go with the latest trunk development -- it's the most stable and has
the la
> - latest development from trunk?
If you plan to deploy anytime in the next month or two (yes, this is a
real possibility with Django!), you should start with trunk but settle
on a revision before you get too far into the project. I wouldn't
recommend updating from trunk once you've deployed unt
Its a trade off, I chose the magic removal branch, because the
syntactical changes really appeal to me. The models are a lot cleaner
and DB API too.
However it does have problems. And when 0.92 comes out you will have to
change to the new syntax anyways. So if your starting from scratch like
me,
On Friday 24 Feb 2006 1:40 pm, Michal wrote:
> - latest development from trunk?
this one
--
regards
kg
http://www.livejournal.com/users/lawgon
tally ho! http://avsap.org.in
ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!
--~--~-~--~~~---~--~~
You received this message because you are subsc
The latest development branch works utterly fine for me. I update from it maybe once a day and haven't run into any problems yet (touch wood).AFAIK: magic-removal is changing all the time. Lots of refactoring. So if you're just starting out, I'd recommend the "trunk".
Ij.On 2/24/06, Michal <[EMAIL
Hello,
I would like start with Django, but I don't know which version I should
to download:
- stable 0.91?
- latest development from trunk?
- magic-removal branch?
Thank you for any advice.
Regards
Michal
--~--~-~--~~~---~--~~
You received this message because y
50 matches
Mail list logo
