[Python-modules-commits] r6383 - in packages/python-django/trunk/debian (11 files)
netzwurm at users.alioth.debian.org
netzwurm at users.alioth.debian.org
Thu Aug 28 17:28:15 UTC 2008
Date: Thursday, August 28, 2008 @ 17:28:14
Author: netzwurm
Revision: 6383
deleting and adding files
Added:
packages/python-django/trunk/debian/python-django-doc.doc-base
packages/python-django/trunk/debian/python-django-doc.examples
packages/python-django/trunk/debian/python-django-doc.install
packages/python-django/trunk/debian/python-django.README.Debian
packages/python-django/trunk/debian/python-django.docs
packages/python-django/trunk/debian/python-django.install
packages/python-django/trunk/debian/python-django.manpages
Deleted:
packages/python-django/trunk/debian/README.Debian
packages/python-django/trunk/debian/docs
packages/python-django/trunk/debian/install
packages/python-django/trunk/debian/manpages
Deleted: packages/python-django/trunk/debian/README.Debian
===================================================================
--- packages/python-django/trunk/debian/README.Debian 2008-08-28 17:24:05 UTC (rev 6382)
+++ packages/python-django/trunk/debian/README.Debian 2008-08-28 17:28:14 UTC (rev 6383)
@@ -1,164 +0,0 @@
-0.95 -> 0.96
-============
-
-Information here has been gathered from:
- http://www.djangoproject.com/documentation/release_notes_0.96/
-and
- http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges
-
-Backwards Incompatible Changes
-------------------------------
-
- Database constraint names changed
- =================================
-
- As of [3512], the format of the constraint names Django generates for
- foreign key references changed slightly. These names are only used
- sometimes, when it is not possible to put the reference directly on the
- affected column, so this is not always visible.
-
- The effect of this change is that manage.py reset app_name and similar
- commands may generate SQL with invalid constraint names and thus generate
- an error when run against the database (the database server will complain
- about the constraint not existing). To fix this, you will need to tweak the
- output of manage.py sqlreset app_name to match the correct constraint names
- and pass the results to the database server manually.
-
- Backslash escaping changed
- ==========================
-
- As of [3552], the Django database API now escapes backslashes given as
- query parameters. If you have any database API code that match backslashes,
- and it was working before (despite the broken escaping), you'll have to
- change your code to "unescape" the slashes one level.
-
- For example, this used to work:
-
- # Code that matches a single backslash
- MyModel.objects.filter(text__contains='\\\\')
-
- But it should be rewritten as this:
-
- # Code that matches a single backslash
- MyModel.objects.filter(text__contains='\\')
-
- Removed ENABLE_PSYCO setting
- ============================
-
- As of [3877], the ENABLE_PSYCO setting no longer exists. If your settings
- file includes ENABLE_PSYCO, nothing will break per se, but it just won't do
- anything. If you want to use Psyco with Django, write some custom
- middleware that activates Psyco.
-
- Changed Admin.manager option to more flexible hook
- ==================================================
-
- As of [4342], the manager option to class Admin no longer exists. This
- option was undocumented, but we're mentioning the change here in case you
- used it. In favor of this option, class Admin may now define one of these
- methods:
-
- * queryset()
- * queryset_add()
- * queryset_change()
-
- These give you much more flexibility.
-
- Note that this change was made to the NewformsAdminBranch. (We initially
- called the new method change_list_queryset, but this was changed in [4584]
- to be more flexible.) The change will not be made to trunk until that
- branch is merged to trunk.
-
- Changed prepopulate_from to be defined in the Admin class,
- not database field classes ¶
- ==========================================================
-
- As of [4446], the prepopulate_from option to database fields no
- longer exists. It's been discontinued in favor of the new
- prepopulated_fields option on class Admin. The new
- prepopulated_fields option, if given, should be a dictionary
- mapping field names to lists/tuples of field names. Here's an
- example comparing old syntax and new syntax:
-
- # OLD:
- class MyModel(models.Model):
- first_name = models.CharField(maxlength=30)
- last_name = models.CharField(maxlength=30)
- slug = models.CharField(maxlength=60, prepopulate_from=('first_name', 'last_name'))
-
- class Admin:
- pass
-
- # NEW:
- class MyModel(models.Model):
- first_name = models.CharField(maxlength=30)
- last_name = models.CharField(maxlength=30)
- slug = models.CharField(maxlength=60)
-
- class Admin:
- prepopulated_fields = {'slug': ('first_name', 'last_name')}
-
- Moved admin doc views into django.contrib.admindocs
- ====================================================
-
- As of [4585], the documentation views for the Django admin site were moved
- into a new package, django.contrib.admindocs.
-
- The admin docs, which aren't documented very well, were located at docs/ in
- the admin site. They're also linked-to by the "Documentation" link in the
- upper right of default admin templates.
-
- Because we've moved the doc views, you now have to activate admin docs
- explicitly. Do this by adding the following line to your URLconf:
-
- (r'^admin/doc/', include('django.contrib.admindocs.urls')),
-
- Note that this change was made to the NewformsAdminBranch. The change will
- not be made to trunk until that branch is merged to trunk.
-
- Enforcing MySQLdb version
- =========================
-
- As of [4724], Django will raise an error if you try to use the MySQL
- backend with a MySQLdb ( MySQL python module) version earlier than 1.2.1p2.
- There were significant, production-related bugs in earlier versions, so we
- have upgraded the minimum requirement.
-
- In [4767], a mysql_old backend was added, that is identical to the original
- mysql backend prior to the change in [4724]. This backend can be used if
- upgrading the MySQLdb module is not immediately possible, however, it is
- deprecated and no further development will be done on it.
-
-New Features
-------------
-
- New forms library
- =================
-
- The new forms library has been merged from the new forms branch in to
- django.newforms in 0.96, the next revision will replace django.forms with
- django.newforms, the current forms library is already copied to
- django.oldforms to make the transition easier - it's advised to either
- upgrade your forms code to the newforms library or to change your imports
- as follows:
-
- from django import forms
- becomes
- from django import oldforms as forms
-
- URLconf improvements
- ====================
-
- It's now possible to use imported views in the urlconf rather than a string
- representing the view to call.
-
- Test framework
- ==============
-
- Now possible to write tests based on doctest and unittest
-
- Admin area changes
- ==================
-
- Changes to the user adding and updating views so that you don't need to
- worry about hashed passwords.
Deleted: packages/python-django/trunk/debian/docs
===================================================================
--- packages/python-django/trunk/debian/docs 2008-08-28 17:24:05 UTC (rev 6382)
+++ packages/python-django/trunk/debian/docs 2008-08-28 17:28:14 UTC (rev 6383)
@@ -1,3 +0,0 @@
-README
-AUTHORS
-docs/*.txt
Deleted: packages/python-django/trunk/debian/install
===================================================================
--- packages/python-django/trunk/debian/install 2008-08-28 17:24:05 UTC (rev 6382)
+++ packages/python-django/trunk/debian/install 2008-08-28 17:28:14 UTC (rev 6383)
@@ -1 +0,0 @@
-extras/django_bash_completion etc/bash_completion.d/
Deleted: packages/python-django/trunk/debian/manpages
===================================================================
--- packages/python-django/trunk/debian/manpages 2008-08-28 17:24:05 UTC (rev 6382)
+++ packages/python-django/trunk/debian/manpages 2008-08-28 17:28:14 UTC (rev 6383)
@@ -1 +0,0 @@
-docs/man/django-admin.1
Added: packages/python-django/trunk/debian/python-django-doc.doc-base
===================================================================
--- packages/python-django/trunk/debian/python-django-doc.doc-base (rev 0)
+++ packages/python-django/trunk/debian/python-django-doc.doc-base 2008-08-28 17:28:14 UTC (rev 6383)
@@ -0,0 +1,23 @@
+Document: python-django-doc
+Title: Python Django Documentation
+Author: Django Software Foundation
+Abstract: This documentation gives an introduction
+ to Django and its contributed packages like its automatic
+ admin and the user authentification applications.
+Section: Programming/Python
+
+Format: HTML
+Index: /usr/share/doc/python-django-doc/html/index.html
+Files: /usr/share/doc/python-django-doc/html/*.html
+ /user/share/doc/python-django-doc/html/faq/*.html
+ /usr/share/doc/python-django-doc/html/howto/*.html
+ /usr/share/doc/python-django-doc/html/internals/*.html
+ /usr/share/doc/python-django-doc/html/intro/*.html
+ /usr/share/doc/python-django-doc/html/misc/*.html
+ /usr/share/doc/python-django-doc/html/obsolete/*.html
+ /usr/share/doc/python-django-doc/html/ref/*.html
+ /usr/share/doc/python-django-doc/html/releases/*.html
+ /usr/share/doc/python-django-doc/html/topics/*.html
+
+Format: PDF
+Files: /usr/share/doc/python-django-doc/django.pdf
\ No newline at end of file
Added: packages/python-django/trunk/debian/python-django-doc.examples
===================================================================
--- packages/python-django/trunk/debian/python-django-doc.examples (rev 0)
+++ packages/python-django/trunk/debian/python-django-doc.examples 2008-08-28 17:28:14 UTC (rev 6383)
@@ -0,0 +1 @@
+examples/*
Added: packages/python-django/trunk/debian/python-django-doc.install
===================================================================
--- packages/python-django/trunk/debian/python-django-doc.install (rev 0)
+++ packages/python-django/trunk/debian/python-django-doc.install 2008-08-28 17:28:14 UTC (rev 6383)
@@ -0,0 +1,7 @@
+docs/_build/html/* usr/share/doc/python-django-doc/html/
+docs/_build/latex/django.pdf usr/share/doc/python-django-doc/
+#docs/_build/latex/django.ps usr/share/doc/python-django-doc/
+docs/_build/latex/*.tex usr/share/doc/python-django-doc/latex/
+docs/_build/latex/*.sty usr/share/doc/python-django-doc/latex/
+docs/_build/latex/*.cls usr/share/doc/python-django-doc/latex/
+docs/_build/latex/*.ist usr/share/doc/python-django-doc/latex/
Added: packages/python-django/trunk/debian/python-django.README.Debian
===================================================================
--- packages/python-django/trunk/debian/python-django.README.Debian (rev 0)
+++ packages/python-django/trunk/debian/python-django.README.Debian 2008-08-28 17:28:14 UTC (rev 6383)
@@ -0,0 +1,164 @@
+0.95 -> 0.96
+============
+
+Information here has been gathered from:
+ http://www.djangoproject.com/documentation/release_notes_0.96/
+and
+ http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges
+
+Backwards Incompatible Changes
+------------------------------
+
+ Database constraint names changed
+ =================================
+
+ As of [3512], the format of the constraint names Django generates for
+ foreign key references changed slightly. These names are only used
+ sometimes, when it is not possible to put the reference directly on the
+ affected column, so this is not always visible.
+
+ The effect of this change is that manage.py reset app_name and similar
+ commands may generate SQL with invalid constraint names and thus generate
+ an error when run against the database (the database server will complain
+ about the constraint not existing). To fix this, you will need to tweak the
+ output of manage.py sqlreset app_name to match the correct constraint names
+ and pass the results to the database server manually.
+
+ Backslash escaping changed
+ ==========================
+
+ As of [3552], the Django database API now escapes backslashes given as
+ query parameters. If you have any database API code that match backslashes,
+ and it was working before (despite the broken escaping), you'll have to
+ change your code to "unescape" the slashes one level.
+
+ For example, this used to work:
+
+ # Code that matches a single backslash
+ MyModel.objects.filter(text__contains='\\\\')
+
+ But it should be rewritten as this:
+
+ # Code that matches a single backslash
+ MyModel.objects.filter(text__contains='\\')
+
+ Removed ENABLE_PSYCO setting
+ ============================
+
+ As of [3877], the ENABLE_PSYCO setting no longer exists. If your settings
+ file includes ENABLE_PSYCO, nothing will break per se, but it just won't do
+ anything. If you want to use Psyco with Django, write some custom
+ middleware that activates Psyco.
+
+ Changed Admin.manager option to more flexible hook
+ ==================================================
+
+ As of [4342], the manager option to class Admin no longer exists. This
+ option was undocumented, but we're mentioning the change here in case you
+ used it. In favor of this option, class Admin may now define one of these
+ methods:
+
+ * queryset()
+ * queryset_add()
+ * queryset_change()
+
+ These give you much more flexibility.
+
+ Note that this change was made to the NewformsAdminBranch. (We initially
+ called the new method change_list_queryset, but this was changed in [4584]
+ to be more flexible.) The change will not be made to trunk until that
+ branch is merged to trunk.
+
+ Changed prepopulate_from to be defined in the Admin class,
+ not database field classes ¶
+ ==========================================================
+
+ As of [4446], the prepopulate_from option to database fields no
+ longer exists. It's been discontinued in favor of the new
+ prepopulated_fields option on class Admin. The new
+ prepopulated_fields option, if given, should be a dictionary
+ mapping field names to lists/tuples of field names. Here's an
+ example comparing old syntax and new syntax:
+
+ # OLD:
+ class MyModel(models.Model):
+ first_name = models.CharField(maxlength=30)
+ last_name = models.CharField(maxlength=30)
+ slug = models.CharField(maxlength=60, prepopulate_from=('first_name', 'last_name'))
+
+ class Admin:
+ pass
+
+ # NEW:
+ class MyModel(models.Model):
+ first_name = models.CharField(maxlength=30)
+ last_name = models.CharField(maxlength=30)
+ slug = models.CharField(maxlength=60)
+
+ class Admin:
+ prepopulated_fields = {'slug': ('first_name', 'last_name')}
+
+ Moved admin doc views into django.contrib.admindocs
+ ====================================================
+
+ As of [4585], the documentation views for the Django admin site were moved
+ into a new package, django.contrib.admindocs.
+
+ The admin docs, which aren't documented very well, were located at docs/ in
+ the admin site. They're also linked-to by the "Documentation" link in the
+ upper right of default admin templates.
+
+ Because we've moved the doc views, you now have to activate admin docs
+ explicitly. Do this by adding the following line to your URLconf:
+
+ (r'^admin/doc/', include('django.contrib.admindocs.urls')),
+
+ Note that this change was made to the NewformsAdminBranch. The change will
+ not be made to trunk until that branch is merged to trunk.
+
+ Enforcing MySQLdb version
+ =========================
+
+ As of [4724], Django will raise an error if you try to use the MySQL
+ backend with a MySQLdb ( MySQL python module) version earlier than 1.2.1p2.
+ There were significant, production-related bugs in earlier versions, so we
+ have upgraded the minimum requirement.
+
+ In [4767], a mysql_old backend was added, that is identical to the original
+ mysql backend prior to the change in [4724]. This backend can be used if
+ upgrading the MySQLdb module is not immediately possible, however, it is
+ deprecated and no further development will be done on it.
+
+New Features
+------------
+
+ New forms library
+ =================
+
+ The new forms library has been merged from the new forms branch in to
+ django.newforms in 0.96, the next revision will replace django.forms with
+ django.newforms, the current forms library is already copied to
+ django.oldforms to make the transition easier - it's advised to either
+ upgrade your forms code to the newforms library or to change your imports
+ as follows:
+
+ from django import forms
+ becomes
+ from django import oldforms as forms
+
+ URLconf improvements
+ ====================
+
+ It's now possible to use imported views in the urlconf rather than a string
+ representing the view to call.
+
+ Test framework
+ ==============
+
+ Now possible to write tests based on doctest and unittest
+
+ Admin area changes
+ ==================
+
+ Changes to the user adding and updating views so that you don't need to
+ worry about hashed passwords.
Added: packages/python-django/trunk/debian/python-django.docs
===================================================================
--- packages/python-django/trunk/debian/python-django.docs (rev 0)
+++ packages/python-django/trunk/debian/python-django.docs 2008-08-28 17:28:14 UTC (rev 6383)
@@ -0,0 +1,3 @@
+README
+AUTHORS
+docs/*.txt
Added: packages/python-django/trunk/debian/python-django.install
===================================================================
--- packages/python-django/trunk/debian/python-django.install (rev 0)
+++ packages/python-django/trunk/debian/python-django.install 2008-08-28 17:28:14 UTC (rev 6383)
@@ -0,0 +1,3 @@
+debian/tmp/usr/bin/django-admin.py
+debian/tmp/usr/lib/python*/site-packages
+extras/django_bash_completion etc/bash_completion.d/
Added: packages/python-django/trunk/debian/python-django.manpages
===================================================================
--- packages/python-django/trunk/debian/python-django.manpages (rev 0)
+++ packages/python-django/trunk/debian/python-django.manpages 2008-08-28 17:28:14 UTC (rev 6383)
@@ -0,0 +1 @@
+docs/man/django-admin.1
More information about the Python-modules-commits
mailing list