Re: Upgrading Django from 3.2.16 to 4.1.x

Try: https://github.com/browniebroke/django-codemod or https://github.com/adamchainz/django-upgrade On Tue, 17 Jan 2023 at 05:18, 'Ellinghaus, Lance J' via Django users < django-users@googlegroups.com> wrote: > I will be upgrading from Django 3.2.16 to 4.1.x and wanted to know if > anyone has an

Re: Upgrading Django from 3.2.16 to 4.1.x

Yes, you should be able to upgrade from Django 3.2.16 to 4.1.x by simply installing the Django 4.1.x software and running the makemigrations command. It's always a good practice to make a backup of your database and application before upgrading, just in case any errors occur during the upgrade proc

Upgrading Django from 3.2.16 to 4.1.x

I will be upgrading from Django 3.2.16 to 4.1.x and wanted to know if anyone has any suggestions. I am using oracle as the backend. The release notes do not go into much detail. Do I just need to install the Django 4.1.x software and run the makemigrations to do the upgrade? Thank you, Lance Ell

Re: django.db.migrations.exceptions.NodeNotFoundError while upgrading django

I am facing the same issue.. Anyone get the solution for the same? Please domlet me know if anyone get the solution. On Monday, 23 April 2018 12:08:06 UTC+5:30, Akhi wrote: > > I am upgrading my django project from django1.5 to django1.11.10. while > upgrading when I run ./manange.py migrate I am

Re: Upgrading django from 1.8 to 2.2.0

i dont know why any time i run my django website with opra_mini browser it always bring source code ‪On Sun, Feb 2, 2020 at 7:49 AM ‫אורי‬‎ wrote:‬ > By the way, each time upgrade to the latest release of each version. So > it's 2.2.9 you should use. And all the latest versions on > https://www.

Re: Upgrading django from 1.8 to 2.2.0

When you upgrade Django with pip, you can install the latest version of 1.9 with `pip install --upgrade "Django>=1.8,<1.10"` and then the same for each version, until you want the latest version of 2.2 and then use "Django>=1.8,<3.0". (actually the 1.8 is not needed here, you can also use 2.2 etc.)

Re: Upgrading django from 1.8 to 2.2.0

By the way, each time upgrade to the latest release of each version. So it's 2.2.9 you should use. And all the latest versions on https://www.djangoproject.com/download/ (1.9.13 etc.) אורי u...@speedy.net On Fri, Jan 31, 2020 at 12:53 PM Santhosh sridhar wrote: > Hi, > Im upgrading my django pr

Re: Upgrading django from 1.8 to 2.2.0

Upgrade Django from 1.8 to 1.9, then 1.10 etc. until 2.2. Each time run makemigratons and migrate and run your tests to see that everything works. And if there is a problem with a specific migration - maybe you have to edit it manually like Mike suggested. >From my experience, it takes time to upg

Re: Upgrading django from 1.8 to 2.2.0

On 31/01/2020 9:53 pm, Santhosh sridhar wrote: Hi, Im upgrading my django project from 1.8 to 2.2.0. I have done the below changes. 1. Added on_delete to all the Foreign Key fields 2. Changed the url reverse import as from django.urls import reverse 3. Included path/re_path instead of url in a

Upgrading django from 1.8 to 2.2.0

Hi, Im upgrading my django project from 1.8 to 2.2.0. I have done the below changes. 1. Added on_delete to all the Foreign Key fields 2. Changed the url reverse import as from django.urls import reverse 3. Included path/re_path instead of url in all the app's url files. 4. Changed the MIDDLEWARE

Re: Upgrading Django from 2.1 to 2.2 - strings are not translated

Hi issuer, Plz check https://docs.djangoproject.com/en/2.2/topics/auth/passwords/#password-validatio4n On Fri, Nov 1, 2019, 14:46 אורי wrote: > Hi, > > Take a look at this ticket: > https://code.djangoproject.com/ticket/30939 > > This issue prevents me from upgrading Django

Upgrading Django from 2.1 to 2.2 - strings are not translated

Hi, Take a look at this ticket: https://code.djangoproject.com/ticket/30939 This issue prevents me from upgrading Django to 2.2. Currently everything works with Django 2.1 but not with Django 2.2. אורי u...@speedy.net -- You received this message because you are subscribed to the Google

