search

google-code-export / stoqs

Automatically exported from code.google.com/p/stoqs
GNU General Public License v3.0
1 stars 1 forks source link

Upgrade Django #44

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Visit the django documentation page for version 1.3: 
https://docs.djangoproject.com/en/1.3/contents/
2. Observe the warning at the top of the page: This document is for an insecure 
version of Django that is no longer supported. Please upgrade to a newer 
release!

Minor version upgrades require reading the release notes for each version. 
Initial perusal indicates that some source code and configuration changes will 
be required. The upgrade can be implemented on a branch of the Mercurial 
repository and then merged with the main trunk.

Original issue reported on code.google.com by MBARIm...@gmail.com on 28 Feb 2014 at 10:37

GoogleCodeExporter commented 9 years ago 
An upgrade should also fix the problem of libgeos failing to parse a version 
number with a release candidate number:

dev/stoqshg/venv-stoqs/lib/python2.6/site-packages/django/contrib/gis/geos/libge
os.py", line 113, in geos_version_info
    if not m: raise GEOSException('Could not parse version info string "%s"' % ver)
django.contrib.gis.geos.error.GEOSException: Could not parse version info 
string "3.4.2-CAPI-1.8.2 r3921"

Original comment by MBARIm...@gmail.com on 11 Mar 2014 at 8:52

GoogleCodeExporter commented 9 years ago 
Working from a bare-bones CentOS 6.6 iso copied from RedHat, named "CentOS 
64-bit" in VMware on my MacBook Pro.

Installed PostgreSQL-9.3 on top of a partitioned file system - put instructions 
in SEVER instruction file in the repo.

Installed Python 2.7 and 3.4 following instructions at 
https://www.digitalocean.com/community/tutorials/how-to-set-up-python-2-7-6-and-
3-3-3-on-centos-6-4

Finished reading http://twoscoopspress.org/products/two-scoops-of-django-1-6

Lots of good ideas there for better test coverage, class-based-views, REST 
apis, CI and stuff. Let's get upgraded to Django 1.7 and then we can do these 
things. In getting dev environment setup I will update other components as 
well, e.g. Mapserver, PostGIS, ...

Original comment by MBARIm...@gmail.com on 3 Feb 2015 at 12:31

GoogleCodeExporter commented 9 years ago 
Created "django17upgrade" branch and pushed first change set:

hg branch django17upgrade
hg commit ...
hg push -f

Original comment by MBARIm...@gmail.com on 3 Feb 2015 at 3:44