Issue in upgrading Django-cms 3.4.2 to 3.6.0

Hi, Please find the issue details below. I am upgrading my website from *python2.7, django1.8.17, django-cms 3.4.2* to *python2.7, django1.1.21, django-cms 3.6.0* when I run *python manage.py runserver* It gives me following error. *django.template.library.InvalidTemplateLibrary: Invalid temp

Re: Upgrading Django from 1.11 to 2.2

>From the page Tim linked: "If you’re upgrading through more than one feature version (e.g. A.B to A.B+2), it’s usually easier to upgrade through each feature release incrementally (A.B to A.B+1 to A.B+2) rather than to make all the changes for each feature release at once. For each feature releas

Re: Upgrading Django from 1.11 to 2.2

I accept Tim's advice to upgrade from one major version to the next. Even if I want to upgrade from 1.11 to 2.2, I have to upgrade first to 2.0 and then 2.1 and only then 2.2. It makes sense. אורי u...@speedy.net On Tue, Apr 2, 2019 at 4:44 PM Derek wrote: > I agree; and the reason for Django

Re: Upgrading Django from 1.11 to 2.2

I agree; and the reason for Django moving to LTS releases was so that you would be able to upgrade from one LTS to the next. Hence the OP (and others like me I am sure) asking how that can be done - we are looking for specific advice or instructions (and less about "general" guidelines). On Tu

Re: Upgrading Django from 1.11 to 2.2

always go for 2nd last or 3rd last release of any framework or any language it will be more stable but if you want to go with 2.2 you can because it comes with LTS On Friday, March 29, 2019 at 2:22:10 PM UTC+5:30, Uri Even-Chen wrote: > > Hi, > > I want to upgrade Django from 1.11 to 2.2. Do I h

Re: Upgrading Django from 1.11 to 2.2

always go for 2nd last or 3rd last release of any frame it will be more stable but if you want to go 2.2 you can because it comes with LTS On Friday, March 29, 2019 at 2:22:10 PM UTC+5:30, Uri Even-Chen wrote: > > Hi, > > I want to upgrade Django from 1.11 to 2.2. Do I have to upgrade first to >

Re: Upgrading Django from 1.11 to 2.2

The advice is to go from one the major version to the next. Don't try to skip versions. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...

Re: Upgrading Django from 1.11 to 2.2

). On Saturday, 30 March 2019 15:36:48 UTC+2, Tim Graham wrote: > > Consider the "Upgrading Django to a newer version" guide. > https://docs.djangoproject.com/en/stable/howto/upgrade-version/ > > On Friday, March 29, 2019 at 4:52:10 AM UTC-4, Uri Even-Chen wrote: >>

Re: Upgrading Django from 1.11 to 2.2

Consider the "Upgrading Django to a newer version" guide. https://docs.djangoproject.com/en/stable/howto/upgrade-version/ On Friday, March 29, 2019 at 4:52:10 AM UTC-4, Uri Even-Chen wrote: > > Hi, > > I want to upgrade Django from 1.11 to 2.2. Do I have to upgrade first to

Re: Upgrading Django from 1.11 to 2.2

you can upgrade directly from 1.11 to 2.2, but some of third party packages may not support Django 2.2 ‪On Fri, Mar 29, 2019 at 2:22 PM ‫אורי‬‎ wrote:‬ > Hi, > > I want to upgrade Django from 1.11 to 2.2. Do I have to upgrade first to > 2.0 and then to 2.1, or can I upgrade directly from 1.11 to

Re: Upgrading Django from 1.11 to 2.2

I'd suggest not worrying too much about upgrading to 2.2 right away. Since it's going to be an LTS release, the projects your project depends on will probably consider adding 2.2 support fairly fast. But if you want to give it a shot anyway, I'd suggest taking a look at what changed from 1.11 to 2

Re: Upgrading Django from 1.11 to 2.2

First use 'pip freeze' in your virtual env to see all the packages installed. Then checkout their official, latest documentation to see whether they support django2.1 or not. Even if all them do, you might need to make a lot of changes in your code after upgrade. And no, you dont need to install

Upgrading Django from 1.11 to 2.2

Hi, I want to upgrade Django from 1.11 to 2.2. Do I have to upgrade first to 2.0 and then to 2.1, or can I upgrade directly from 1.11 to 2.2? By the way, we use many third-party packages and I'm not sure which version of Django they support. Maybe not all of them already support Django 2.2. Than

Re: Form no longer validates after upgrading django from 2.0.5 to 2.1. Should I report a bug?

Fair enough. I think the behavior makes sense the way it is, so I'll leave it. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegro

Re: Form no longer validates after upgrading django from 2.0.5 to 2.1. Should I report a bug?

I think the behavior changed in https://github.com/django/django/commit/5fa4f40f45fcdbb7e48489ed3039a314b5c961d0. The old behavior looks like a bug to me (can you explain why it would be expected?) and we don't generally document bug fixes in the release notes. On Monday, December 31, 2018 at 8

Form no longer validates after upgrading django from 2.0.5 to 2.1. Should I report a bug?

Hello, In our project we have a Model with this field: has_drivers_license = models.BooleanField(verbose_name=_('Heeft rijbewijs'), default=False, choices=BOOL_CHOICES) and we have a ModelForm, where this field is used: fields = [*...* 'has_drivers_license', ] and we use a radio se

Re: Upgrading Django

See: https://docs.djangoproject.com/en/1.10/ref/templates/upgrading/ On Friday, 13 July 2018 14:36:52 UTC+2, Ghiath ghanem wrote: > > I'm working on small project, (Automatic Calender for the near future > events from Tweets). > I have upgraded to Python 3.4.3, and Now i would like to upgrade D

Re: Upgrading Django

please share your settings.py . maybe you need to add or edit some middleware in settings.py On Fri, 13 Jul 2018, 14:36 Ghiath ghanem, wrote: > I'm working on small project, (Automatic Calender for the near future > events from Tweets). > I have upgraded to Python 3.4.3, and Now i would like to

Upgrading Django

I'm working on small project, (Automatic Calender for the near future events from Tweets). I have upgraded to Python 3.4.3, and Now i would like to upgrade Django from 1.5.11 to 2.0.7. Almost everything went well until i got this error: ?: (admin.E402) 'django.contrib.auth.context_processors.aut

RE: django.db.migrations.exceptions.NodeNotFoundError while upgrading django

Did you try running makemigrations first? ./manage.py makemigrations From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On Behalf Of Akhi Sent: Monday, April 23, 2018 1:38 AM To: Django users Subject: django.db.migrations.exceptions.NodeNotFoundError while upgrading

django.db.migrations.exceptions.NodeNotFoundError while upgrading django

I am upgrading my django project from django1.5 to django1.11.10. while upgrading when I run ./manange.py migrate I am getting django.db.migrations.exceptions.NodeNotFoundError django.db.migrations.exceptions.NodeNotFoundError: Migration account.0004_auto_20180419_1309 dependencies reference no

Re: Warning while upgrading Django to 1.11.3

Thank you Andréas, this is a bug! I didn't notice it. I'll remove it. Uri. *Uri Even-Chen* [image: photo] Phone: +972-54-3995700 Email: u...@speedy.net Website: http://www.speedysoftware.com/uri/en/

Re: Warning while upgrading Django to 1.11.3

Hi, In your match urls file, you include urlpatterns twice. urlpatterns += [ url(r'^matches/', include('speedy.match.matches.urls', namespace='matches')), url(r'^', include('speedy.match.accounts.urls', namespace='accounts')), url(r'^admin/', admin.site.urls), url(r'^i18n/', include('django.conf.

Warning while upgrading Django to 1.11.3

Hi friends, I upgraded Django from 1.10.7 to 1.11.3 and I got these warnings while running tests: speedy\match>manage.py test Creating test database for alias 'default'... System check identified some issues: WARNINGS: ?: (urls.W005) URL namespace 'about' isn't unique. You may not be able to rev

Re: upgrading django 1.11 warning list

Yes, it's safe to add that to migrations. https://docs.djangoproject.com/en/dev/releases/1.9/#foreignkey-and-onetoonefield-on-delete-argument On Tuesday, July 25, 2017 at 8:55:24 AM UTC-4, pablochud wrote: > > Hi! > It showed me warning related to 'on_delete' as required arg for ForeignKey > in

upgrading django 1.11 warning list

Hi! It showed me warning related to 'on_delete' as required arg for ForeignKey in migration files. is it safty to change migration file manually or is there alternative way to bypass warning? -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Re: Upgrading Django (to 1.7)

depend on - Upgrading Python itself - Release notes for each version -- Backwards-incompatible changes -- Deprecated features -- New features - Use new Check Framework to enforce coding standards - etc. See also: - http://andrewsforge.com/article/upgrading-django-to-17/checklist Than

Re: Upgrading Django (to 1.7)

no Windows or Gates. On 11/25/14 3:03 PM, Andrew Pinkham wrote: Hi, I have just updated Upgrading Django (to 1.7) Part III: Django 1.7's New Features. The App Registry and System Check Framework sections have been updated to be more accessible. For the article: afrg.co/updj17/a3/ For all o

Re: Upgrading Django (to 1.7)

Excellent resource. Thanks Andrew. On Tue, Nov 25, 2014 at 10:16 PM, Andrew Pinkham wrote: > Hi, > Upgrading Django (to 1.7) Part IV: Upgrade Strategies is now available! > > For the article: > afrg.co/updj17/a4/ > > For all of the material: > afrg.co/updj17/

Re: Upgrading Django (to 1.7)

Hi, Upgrading Django (to 1.7) Part IV: Upgrade Strategies is now available! For the article: afrg.co/updj17/a4/ For all of the material: afrg.co/updj17/ I've also provided a checklist of upgrade steps, as well as a list of all the links used throughout the series: afrg.co/updj

Re: Upgrading Django (to 1.7)

Hi, I have just updated Upgrading Django (to 1.7) Part III: Django 1.7's New Features. The App Registry and System Check Framework sections have been updated to be more accessible. For the article: afrg.co/updj17/a3/ For all of the material: afrg.co/updj17/ Part IV will be available b

Re: Upgrading Django (to 1.7)

Sounds good! Thanks! --Fred Fred Stluka -- mailto:f...@bristle.com -- http://bristle.com/~fred/ Bristle Software, Inc -- http://bristle.com -- Glad to be of service! Open Source: Without walls and fences, we need no Windows

Re: Upgrading Django (to 1.7)

Hi, Thanks to feedback from Fred and a few others, I've started editing Part III to make it more accessible. Part IV was originally set to be published today. Unfortunately, it is not ready to be published. As soon as the new Part III and Part IV are available, I will let you know. Thanks, And

Re: Upgrading Django (to 1.7)

Andrew, Yes, that explains a lot. I'd recommend including this explanation in one of the articles of your current series. BTW, one other thing to keep in mind is that we 1.4 users don't know what an apps.py file is, so we don't appreciate not having to create one, since we never did before. Th

Re: Upgrading Django (to 1.7)

Hi Fred, Thanks again for the positive feedback! I'm sorry I lost you at the App Registry section. I'm afraid I can't recommend an article to help with the topic, either. Given your questions, I can see I missed the mark. Let me give it another go (warning: this is neither technically reviewed

Re: Upgrading Django (to 1.7)

On 10/8/14 11:30 PM, Andrew Pinkham wrote: Hi, Upgrading Django (to 1.7) Part III: Django 1.7's New Features is now available! For the article: afrg.co/updj17/a3/ For all of the material: afrg.co/updj17/ Any feedback appreciated. I hope you find the material helpful. Andrew A

Re: Upgrading Django (to 1.7)

Hi, Upgrading Django (to 1.7) Part III: Django 1.7's New Features is now available! For the article: afrg.co/updj17/a3/ For all of the material: afrg.co/updj17/ Any feedback appreciated. I hope you find the material helpful. Andrew -- You received this message because you are subsc

Re: Upgrading Django (to 1.7)

Hi Fred, Thanks again for the input! Glad you liked Part II. Andrew -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. T

Re: Upgrading Django (to 1.7)

On 10/1/14 11:36 PM, Andrew Pinkham wrote: Any feedback appreciated. I hope you find the material helpful. Andrew, Excellent 2nd article. Thanks! I especially liked the clear explanation of how South migrations interact badly with initial_data fixtures. OK to use fixtures, but load them exp

Re: Upgrading Django (to 1.7)

Stodge, Part II focuses on migrations, and deals in passing with AppConfig objects via data-migrations. Part III will take a closer look at the app registry, as we will create a custom AppConfig objects for `roundtable`. There is a (very) short section in Part III about import problems caused by

Re: Upgrading Django (to 1.7)

Carsten, Thank you for reading and for the positive feedback! Andrew -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com.

Re: Upgrading Django (to 1.7)

I will read this thanks. Does it cover this issue? django.core.exceptions.AppRegistryNotReady: The translation infrastructure > cannot be initialized before the apps registry is ready. Check that you > don't make non-lazy gettext calls at import time. > I don't know if this has been a pain to m

Re: Upgrading Django (to 1.7)

Hi Andrew, Am 2014-10-02 um 05:36 schrieb Andrew Pinkham: Any feedback appreciated. I hope you find the material helpful. Also from me a hearty thanks for your article series! It's very helpful, and very much appreciated! Best regards, Carsten -- Cafu Engine * www.cafu.de an open-source 3D

Re: Upgrading Django (to 1.7)

Hi, Upgrading Django (to 1.7) Part II: Migrations in Django 1.6 and 1.7 is now available! For the article: afrg.co/updj17/a2/ For all of the material: afrg.co/updj17/ Any feedback appreciated. I hope you find the material helpful. Andrew -- You received this message because you are

Re: Re: Upgrading Django (to 1.7)

Fred, thanks a jillion for the excellent advice! I obviously missed that bit in the data migration boilerplate. On Saturday, September 27, 2014 9:29:10 AM UTC-5, Fred Stluka wrote: > > Bob, > > Are you referring directly to the models by name in the data > migrations? That could be the probl

Re: Upgrading Django (to 1.7)

Hi Bob, Thank you! I spend a lot of Part II talking about schema and data migrations in both South and native Django 1.7 migrations. When building data migrations, you should be using historical models. In Django 1.7, you can request these models directly from the app registry built on the fly

Re: Upgrading Django (to 1.7)

Benjamin, Thank you! The next two parts of the article will focus on why certain changes were made. Please let me know if you think there were changes that I should have written about. Depending on my schedule and feedback, I would be willing to consider adding to the material if I've missed an

Fwd: Re: Upgrading Django (to 1.7)

Bob, Are you referring directly to the models by name in the data migrations? That could be the problem, because yes, the migration would be using the latest models at the time that the migration is executed, not the models as they stood at the time that the migration was written. There's a war

Re: Upgrading Django (to 1.7)

The problem we ran into was not with the order of migrations, it was that all of the migrations were running with the latest models.py code. The data migration was trying to move data from one model field to another model field, and the "from" field had been deleted from models.py. This was a

Re: Upgrading Django (to 1.7)

Bob, You can control the order in which migrations run. For South, see "depends_on" and "needed_by": - http://south.readthedocs.org/en/latest/dependencies.html For Django 1.7 migrations, see "dependencies": - https://docs.djangoproject.com/en/dev/topics/migrations/#dependencies --Fred

Re: Upgrading Django (to 1.7)

Andrew, thanks for the article, and the more-to-come. When you get to data migrations, you might want to cover a problem I ran into with them: when I had a data migration in the middle of a sequence of other migrations, and then later wanted to set up a new environment, which meant running all

Re: Upgrading Django (to 1.7)

Great summary - looking forward to the rest. Especially like some of the backgrounder insights also explaining "why" certain things were done. I think this often helps developers understand and use features better than even the otherwise excellent and detailed online docs. Wonder if the Django doc

Re: Upgrading Django (to 1.7)

Sabine, I'm not sure about the new 1.7 Migrations, but with South, restarting your migrations is easy. I'm currently doing it on my project, because we have a long convoluted history of changes before and after we started using South, and have made some mistakes along the way (like editing migra

Re: Upgrading Django (to 1.7)

Fred, Thank you! Good luck with the upgrade! Andrew -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this

Re: Upgrading Django (to 1.7)

Hi Sabine, Thank you! It is really nice getting positive feedback. The migrations section (Part II next week!) is a very basic introduction, aimed at people who have never used South or native migrations. One of the key takeaways (hopefully) of the article is the fact that it is easy to manually

Re: Upgrading Django (to 1.7)

Andrew, Good stuff! Thanks! We're still on 1.4, but planning a move soon to 1.7. Very helpful. --Fred Fred Stluka -- mailto:f...@bristle.com -- http://bristle.com/~fred/ Bristle Software, Inc -- http://bristle.com -- Gla

Re: Upgrading Django (to 1.7)

Dear Andrew, I read your article and it is great. I am really looking forward to your followups. I was hoping for something like this went I attended Django Con Europe. I struggle with the understanding the migrations the most. Usually in the early phases of development I do not want migration

Upgrading Django (to 1.7)

Hi, I am writing a series of articles based on the presentation I gave at DjangoCon US 2014. I put the first article online earlier today, and figured members of this list might be interested in the material. For all of the material: afrg.co/updj17/ For the article: afrg.co/updj17/a1/

Re: Upgrading django on a mac

On Mon, Apr 9, 2012 at 4:53 PM, William Deegan wrote: > Larry, > > Why not use virtualenv? Or buildout? I am not familiar with either one of those. I use my mac for development for a specific client. I need my environment to match their's as much as possible. They had been using -r 13034 from SVN

Re: Upgrading django on a mac

Larry, Why not use virtualenv? Or buildout? -Bill On Apr 7, 2012, at 3:02 PM, Jonathan Baker wrote: > Ah, good to know. Apologies, but I glanced over your original code to quickly > and thought you renamed the directory. Glad it worked out. > > On Sat, Apr 7, 2012 at 3:54 PM, Larry Martell wr

Re: Upgrading django on a mac

Ah, good to know. Apologies, but I glanced over your original code to quickly and thought you renamed the directory. Glad it worked out. On Sat, Apr 7, 2012 at 3:54 PM, Larry Martell wrote: > On Sat, Apr 7, 2012 at 3:46 PM, Jonathan Baker > wrote: > > I'm guessing that your $PATH is configured t

Re: Upgrading django on a mac

On Sat, Apr 7, 2012 at 3:46 PM, Jonathan Baker wrote: > I'm guessing that your $PATH is configured to look for django in it's old > location, and not the new one. No it's not that (the new location is the same as the old). But I figured it out - the django python package is apparently a subdirect

Re: Upgrading django on a mac

I'm guessing that your $PATH is configured to look for django in it's old location, and not the new one. On Sat, Apr 7, 2012 at 3:33 PM, Larry Martell wrote: > I'm on a mac, running Mac OS X Version 10.5.8 (Leopard). I was running > django -r 13034 that I got from SVN. I am trying to upgrade to 1

Upgrading django on a mac

I'm on a mac, running Mac OS X Version 10.5.8 (Leopard). I was running django -r 13034 that I got from SVN. I am trying to upgrade to 1.4 from git. After I upgrade, python can no longer find django. Here's what I did: $ cd /usr/local/lib/python2.6/dist-packages $ sudo mv django/ django-13034 $ sud

NoReverseMatch raised after upgrading django to trunk

Hello, I've just updated django to the las revision and suddenly I'm getting a NoReverseMatch when using the reverse funcion. This is the line of the code: return HttpResponseRedirect(reverse('app.views.info', args=[p.id,])) And this is the url: (r'^any-path-(?P\d)\.html$', 'info'), Does any

Re: upgrading django

On Friday 03 April 2009 12:26:30 Miguel wrote: > thank you. It is not an easy upgrade. It may take long time to do it... > Maybe the differences between versions are no so big ... I have some .90 sites to upgrade to trunk. I finally decided to rewrite everything and manually migrate the db with

Re: upgrading django

thank you. It is not an easy upgrade. It may take long time to do it... Maybe the differences between versions are no so big ... Miguel On Fri, Apr 3, 2009 at 12:40 AM, John Baker wrote: > > I did this over dec/jan for an inherited app.. it was an absolute > nightmare.. i had to rewrite huge c

Re: upgrading django

I did this over dec/jan for an inherited app.. it was an absolute nightmare.. i had to rewrite huge chunks of it.. It really would depend on how many hacks the original app had though. Unfortunately, I inherited lots of obscure shortcuts and extensions that became incompatible so most of it stopp

Re: upgrading django

On 02-Apr-09, at 8:57 PM, Miguel wrote: > I have seem new django versions improve the performance of web > applications. I have a huge web aplication and I m thinking about > changing it. How hard would be to upgrade django 0.96 to the newest > one? Has it backward compatibility? The porting

upgrading django

Hello everybody, I have seem new django versions improve the performance of web applications. I have a huge web aplication and I m thinking about changing it. How hard would be to upgrade django 0.96 to the newest one? Has it backward compatibility? thank you very much, Miguel Miguel Sent fro