Re: [Django] #4926: Ordering in admin listview ignores ordering in admin options

[Django]

#4926: Ordering in admin listview ignores ordering in admin options
+---
  Reporter:  Glin   | Owner:  nobody

Status:  reopened   | Milestone:

 Component:  django.contrib.admin   |   Version:  SVN   

Resolution: |  Keywords:  nfa-someday 
nfa-changelist
 Stage:  Someday/Maybe  | Has_patch:  1 

Needs_docs:  0  |   Needs_tests:  0 

Needs_better_patch:  0  |  
+---
Comment (by bendavis78):

 If anyone is interested, I've submitted a patch for a proposed UI for
 sorting by multiple fields.  This would also fix this particular issue.

 See here: #11868

 Any feedback is appreaciated.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11868: Multiple sort in admin changelist

[Django]

#11868: Multiple sort in admin changelist
---+
  Reporter:  bendavis78| Owner:  nobody 

Status:  new   | Milestone: 

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  admin sort 
multisort ordering order
 Stage:  Unreviewed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by bendavis78):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Also, this is related to the following tickets;  #389, #2234, #4926,
 #5673, #8682

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11868: Multiple sort in admin changelist

[Django]

#11868: Multiple sort in admin changelist
-+--
 Reporter:  bendavis78   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  django.contrib.admin | Version:  SVN   
 Keywords:  admin sort multisort ordering order  |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 I've made an attempt at adding multiple sort columns to the admin
 changelist.  I'm basically putting this up here as an initial proposal of
 what I think would be a good starting point for a UI for multiple column
 sorting.

 The idea is that each time you click on a header, it toggles between three
 states,  "ascending", "descending", and "cleared".  The order in which
 multiple columns are sorted are denoted by a small number next to the
 up/down icon. So (for example) to sort by {{{('last_name',
 'first_name')}}}, you click on the "last name" column, then the "first
 name" column.  To change that to {{{('-last_name', 'first_name')}}} you
 would click once more on the "last name" column.  Clicking "last name"
 again would set the ordering to just {{{('first_name')}}}.

 This patches cleanly against r10843.  Testers are always appreciated.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11716: Various methods in django.db.models.fields don't wrap ValueErrors and allow them to escape

[Django]

#11716: Various methods in django.db.models.fields don't wrap ValueErrors and 
allow
them to escape
---+
  Reporter:  Leo   | Owner:  Leo
Status:  assigned  | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  1.1
Resolution:|  Keywords: 
 Stage:  Unreviewed| Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by Leo):

  * owner:  nobody => Leo
  * status:  new => assigned
  * needs_tests:  1 => 0

Comment:

 Thanks to mattmcc for pointing me in the right direction, I've attached a
 patch with the tests.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11867: if spatialite is installed and pysqlite2.5 is installed without `enable_load_extension` tests won't run

[Django]

#11867: if spatialite is installed and pysqlite2.5 is installed without
`enable_load_extension` tests won't run
---+
 Reporter:  danring|   Owner:  nobody
   Status:  new|   Milestone:
Component:  GIS| Version:  1.1   
 Keywords:  enable_load_extension  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Using spatialite with contrib.gis is supported only with pysqlite2.5.0 or
 higher, and pysqlite must be compiled with `enable_load_extension` support
 (see http://geodjango.org/docs/install.html#pysqlite2 ).  If spatialite is
 present, `settings.DATABASE_ENGINE == 'sqlite3'`, and pysqlite is present
 but without `enable_load_extension` support, tests/runtests.py fails as
 follows:

 {{{
 Traceback (most recent call last):
   File "./runtests.py", line 191, in 
 django_tests(int(options.verbosity), options.interactive, args)
   File "./runtests.py", line 161, in django_tests
 failures = test_runner(test_labels, verbosity=verbosity,
 interactive=interactive, extra_tests=extra_tests)
   File "/home/dan/work/django/django/django/test/simple.py", line 191, in
 run_tests
 connection.creation.create_test_db(verbosity, autoclobber=not
 interactive)
   File "/home/dan/work/django/django/django/db/backends/creation.py", line
 332, in create_test_db
 can_rollback = self._rollback_works()
   File "/home/dan/work/django/django/django/db/backends/creation.py", line
 389, in _rollback_works
 cursor = self.connection.cursor()
   File "/home/dan/work/django/django/django/db/backends/__init__.py", line
 81, in cursor
 cursor = self._cursor()
   File "/home/dan/work/django/django/django/db/backends/sqlite3/base.py",
 line 175, in _cursor
 connection_created.send(sender=self.__class__)
   File "/home/dan/work/django/django/django/dispatch/dispatcher.py", line
 166, in send
 response = receiver(signal=self, sender=sender, **named)
   File
 
"/home/dan/work/django/django/django/contrib/gis/db/backend/spatialite/__init__.py",
 line 26, in initialize_spatialite
 connection.connection.enable_load_extension(True)
 AttributeError: 'sqlite3.Connection' object has no attribute
 'enable_load_extension'
 }}}

 Note that this is not a test failure, but rather a failure of any tests to
 run at all.

 Also, Debian package python-pysqlite2 (currently) defaults to disabling
 `enable_load_extension`.  (See: http://bugs.debian.org/cgi-
 bin/bugreport.cgi?bug=543252 )

 I think either

 1. `settings.DATABASE_ENGINE='spatialite'` instead of `'sqlite3'` should
 be used (my preference) (or maybe `sqlite3_spatialite` or something); or

 2. `contrib.gis.tests.utils.spatialite` should only be set if
 `enable_load_extension` is available (`contrib.gis` tests should be
 skipped somehow).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11283: latest() doesn't clear previous ordering

[Django]

#11283: latest() doesn't clear previous ordering
---+
  Reporter:  benmoran  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by punteney):

  * needs_tests:  1 => 0

Comment:

 Added test to the existing patch

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11863: Add a method to the orm to create Model instances from raw sql queries

[Django]

#11863: Add a method to the orm to create Model instances from raw sql queries
---+
  Reporter:  seanoc| Owner:  seanoc
Status:  assigned  | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by seanoc):

 Had a discussion with RKM and worked out a bit of a variation which should
 work.  Unfortunately the final implementation will depend on some
 decisions being made around multi-db support so it will be a little while
 before a full patch will be ready.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11301: Fields using SplitHiddenDateTimeWidget are still rendered with their label

[Django]

#11301: Fields using SplitHiddenDateTimeWidget are still rendered with their 
label
---+
  Reporter:  dgouldin  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by punteney):

  * needs_tests:  1 => 0

Comment:

 updated patch with a test case

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11303: changed_data wrong work with BooleanField

[Django]

#11303: changed_data wrong work with BooleanField
---+
  Reporter:  oduvan| Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  1.1-beta-1
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by punteney):

  * needs_better_patch:  1 => 0
  * needs_tests:  1 => 0

Comment:

 Updated the patch to do the fix at the CheckBoxInput widget _has_changed
 function level as it was a problem with the string 'False" being evaluated
 as a boolean and returning as True. Also added a test to check for this
 issue

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11866: non-null FK to a CharField primary key fails when key value is the empty string, giving "[model.fk_col] may not be NULL"

[Django]

#11866: non-null FK to a CharField primary key fails when key value is the empty
string, giving "[model.fk_col] may not be NULL"
---+
  Reporter:  andrewbadr| Owner:  andrewbadr
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by andrewbadr):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Seems to be caused by `ForeignKey.get_db_prep_save` (called from
 `Model.save_base`):
 {{{
 def get_db_prep_save(self, value):
 if value == '' or value == None:
 return None
 ...
 }}}

 Unsure where to go since I don't know the reasoning behind this code. Is
 this due to forms assigning the empty-string to fields left blank?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11863: Add a method to the orm to create Model instances from raw sql queries

[Django]

#11863: Add a method to the orm to create Model instances from raw sql queries
---+
  Reporter:  seanoc| Owner:  seanoc
Status:  assigned  | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by seanoc):

 So after some testing and research here's an example of the API I'd
 propose:

 {{{
 import ResultHandler
 from library import Author, Book

 # Basic use
 query = "select id, first_name, last_name from library_author"
 authors = ResultHandler(Author, query)

 # Extended use
 query = """select id, first_name as first, last_name as last, count(select
 * from library_book...) as book_count
from library_author where first ilike %s and last ilike %s"""
 params = ('John', 'Doe')
 translations = (
 ('first', 'first_name'),
 ('last', 'last_name'),
 )
 authors = ResultHandler(Author, query, params, translations)
 }}}

 In the basic use, authors would be a iterable which would return normal
 model instances.  The extended use example authors would be an iterable of
 model instances with an extra property called book_count.  Obviously this
 example is a bit contrived since this could be accomplished via the ORM
 but it illustrates the API I'm proposing.

 I've confirmed that it is possible to figure out the result field to model
 field translation independent of field ordering.

 Let me know what you think of the API and it's appropriateness for Django
 proper.  I'd be happy to package it in the form of a Django patch or a
 third party app once my implementation is complete.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #3100: Support for arguments on intermediate tag tokens (ex. {% if arg %}{% elif arg %}{% endif %})

[Django]

#3100: Support for arguments on intermediate tag tokens (ex. {% if arg %}{% elif
arg %}{% endif %})
---+
  Reporter:  Eric Van Dewoestine   | Owner: 
 adrian
Status:  reopened  | Milestone: 
   
 Component:  Template system   |   Version: 
 SVN   
Resolution:|  Keywords: 
   
 Stage:  Accepted  | Has_patch: 
 1 
Needs_docs:  0 |   Needs_tests: 
 1 
Needs_better_patch:  1 |  
---+
Changes (by danring):

 * cc: danring (added)

Comment:

 The patch just added breaks the regressiontests.templates
 'namedendblocks0?' by failing to raise TemplateSyntaxError when {%
 endblock %} tags are out of order.  (Since endblock tags are the only
 (core) tags where the endtag has an argument.)

 So two possibilities are:
 1. remove those tests - seems okay to me, since the named-endblock tags
 are for readability anyway, rather than providing functionality; also,
 named endblocks are only used (at least in trunk) in contrib.gis
 javascripts.
 2. make additional changes in template.loader_tags.do_block to force
 strict checking of endblock tags there

 Which would be the desired route?  Or something altogether different?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11526 - in django/trunk: . django/core/management extras

[noreply]

Author: jkocherhans
Date: 2009-09-11 18:15:59 -0500 (Fri, 11 Sep 2009)
New Revision: 11526

Modified:
   django/trunk/AUTHORS
   django/trunk/django/core/management/__init__.py
   django/trunk/extras/django_bash_completion
Log:
Fixed #10752. Added more advanced bash completion. Thanks, Arthur Koziel.

Modified: django/trunk/AUTHORS
===
--- django/trunk/AUTHORS2009-09-11 22:12:30 UTC (rev 11525)
+++ django/trunk/AUTHORS2009-09-11 23:15:59 UTC (rev 11526)
@@ -241,6 +241,7 @@
 Igor Kolar 
 Gasper Koren
 Martin Kosír 
+Arthur Koziel 
 Meir Kriheli 
 Bruce Kroeze 
 krzysiek.paw...@silvermedia.pl

Modified: django/trunk/django/core/management/__init__.py
===
--- django/trunk/django/core/management/__init__.py 2009-09-11 22:12:30 UTC 
(rev 11525)
+++ django/trunk/django/core/management/__init__.py 2009-09-11 23:15:59 UTC 
(rev 11526)
@@ -261,6 +261,82 @@
 sys.exit(1)
 return klass
 
+def autocomplete(self):
+"""
+Output completion suggestions for BASH.
+
+The output of this function is passed to BASH's `COMREPLY` variable and
+treated as completion suggestions. `COMREPLY` expects a space
+separated string as the result.
+
+The `COMP_WORDS` and `COMP_CWORD` BASH environment variables are used
+to get information about the cli input. Please refer to the BASH
+man-page for more information about this variables.
+
+Subcommand options are saved as pairs. A pair consists of
+the long option string (e.g. '--exclude') and a boolean
+value indicating if the option requires arguments. When printing to
+stdout, a equal sign is appended to options which require arguments.
+
+Note: If debugging this function, it is recommended to write the debug
+output in a separate file. Otherwise the debug output will be treated
+and formatted as potential completion suggestions.
+"""
+# Don't complete if user hasn't sourced bash_completion file.
+if not os.environ.has_key('DJANGO_AUTO_COMPLETE'):
+return
+
+cwords = os.environ['COMP_WORDS'].split()[1:]
+cword = int(os.environ['COMP_CWORD'])
+
+try:
+curr = cwords[cword-1]
+except IndexError:
+curr = ''
+
+subcommands = get_commands().keys() + ['help']
+options = [('--help', None)]
+
+# subcommand
+if cword == 1:
+print ' '.join(filter(lambda x: x.startswith(curr), subcommands))
+# subcommand options
+# special case: the 'help' subcommand has no options
+elif cwords[0] in subcommands and cwords[0] != 'help':
+subcommand_cls = self.fetch_command(cwords[0])
+# special case: 'runfcgi' stores additional options as
+# 'key=value' pairs
+if cwords[0] == 'runfcgi':
+from django.core.servers.fastcgi import FASTCGI_OPTIONS
+options += [(k, 1) for k in FASTCGI_OPTIONS]
+# special case: add the names of installed apps to options
+elif cwords[0] in ('dumpdata', 'reset', 'sql', 'sqlall',
+   'sqlclear', 'sqlcustom', 'sqlindexes',
+   'sqlreset', 'sqlsequencereset', 'test'):
+try:
+from django.conf import settings
+# Get the last part of the dotted path as the app name.
+options += [(a.split('.')[-1], 0) for a in 
settings.INSTALLED_APPS]
+except ImportError:
+# Fail silently if DJANGO_SETTINGS_MODULE isn't set. The
+# user will find out once they execute the command.
+pass
+options += [(s_opt.get_opt_string(), s_opt.nargs) for s_opt in
+subcommand_cls.option_list]
+# filter out previously specified options from available options
+prev_opts = [x.split('=')[0] for x in cwords[1:cword-1]]
+options = filter(lambda (x, v): x not in prev_opts, options)
+
+# filter options by current input
+options = [(k, v) for k, v in options if k.startswith(curr)]
+for option in options:
+opt_label = option[0]
+# append '=' to options which require args
+if option[1]:
+opt_label += '='
+print opt_label
+sys.exit(1)
+
 def execute(self):
 """
 Given the command-line arguments, this figures out which subcommand is
@@ -272,6 +348,7 @@
 parser = LaxOptionParser(usage="%prog subcommand [options] [args]",
  version=get_vers

[Django] #11866: non-null FK to a CharField primary key fails when key value is the empty string, giving "[model.fk_col] may not be NULL"

[Django]

#11866: non-null FK to a CharField primary key fails when key value is the empty
string, giving "[model.fk_col] may not be NULL"
--+-
 Reporter:  andrewbadr|   Owner:  andrewbadr
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Model A has a CharField primary_key. Model B has a ForeignKey field to
 model A. If an instance of A has a row with an empty-string in the primary
 key column, no B instance can point to it. Attempting to create such a B
 instance fails with "[model.fk_col] may not be NULL". Repro'd with PG and
 sqlite3.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #6298: Don't require a settings file to run django unit tests i.e. make running unit tests easier

[Django]

#6298: Don't require a settings file to run django unit tests i.e. make running
unit tests easier
-+--
  Reporter:  cur...@oddpost.com  | Owner:  nobody
Status:  reopened| Milestone:  1.2   
 Component:  Testing framework   |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * status:  closed => reopened
  * resolution:  wontfix =>

Comment:

 Eric, Joseph and I have arrived at a compromise suggestion - checking in a
 test_sqlite.py settings file that is sufficient for testing sqlite, but
 still requires that you specify --settings=test_sqlite at the command
 line. Will commit soon.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9310: 404 debug pages should show the name of the tried urlpattern if one exists.

[Django]

#9310: 404 debug pages should show the name of the tried urlpattern if one 
exists.
-+--
  Reporter:  floguy  | Owner:  tobias
Status:  assigned| Milestone:  1.2   
 Component:  Core framework  |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by tobias):

 The code needs to make a list instead of a string so the template can
 iterate through the different resolvers and patterns (and hence have
 access to the final pattern's name).  The template has been updated to
 work with the new format and I couldn't find anything else that depends on
 Resolver404's 'tried' arg.

 I updated Eric's patch to apply to the latest trunk, converted the
 generator expression into a list comprehension, and created a test for the
 new feature.

 Let me know what you think.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11840: Form validation should check for IOErrors

[Django]

#11840: Form validation should check for IOErrors
-+--
  Reporter:  stavros | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  worksforme  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Comment (by stavros):

 That's odd, I checked my home install and it has it, but both production
 and staging don't, and django.VERSION reports 1.1.0 there. This is
 positively strange, but I upgraded and everything is fine now, thank you.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11840: Form validation should check for IOErrors

[Django]

#11840: Form validation should check for IOErrors
-+--
  Reporter:  stavros | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  worksforme  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Comment (by Honza_Kral):

 No, the try: except: block is present in the 1.1 tarball, just checked
 just to be sure.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11847: FormWizard in urlconf is not reversable

[Django]

#11847: FormWizard in urlconf is not reversable
---+
  Reporter:  r...@whidbey.com   | Owner:  nobody

Status:  closed| Milestone: 
   
 Component:  django.contrib.formtools  |   Version:  1.1
   
Resolution:  invalid   |  Keywords:  formwizard url 
reverse
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by r...@whidbey.com):

 Great, thanks for the tip, much better workaround.  Does FormWizard need a
 default behavior, like a standard view?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11840: Form validation should check for IOErrors

[Django]

#11840: Form validation should check for IOErrors
-+--
  Reporter:  stavros | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  worksforme  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Comment (by stavros):

 Sadly, I've searched high and low for such a file, but none of my users
 has responded. Looking at your code it is indeed miraculous that this
 happens, but looking at mine elucidates the situation:


 {{{
 def clean(self, data, initial=None):
 ...
 # load() is the only method that can spot a truncated JPEG,
 #  but it cannot be called sanely after verify()
 trial_image = Image.open(file)
 trial_image.load()
 }}}

 There's no exception block to be found there. I assume it was added after
 1.1?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11840: Form validation should check for IOErrors

[Django]

#11840: Form validation should check for IOErrors
-+--
  Reporter:  stavros | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  worksforme  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by Honza_Kral):

  * status:  new => closed
  * needs_better_patch:  => 0
  * component:  Uncategorized => Forms
  * needs_tests:  => 1
  * needs_docs:  => 0
  * resolution:  => worksforme

Comment:

 can you provide a test for that? or just a file that results in this
 error? Looking through the code that shouldn't happen:

 {{{
 except Exception: # Python Imaging Library doesn't recognize it as
 an image
 raise ValidationError(self.error_messages['invalid_image'])
 }}}

 I am closing it as works for me, feel free to reopen it if you find a file
 that results in this error. Thanks!

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #5176: Bug in django.utils.cache._generate_cache_key(request, headerlist, key_prefix)

[Django]

#5176: Bug in django.utils.cache._generate_cache_key(request, headerlist,
key_prefix)
---+
  Reporter:  Eratothene| Owner:  nobody  
Status:  reopened  | Milestone:  
 Component:  Cache system  |   Version:  SVN 
Resolution:|  Keywords:  cache session testclient
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  1 |  
---+
Changes (by ryszard):

 * cc: ryszard.szopa+dja...@gmail.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11826: django.forms.fields.URLField rejects valid URLs with no abs_path component

[Django]

#11826: django.forms.fields.URLField rejects valid URLs with no abs_path 
component
+---
  Reporter:  wam| Owner:  Honza_Kral
Status:  new| Milestone:
 Component:  Forms  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Fixed on a branch  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Honza_Kral):

  * owner:  nobody => Honza_Kral
  * needs_better_patch:  => 0
  * stage:  Unreviewed => Fixed on a branch
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Fixed on model-validation branch in [11525]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11525 - in django/branches/soc2009/model-validation: django/core django/forms tests/modeltests/validators tests/regressiontests/forms

[noreply]

Author: Honza_Kral
Date: 2009-09-11 17:12:30 -0500 (Fri, 11 Sep 2009)
New Revision: 11525

Modified:
   django/branches/soc2009/model-validation/django/core/validators.py
   django/branches/soc2009/model-validation/django/forms/fields.py
   django/branches/soc2009/model-validation/tests/modeltests/validators/tests.py
   
django/branches/soc2009/model-validation/tests/regressiontests/forms/fields.py
Log:
[soc2009/model-validation] Fixed #11826 django.forms.fields.URLField rejects 
valid URLs with no abs_path component

Thanks wam

Modified: django/branches/soc2009/model-validation/django/core/validators.py
===
--- django/branches/soc2009/model-validation/django/core/validators.py  
2009-09-11 22:00:24 UTC (rev 11524)
+++ django/branches/soc2009/model-validation/django/core/validators.py  
2009-09-11 22:12:30 UTC (rev 11525)
@@ -44,7 +44,7 @@
 r'localhost|' #localhost...
 r'\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})' # ...or ip
 r'(?::\d+)?' # optional port
-r'(?:/?|/\S+)$', re.IGNORECASE)
+r'(?:/?|[/?]\S+)$', re.IGNORECASE)
 
 def __init__(self, verify_exists=False, 
validator_user_agent=URL_VALIDATOR_USER_AGENT):
 super(URLValidator, self).__init__()

Modified: django/branches/soc2009/model-validation/django/forms/fields.py
===
--- django/branches/soc2009/model-validation/django/forms/fields.py 
2009-09-11 22:00:24 UTC (rev 11524)
+++ django/branches/soc2009/model-validation/django/forms/fields.py 
2009-09-11 22:12:30 UTC (rev 11525)
@@ -551,12 +551,15 @@
 
self.validators.append(validators.URLValidator(verify_exists=verify_exists, 
validator_user_agent=validator_user_agent))
 
 def to_python(self, value):
-# If no URL scheme given, assume http://
-if value and '://' not in value:
-value = u'http://%s' % value
-# If no URL path given, assume /
-if value and not urlparse.urlsplit(value)[2]:
-value += '/'
+if value: 
+if '://' not in value: 
+# If no URL scheme given, assume http:// 
+value = u'http://%s' % value 
+url_fields = list(urlparse.urlsplit(value)) 
+if not url_fields[2]: 
+# the path portion may need to be added before query params 
+url_fields[2] = '/' 
+value = urlparse.urlunsplit(url_fields) 
 return super(URLField, self).to_python(value)
 
 class BooleanField(Field):

Modified: 
django/branches/soc2009/model-validation/tests/modeltests/validators/tests.py
===
--- 
django/branches/soc2009/model-validation/tests/modeltests/validators/tests.py   
2009-09-11 22:00:24 UTC (rev 11524)
+++ 
django/branches/soc2009/model-validation/tests/modeltests/validators/tests.py   
2009-09-11 22:12:30 UTC (rev 11525)
@@ -106,6 +106,8 @@
 (URLValidator(), 'http://200.8.9.10/', None),
 (URLValidator(), 'http://200.8.9.10:8000/test', None),
 (URLValidator(), 'http://valid-hyphens.com/', None),
+(URLValidator(), 'http://example.com?something=value', None),
+(URLValidator(), 
'http://example.com/index.php?something=value&another=value2', None),
 
 (URLValidator(), 'foo', ValidationError),
 (URLValidator(), 'http://', ValidationError),

Modified: 
django/branches/soc2009/model-validation/tests/regressiontests/forms/fields.py
===
--- 
django/branches/soc2009/model-validation/tests/regressiontests/forms/fields.py  
2009-09-11 22:00:24 UTC (rev 11524)
+++ 
django/branches/soc2009/model-validation/tests/regressiontests/forms/fields.py  
2009-09-11 22:12:30 UTC (rev 11525)
@@ -496,6 +496,10 @@
 f = URLField()
 self.assertEqual(u'http://example.com/', f.clean('http://example.com'))
 self.assertEqual(u'http://example.com/test', 
f.clean('http://example.com/test'))
+
+def test_urlfield_ticket11826(self):
+f = URLField()
+self.assertEqual(u'http://example.com/?some_param=some_value', 
f.clean('http://example.com?some_param=some_value'))
 
 # BooleanField 

 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11794: Grammar and sentence fix

[Django]

#11794: Grammar and sentence fix
+---
  Reporter:  seemant| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Documentation
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11524 - django/branches/releases/1.1.X/docs/internals

[noreply]

Author: ubernostrum
Date: 2009-09-11 17:00:24 -0500 (Fri, 11 Sep 2009)
New Revision: 11524

Modified:
   django/branches/releases/1.1.X/docs/internals/svn.txt
Log:
[1.1.X] Document the fact that we now put dead branches in the attic. Backport 
of r11523 from trunk.

Modified: django/branches/releases/1.1.X/docs/internals/svn.txt
===
--- django/branches/releases/1.1.X/docs/internals/svn.txt   2009-09-11 
21:59:29 UTC (rev 11523)
+++ django/branches/releases/1.1.X/docs/internals/svn.txt   2009-09-11 
22:00:24 UTC (rev 11524)
@@ -114,14 +114,9 @@
 being actively worked on by any developer. At this point the branch is
 considered closed.
 
-Unfortunately, Subversion has no standard way of indicating
-this. Generally, you can recognize a dead branch by viewing it through
-the web interface, which lists the date of the most recent change to
-the branch. Branches which have gone more than a month or two with no
-activity can usually be assumed to be closed. In the future, the
-layout of branches in the repository may be rearranged to make it
-easier to tell which branches are still active (e.g., by moving closed
-or abandoned branches into the ``django/branches/attic`` directory).
+Unfortunately, Subversion has no standard way of indicating this. As a
+workaround, branches of Django which are closed and no longer
+maintained are moved into the directory ``django/branches/attic``.
 
 For reference, the following are branches whose code eventually became
 part of Django itself, and so are no longer separately maintained:
@@ -184,7 +179,10 @@
 
 * ``sqlalchemy``
 
+All of the above-mentioned branches now reside in
+``django/branches/attic``.
 
+
 Support and bugfix branches
 ---
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11523 - django/trunk/docs/internals

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:59:29 -0500 (Fri, 11 Sep 2009)
New Revision: 11523

Modified:
   django/trunk/docs/internals/svn.txt
Log:
Document the fact that we now put dead branches in the attic.

Modified: django/trunk/docs/internals/svn.txt
===
--- django/trunk/docs/internals/svn.txt 2009-09-11 21:28:53 UTC (rev 11522)
+++ django/trunk/docs/internals/svn.txt 2009-09-11 21:59:29 UTC (rev 11523)
@@ -114,14 +114,9 @@
 being actively worked on by any developer. At this point the branch is
 considered closed.
 
-Unfortunately, Subversion has no standard way of indicating
-this. Generally, you can recognize a dead branch by viewing it through
-the web interface, which lists the date of the most recent change to
-the branch. Branches which have gone more than a month or two with no
-activity can usually be assumed to be closed. In the future, the
-layout of branches in the repository may be rearranged to make it
-easier to tell which branches are still active (e.g., by moving closed
-or abandoned branches into the ``django/branches/attic`` directory).
+Unfortunately, Subversion has no standard way of indicating this. As a
+workaround, branches of Django which are closed and no longer
+maintained are moved into the directory ``django/branches/attic``.
 
 For reference, the following are branches whose code eventually became
 part of Django itself, and so are no longer separately maintained:
@@ -184,7 +179,10 @@
 
 * ``sqlalchemy``
 
+All of the above-mentioned branches now reside in
+``django/branches/attic``.
 
+
 Support and bugfix branches
 ---
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11863: Add a method to the orm to create Model instances from raw sql queries

[Django]

#11863: Add a method to the orm to create Model instances from raw sql queries
---+
  Reporter:  seanoc| Owner:  seanoc
Status:  assigned  | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by lukeplant):

 If it's possible to write this generically at all, then you don't actually
 have to write any boilerplate - you can already write a utility function
 that will do it for any model (and it doesn't have to be method on Model).
 It also sounds like you've got specific requirements in mind with your
 extra features.  Why don't you come up with a function that does what you
 want, and then we can see if it's likely to get into Django?  It may be
 that *some* of the things you want would definitely *not* make it, in
 which case there is no point adding a feature that is not even sufficient
 for the one person who's asked for it.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11847: FormWizard in urlconf is not reversable

[Django]

#11847: FormWizard in urlconf is not reversable
---+
  Reporter:  r...@whidbey.com   | Owner:  nobody

Status:  closed| Milestone: 
   
 Component:  django.contrib.formtools  |   Version:  1.1
   
Resolution:  invalid   |  Keywords:  formwizard url 
reverse
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by Honza_Kral):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 The recommended way to do that would be to use the named url mappings. See
 http://docs.djangoproject.com/en/dev/topics/http/urls/#id2 for details

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11522 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:28:53 -0500 (Fri, 11 Sep 2009)
New Revision: 11522

Added:
   django/branches/attic/unicode/
Removed:
   django/branches/unicode/
Log:
Move the unicode branch into the attic.

Copied: django/branches/attic/unicode (from rev 11521, django/branches/unicode)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11521 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:28:11 -0500 (Fri, 11 Sep 2009)
New Revision: 11521

Added:
   django/branches/attic/sqlalchemy/
Removed:
   django/branches/sqlalchemy/
Log:
Move the sqlalchemy branch into the attic.

Copied: django/branches/attic/sqlalchemy (from rev 11520, 
django/branches/sqlalchemy)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11863: Add a method to the orm to create Model instances from raw sql queries

[Django]

#11863: Add a method to the orm to create Model instances from raw sql queries
---+
  Reporter:  seanoc| Owner:  seanoc
Status:  assigned  | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by seanoc):

 That's assuming that the order of the fields coming back from your query
 match the order of your model's fields.  There's value in providing
 something which can be a bit more robust and flexible (i.e. adding "extra"
 fields as properties.  Additionally providing a supported and documented
 method of handling this process for newer users holds significant value.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11520 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:27:33 -0500 (Fri, 11 Sep 2009)
New Revision: 11520

Added:
   django/branches/attic/search-api/
Removed:
   django/branches/search-api/
Log:
Move the search-api branch into the attic.

Copied: django/branches/attic/search-api (from rev 11519, 
django/branches/search-api)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11519 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:26:49 -0500 (Fri, 11 Sep 2009)
New Revision: 11519

Added:
   django/branches/attic/schema-evolution-ng/
Removed:
   django/branches/schema-evolution-ng/
Log:
Move the schema-evolution-ng branch into the attic.

Copied: django/branches/attic/schema-evolution-ng (from rev 11518, 
django/branches/schema-evolution-ng)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11518 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:26:12 -0500 (Fri, 11 Sep 2009)
New Revision: 11518

Added:
   django/branches/attic/schema-evolution/
Removed:
   django/branches/schema-evolution/
Log:
Move the schema-evolution branch into the attic.

Copied: django/branches/attic/schema-evolution (from rev 11517, 
django/branches/schema-evolution)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11517 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:25:32 -0500 (Fri, 11 Sep 2009)
New Revision: 11517

Added:
   django/branches/attic/queryset-refactor/
Removed:
   django/branches/queryset-refactor/
Log:
Move the queryset-refactor branch into the attic.

Copied: django/branches/attic/queryset-refactor (from rev 11516, 
django/branches/queryset-refactor)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11516 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:25:01 -0500 (Fri, 11 Sep 2009)
New Revision: 11516

Added:
   django/branches/attic/per-object-permissions/
Removed:
   django/branches/per-object-permissions/
Log:
Move the per-object-permissions branch into the attic.

Copied: django/branches/attic/per-object-permissions (from rev 11515, 
django/branches/per-object-permissions)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11515 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:24:24 -0500 (Fri, 11 Sep 2009)
New Revision: 11515

Added:
   django/branches/attic/newforms-admin/
Removed:
   django/branches/newforms-admin/
Log:
Move the newforms-admin branch into the attic.

Copied: django/branches/attic/newforms-admin (from rev 11514, 
django/branches/newforms-admin)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11514 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:23:58 -0500 (Fri, 11 Sep 2009)
New Revision: 11514

Added:
   django/branches/attic/new-admin/
Removed:
   django/branches/new-admin/
Log:
Move the new-admin branch into the attic.

Copied: django/branches/attic/new-admin (from rev 11512, 
django/branches/new-admin)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11513 - in django/branches/soc2009/model-validation: django/contrib/admin django/contrib/admin/templates/admin/edit_inline django/contrib/admin/templatetags django/contrib/auth/tests djan

[noreply]

Author: Honza_Kral
Date: 2009-09-11 16:23:55 -0500 (Fri, 11 Sep 2009)
New Revision: 11513

Modified:
   django/branches/soc2009/model-validation/django/contrib/admin/sites.py
   
django/branches/soc2009/model-validation/django/contrib/admin/templates/admin/edit_inline/tabular.html
   
django/branches/soc2009/model-validation/django/contrib/admin/templatetags/admin_list.py
   django/branches/soc2009/model-validation/django/contrib/admin/widgets.py
   
django/branches/soc2009/model-validation/django/contrib/auth/tests/__init__.py
   django/branches/soc2009/model-validation/django/core/management/base.py
   django/branches/soc2009/model-validation/django/core/urlresolvers.py
   django/branches/soc2009/model-validation/django/forms/widgets.py
   django/branches/soc2009/model-validation/django/utils/datastructures.py
   django/branches/soc2009/model-validation/docs/ref/forms/widgets.txt
   django/branches/soc2009/model-validation/docs/ref/request-response.txt
   django/branches/soc2009/model-validation/docs/topics/auth.txt
   django/branches/soc2009/model-validation/docs/topics/generic-views.txt
   
django/branches/soc2009/model-validation/tests/regressiontests/admin_views/tests.py
   
django/branches/soc2009/model-validation/tests/regressiontests/forms/error_messages.py
   
django/branches/soc2009/model-validation/tests/regressiontests/templates/filters.py
Log:
[soc2009/model-validation] Merged to trunk at r11499

Modified: django/branches/soc2009/model-validation/django/contrib/admin/sites.py
===
--- django/branches/soc2009/model-validation/django/contrib/admin/sites.py  
2009-09-11 21:23:21 UTC (rev 11512)
+++ django/branches/soc2009/model-validation/django/contrib/admin/sites.py  
2009-09-11 21:23:55 UTC (rev 11513)
@@ -300,7 +300,7 @@
 user = authenticate(username=username, password=password)
 if user is None:
 message = ERROR_MESSAGE
-if u'@' in username:
+if username is not None and u'@' in username:
 # Mistakenly entered e-mail address instead of username? Look 
it up.
 try:
 user = User.objects.get(email=username)

Modified: 
django/branches/soc2009/model-validation/django/contrib/admin/templates/admin/edit_inline/tabular.html
===
--- 
django/branches/soc2009/model-validation/django/contrib/admin/templates/admin/edit_inline/tabular.html
  2009-09-11 21:23:21 UTC (rev 11512)
+++ 
django/branches/soc2009/model-validation/django/contrib/admin/templates/admin/edit_inline/tabular.html
  2009-09-11 21:23:55 UTC (rev 11513)
@@ -15,6 +15,7 @@
  {% if inline_admin_formset.formset.can_delete %}{% trans "Delete?" 
%}{% endif %}
  
 
+ 
  {% for inline_admin_form in inline_admin_formset %}
 {% if inline_admin_form.form.non_field_errors %}
 {{ 
inline_admin_form.form.non_field_errors }}
@@ -57,7 +58,7 @@
 
 
  {% endfor %}
-
+ 

 
 

Modified: 
django/branches/soc2009/model-validation/django/contrib/admin/templatetags/admin_list.py
===
--- 
django/branches/soc2009/model-validation/django/contrib/admin/templatetags/admin_list.py
2009-09-11 21:23:21 UTC (rev 11512)
+++ 
django/branches/soc2009/model-validation/django/contrib/admin/templatetags/admin_list.py
2009-09-11 21:23:55 UTC (rev 11513)
@@ -22,7 +22,7 @@
 elif i == cl.page_num:
 return mark_safe(u'%d ' % (i+1))
 else:
-return mark_safe(u'%d ' % 
(cl.get_query_string({PAGE_VAR: i}), (i == cl.paginator.num_pages-1 and ' 
class="end"' or ''), i+1))
+return mark_safe(u'%d ' % 
(escape(cl.get_query_string({PAGE_VAR: i})), (i == cl.paginator.num_pages-1 and 
' class="end"' or ''), i+1))
 paginator_number = register.simple_tag(paginator_number)
 
 def pagination(cl):
@@ -265,7 +265,7 @@
 day_lookup = cl.params.get(day_field)
 year_month_format, month_day_format = get_partial_date_formats()
 
-link = lambda d: mark_safe(cl.get_query_string(d, [field_generic]))
+link = lambda d: cl.get_query_string(d, [field_generic])
 
 if year_lookup and month_lookup and day_lookup:
 day = datetime.date(int(year_lookup), int(month_lookup), 
int(day_lookup))

Modified: 
django/branches/soc2009/model-validation/django/contrib/admin/widgets.py
===
--- django/branches/soc2009/model-validation/django/contrib/admin/widgets.py
2009-09-11 21:23:21 UTC (rev 11512)
+++ django/branches/soc2009/model-validation/django/contrib/admin/widgets.py
2009-09-11 21:23:55 UTC (rev 11513)
@@ -7,6 +7,7 @@
 from django import forms
 from django.forms.widgets import RadioFieldRenderer
 from django.forms.util import flatatt
+from django.utils.html import escape
 from django.utils.text import 

[Changeset] r11512 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:23:21 -0500 (Fri, 11 Sep 2009)
New Revision: 11512

Added:
   django/branches/attic/multiple-db-support/
Removed:
   django/branches/multiple-db-support/
Log:
Move the (old, not Alex's current SoC one) multiple-db-support branch into the 
attic.

Copied: django/branches/attic/multiple-db-support (from rev 11511, 
django/branches/multiple-db-support)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11511 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:22:22 -0500 (Fri, 11 Sep 2009)
New Revision: 11511

Added:
   django/branches/attic/multi-auth/
Removed:
   django/branches/multi-auth/
Log:
Move the multi-auth branch into the attic.

Copied: django/branches/attic/multi-auth (from rev 11510, 
django/branches/multi-auth)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11510 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:21:38 -0500 (Fri, 11 Sep 2009)
New Revision: 11510

Added:
   django/branches/attic/magic-removal/
Removed:
   django/branches/magic-removal/
Log:
Move the original magic-removal branch into the attic.

Copied: django/branches/attic/magic-removal (from rev 11509, 
django/branches/magic-removal)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11509 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:20:43 -0500 (Fri, 11 Sep 2009)
New Revision: 11509

Added:
   django/branches/attic/i18n/
Removed:
   django/branches/i18n/
Log:
Move the original i18n branch into the attic.

Copied: django/branches/attic/i18n (from rev 11508, django/branches/i18n)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11508 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:20:04 -0500 (Fri, 11 Sep 2009)
New Revision: 11508

Added:
   django/branches/attic/gis/
Removed:
   django/branches/gis/
Log:
Move the original GIS branch into the attic.

Copied: django/branches/attic/gis (from rev 11507, django/branches/gis)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11507 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:19:08 -0500 (Fri, 11 Sep 2009)
New Revision: 11507

Added:
   django/branches/attic/generic-auth/
Removed:
   django/branches/generic-auth/
Log:
Move the generic-auth branch into the attic.

Copied: django/branches/attic/generic-auth (from rev 11506, 
django/branches/generic-auth)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11506 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:17:46 -0500 (Fri, 11 Sep 2009)
New Revision: 11506

Added:
   django/branches/attic/boulder-oracle-sprint/
Removed:
   django/branches/boulder-oracle-sprint/
Log:
Move the original Oracle branch into the attic.

Copied: django/branches/attic/boulder-oracle-sprint (from rev 11505, 
django/branches/boulder-oracle-sprint)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11505 - in django/branches: . attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 16:14:38 -0500 (Fri, 11 Sep 2009)
New Revision: 11505

Added:
   django/branches/attic/full-history/
Removed:
   django/branches/full-history/
Log:
Move full-history into attic.

Copied: django/branches/attic/full-history (from rev 11500, 
django/branches/full-history)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11865: Form media lacks support for raw javascript

[Django]

#11865: Form media lacks support for raw javascript
---+
 Reporter:  tarequeh   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Forms  | Version:  SVN   
 Keywords:  form media raw javascript  |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Form media allows form exclusive css and js to be linked in a systematic
 fashion. But it lacks support for inclusion of raw javascript that are
 generated on a per form basis (e.g. initialization of TinyMCE). As a
 result widget creators have to append javascript to their rendered widget.
 This translates into bad html practice of including javascript at random
 points of the HTML file.

 This situation can be resolved by adding a third media type: raw_js which
 can be included at a desired point in the template as {{{ {{
 form.media.raw_js }} }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11504 - in django/branches/soc2009/model-validation: . django django/contrib/admin django/contrib/admin/templates/admin django/contrib/gis/management/commands django/core/management/comma

[noreply]

Author: Honza_Kral
Date: 2009-09-11 16:06:15 -0500 (Fri, 11 Sep 2009)
New Revision: 11504

Added:
   django/branches/soc2009/model-validation/docs/internals/svn.txt
Modified:
   django/branches/soc2009/model-validation/django/__init__.py
   django/branches/soc2009/model-validation/django/contrib/admin/options.py
   
django/branches/soc2009/model-validation/django/contrib/admin/templates/admin/delete_selected_confirmation.html
   
django/branches/soc2009/model-validation/django/contrib/gis/management/commands/inspectdb.py
   
django/branches/soc2009/model-validation/django/core/management/commands/inspectdb.py
   django/branches/soc2009/model-validation/django/db/backends/__init__.py
   django/branches/soc2009/model-validation/django/db/backends/oracle/base.py
   
django/branches/soc2009/model-validation/django/db/backends/oracle/introspection.py
   django/branches/soc2009/model-validation/docs/conf.py
   django/branches/soc2009/model-validation/docs/howto/deployment/modpython.txt
   django/branches/soc2009/model-validation/docs/howto/deployment/modwsgi.txt
   django/branches/soc2009/model-validation/docs/index.txt
   django/branches/soc2009/model-validation/docs/internals/committers.txt
   
django/branches/soc2009/model-validation/docs/ref/contrib/formtools/form-wizard.txt
   django/branches/soc2009/model-validation/docs/ref/databases.txt
   django/branches/soc2009/model-validation/docs/ref/forms/widgets.txt
   django/branches/soc2009/model-validation/setup.py
   
django/branches/soc2009/model-validation/tests/modeltests/expressions/models.py
   
django/branches/soc2009/model-validation/tests/regressiontests/backends/tests.py
   
django/branches/soc2009/model-validation/tests/regressiontests/introspection/tests.py
   
django/branches/soc2009/model-validation/tests/regressiontests/queries/models.py
Log:
[soc2009/model-validation] Merged to trunk at r11478

Modified: django/branches/soc2009/model-validation/django/__init__.py
===
--- django/branches/soc2009/model-validation/django/__init__.py 2009-09-11 
19:42:32 UTC (rev 11503)
+++ django/branches/soc2009/model-validation/django/__init__.py 2009-09-11 
21:06:15 UTC (rev 11504)
@@ -1,4 +1,4 @@
-VERSION = (1, 1, 0, 'final', 0)
+VERSION = (1, 2, 0, 'alpha', 0)
 
 def get_version():
 version = '%s.%s' % (VERSION[0], VERSION[1])

Modified: 
django/branches/soc2009/model-validation/django/contrib/admin/options.py
===
--- django/branches/soc2009/model-validation/django/contrib/admin/options.py
2009-09-11 19:42:32 UTC (rev 11503)
+++ django/branches/soc2009/model-validation/django/contrib/admin/options.py
2009-09-11 21:06:15 UTC (rev 11504)
@@ -482,7 +482,7 @@
 
 def get_action(self, action):
 """
-Return a given action from a parameter, which can either be a calable,
+Return a given action from a parameter, which can either be a callable,
 or the name of a method on the ModelAdmin.  Return is a tuple of
 (callable, name, description).
 """

Modified: 
django/branches/soc2009/model-validation/django/contrib/admin/templates/admin/delete_selected_confirmation.html
===
--- 
django/branches/soc2009/model-validation/django/contrib/admin/templates/admin/delete_selected_confirmation.html
 2009-09-11 19:42:32 UTC (rev 11503)
+++ 
django/branches/soc2009/model-validation/django/contrib/admin/templates/admin/delete_selected_confirmation.html
 2009-09-11 21:06:15 UTC (rev 11504)
@@ -19,7 +19,7 @@
 {% endfor %}
 
 {% else %}
-{% blocktrans %}Are you sure you want to delete the selected {{ 
object_name }} objects? All of the following objects and it's related items 
will be deleted:{% endblocktrans %}
+{% blocktrans %}Are you sure you want to delete the selected {{ 
object_name }} objects? All of the following objects and their related items 
will be deleted:{% endblocktrans %}
 {% for deleteable_object in deletable_objects %}
 {{ deleteable_object|unordered_list }}
 {% endfor %}
@@ -34,4 +34,4 @@
 
 
 {% endif %}
-{% endblock %}
\ No newline at end of file
+{% endblock %}

Modified: 
django/branches/soc2009/model-validation/django/contrib/gis/management/commands/inspectdb.py
===
--- 
django/branches/soc2009/model-validation/django/contrib/gis/management/commands/inspectdb.py
2009-09-11 19:42:32 UTC (rev 11503)
+++ 
django/branches/soc2009/model-validation/django/contrib/gis/management/commands/inspectdb.py
2009-09-11 21:06:15 UTC (rev 11504)
@@ -131,7 +131,7 @@
 if srid != 4326: extra_params['srid'] = srid
 else:
 try:
-field_type = 
connection.introspection.data_types_reverse[row[1]]
+   

Re: [Django] #11783: django.contrib.humanize.templatetags.ordinal throws TypeError for NoneType

[Django]

#11783: django.contrib.humanize.templatetags.ordinal throws TypeError for 
NoneType
---+
  Reporter:  realpolitik   | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Contrib apps  |   Version:  1.1
   
Resolution:|  Keywords:  contrib, humanize, 
ordinal, ValueError
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by punteney):

  * needs_tests:  1 => 0

Comment:

 Added a test to the patch to check for the None TypeError

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11863: Add a method to the orm to create Model instances from raw sql queries

[Django]

#11863: Add a method to the orm to create Model instances from raw sql queries
---+
  Reporter:  seanoc| Owner:  seanoc
Status:  assigned  | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by dc):

 Just one line:

 {{{
 cursor.execute(query, args)
 values = cursor.fetchrow()

 model = Model(*values)  # "boring boiler plate code"
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2471: [patch] date_based generic view doesn't work with DateField and sqlite

[Django]

#2471: [patch] date_based generic view doesn't work with DateField and sqlite
---+
  Reporter:  Steven Armstrong  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Generic views |   Version:  SVN   
Resolution:  invalid   |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

  * status:  reopened => closed
  * resolution:  => invalid

Comment:

 Bug not reproducible with python 2.6, sqlite3, and jango-trunk. See
 attached tar ball.

 python manage.py syncdb
 python manage.py runserver

 http://localhost:8000/bug/archive/2009/sep/11/

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11503 - django/branches/attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 14:42:32 -0500 (Fri, 11 Sep 2009)
New Revision: 11503

Removed:
   django/branches/attic/full-history/
Log:
Delete that, should've done a mv instead of a cp


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11502 - django/branches/attic

[noreply]

Author: ubernostrum
Date: 2009-09-11 14:39:26 -0500 (Fri, 11 Sep 2009)
New Revision: 11502

Added:
   django/branches/attic/full-history/
Log:
Move full-history branch into attic.

Copied: django/branches/attic/full-history (from rev 11501, 
django/branches/full-history)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #6273: Support for passwd-like password changing

[Django]

#6273: Support for passwd-like password changing
--+-
  Reporter:  toxik| Owner:  justinlilly
Status:  new  | Milestone: 
 Component:  django-admin.py  |   Version:  SVN
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by justinlilly):

  * needs_better_patch:  1 => 0
  * needs_tests:  1 => 0

Comment:

 Russel has given me special dispensation for making this patch a "manual
 test" due to the complications for testing it. Should be ready for review,
 then check in.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11501 - django/branches/releases/1.1.X/django

[noreply]

Author: ubernostrum
Date: 2009-09-11 14:08:55 -0500 (Fri, 11 Sep 2009)
New Revision: 11501

Modified:
   django/branches/releases/1.1.X/django/__init__.py
Log:
This branch is 1.1.1 pre-alpha.

Modified: django/branches/releases/1.1.X/django/__init__.py
===
--- django/branches/releases/1.1.X/django/__init__.py   2009-09-11 19:05:24 UTC 
(rev 11500)
+++ django/branches/releases/1.1.X/django/__init__.py   2009-09-11 19:08:55 UTC 
(rev 11501)
@@ -1,4 +1,4 @@
-VERSION = (1, 2, 0, 'alpha', 0)
+VERSION = (1, 1, 1, 'alpha', 0)
 
 def get_version():
 version = '%s.%s' % (VERSION[0], VERSION[1])


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11500 - django/branches/releases

[noreply]

Author: ubernostrum
Date: 2009-09-11 14:05:24 -0500 (Fri, 11 Sep 2009)
New Revision: 11500

Added:
   django/branches/releases/1.1.X/
Log:
Create 1.1 release branch.

Copied: django/branches/releases/1.1.X (from rev 11499, django/trunk)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11864: Relationship backreference documentation is hard to find

[Django]

#11864: Relationship backreference documentation is hard to find
+---
  Reporter:  anonymous  | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  1.1
Resolution: |  Keywords:  relationships foreigkey
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11863: Add a method to the orm to create Model instances from raw sql queries

[Django]

#11863: Add a method to the orm to create Model instances from raw sql queries
---+
  Reporter:  seanoc| Owner:  seanoc
Status:  assigned  | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by seanoc):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * version:  => SVN
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11864: Relationship backreference documentation is hard to find

[Django]

#11864: Relationship backreference documentation is hard to find
-+--
 Reporter:  anonymous|   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Documentation| Version:  1.1   
 Keywords:  relationships foreigkey  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 I would expect that documentation on backreferences in relationships would
 be documented under Model API documentation, but it takes a few clicks
 from there to see how it works.

 http://docs.djangoproject.com/en/dev/topics/db/models/#relationships

 will, if the seeker of wisdom is pretty sharp or diligent, lead to one
 link labeled "the model field reference", which if followed, takes one to

 http://docs.djangoproject.com/en/dev/ref/models/fields/#foreign-key-
 arguments

 From there, one follows a link labeled "related objects documentation"
 that points at

 http://docs.djangoproject.com/en/dev/topics/db/queries/#backwards-related-
 objects

 which is where the fact that if I have a one-many relationship between Foo
 and Bar, where the Bar model class has a ForeignKey reference to Foo, then
 instances of the Foo
 class will have an attribute named "bar_set" whose value is a relationship
 manager (and that fact's documented on a page about queries).

 All this means that the highly useful and important fact about how Django
 manages the relationship from Foos to Bars is two clicks and quite a bit
 of reading away from the starting point from learning about
 relationships. It might be useful for newcomers to have a quicker path
 (perhaps including a sentence example of the form "if a Car model has a
 ForeignKey reference to the Manufacturer model, then Manufacturer
 instances will have an attribute "car_set" that provides access to the
 related Car instances") -- a natural place for this example might be under
 the docs for ForeignKey.related_name
 
(http://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.ForeignKey.related_name),
 but as it's such a useful an interesting feature, if there's an even more
 prominent place to put it, so much the better.

 thanks!

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11863: Add a method to the orm to create Model instances from raw sql queries

[Django]

#11863: Add a method to the orm to create Model instances from raw sql queries
--+-
 Reporter:  seanoc|   Owner:  seanoc
   Status:  new   |   Milestone:  1.2   
Component:  Database layer (models, ORM)  | Version:
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 There should be a mechanism to easily convert the result of a raw sql
 query into model instances.  It is currently possible to write code to
 generate model instances from raw sql query results but its a fair about
 of boring boiler plate code.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11842: django-admin.py should display help output when no arguments are given

[Django]

#11842: django-admin.py should display help output when no arguments are given
--+-
  Reporter:  bitprophet   | Owner:  nobody
Status:  new  | Milestone:
 Component:  django-admin.py  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by bastih):

  * stage:  Unreviewed => Accepted

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #3469: Django.utils is not documented

[Django]

#3469: Django.utils is not documented
+---
  Reporter:  SmileyChris| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Someday/Maybe  | Has_patch:  0 
Needs_docs:  1  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by cmheisel):

  * owner:  cmheisel => nobody

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11839: Strip tags from django document title elements

[Django]

#11839: Strip tags from django document title elements
+---
  Reporter:  glenjamin  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by bastih):

  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Added a patch that should work.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #3469: Django.utils is not documented

[Django]

#3469: Django.utils is not documented
+---
  Reporter:  SmileyChris| Owner:  cmheisel
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  SVN 
Resolution: |  Keywords:  
 Stage:  Someday/Maybe  | Has_patch:  0   
Needs_docs:  1  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by cmheisel):

  * owner:  nobody => cmheisel

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11739: ContentFile() does not support unicode data

[Django]

#11739: ContentFile() does not support unicode data
---+
  Reporter:  adamnelson| Owner:  nobody
Status:  new   | Milestone:
 Component:  File uploads/storage  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by and...@zen4ever.com):

 I was trying to reproduce this on current trunk on Mac Leopard, everything
 works as it should, my results are:

 {{{
 >>> pager.content.save('tester.html', ContentFile(u'test1'))
 >>> pager.content.read()
 'test1'
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9310: 404 debug pages should show the name of the tried urlpattern if one exists.

[Django]

#9310: 404 debug pages should show the name of the tried urlpattern if one 
exists.
-+--
  Reporter:  floguy  | Owner:  tobias
Status:  assigned| Milestone:  1.2   
 Component:  Core framework  |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by tobias):

  * owner:  nobody => tobias
  * status:  new => assigned

Comment:

 working on this at djangocon sprints with adrian nye

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11212: Don't encode emails with base64/qp

[Django]

#11212: Don't encode emails with base64/qp
---+
  Reporter:  phr   | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  django.core.mail  |   Version:  SVN  
Resolution:|  Keywords:  send_mail
 Stage:  Unreviewed| Has_patch:  1
Needs_docs:  0 |   Needs_tests:  1
Needs_better_patch:  0 |  
---+
Comment (by phr):

 Yes, sure those tests fail. They test for:

 Content-Transfer-Encoding: quoted-printable

 at multiple places, which after the proposed change will not pass.
 If the input is pure ascii, that header will become:

 Content-Transfer-Encoding: 7bit

 If the input contains some accentuated character - e.g. 'áéí', there will
 be 8bit instead.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7270: selected_related() can not follow reverse relations of OneToOne.

[Django]

#7270: selected_related() can not follow reverse relations of OneToOne.
---+
  Reporter:  towjz...@hotmail.com  | Owner:  
mtredinnick
Status:  new   | Milestone:  1.2

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  
select_related onetoone reverse
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Comment (by bendavis78):

 @dchristian:  I'm a bit confused by your use case there, as I don't see
 how that particular setup would be used in a real-world situation.That
 is, I'm having trouble seeing a situation where I would have a one-to-one
 referencing a base model.  If you could provide a more real-world example
 that would help.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11499 - django/trunk/docs/topics

[noreply]

Author: lukeplant
Date: 2009-09-11 08:46:56 -0500 (Fri, 11 Sep 2009)
New Revision: 11499

Modified:
   django/trunk/docs/topics/generic-views.txt
Log:
Fixed #11554: Several errors in Generic Views Documentation. 

Thanks Ramiro. 
Refs #11477 - that ticket should have been marked a duplicate of #11554



Modified: django/trunk/docs/topics/generic-views.txt
===
--- django/trunk/docs/topics/generic-views.txt  2009-09-11 10:47:40 UTC (rev 
11498)
+++ django/trunk/docs/topics/generic-views.txt  2009-09-11 13:46:56 UTC (rev 
11499)
@@ -150,7 +150,7 @@
 publisher = models.ForeignKey(Publisher)
 publication_date = models.DateField()
 
-To build a list page of all books, we'd use a URLconf along these lines::
+To build a list page of all publishers, we'd use a URLconf along these lines::
 
 from django.conf.urls.defaults import *
 from django.views.generic import list_detail
@@ -176,7 +176,7 @@
 .. highlightlang:: html+django
 
 This template will be rendered against a context containing a variable called
-``object_list`` that contains all the book objects. A very simple template
+``object_list`` that contains all the publisher objects. A very simple template
 might look like the following::
 
 {% extends "base.html" %}
@@ -217,7 +217,7 @@
 You might have noticed that our sample publisher list template stores all the
 books in a variable named ``object_list``. While this works just fine, it isn't
 all that "friendly" to template authors: they have to "just know" that they're
-dealing with books here. A better name for that variable would be
+dealing with publishers here. A better name for that variable would be
 ``publisher_list``; that variable's content is pretty obvious.
 
 We can change the name of that variable easily with the 
``template_object_name``
@@ -241,14 +241,14 @@
 
 
 Often you simply need to present some extra information beyond that provided by
-the generic view. For example, think of showing a list of all the other
-publishers on each publisher detail page. The ``object_detail`` generic view
-provides the publisher to the context, but it seems there's no way to get a 
list
-of *all* publishers in that template.
+the generic view. For example, think of showing a list of all the books on each
+publisher detail page. The ``object_detail`` generic view provides the
+publisher to the context, but it seems there's no way to get additional
+information in that template.
 
 But there is: all generic views take an extra optional parameter,
 ``extra_context``. This is a dictionary of extra objects that will be added to
-the template's context. So, to provide the list of all publishers on the detail
+the template's context. So, to provide the list of all books on the detail
 detail view, we'd use an info dict like this:
 
 .. parsed-literal::


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10933: Avoid " TypeError: Cannot convert Decimal("0.0000") to Decimal " when the decimal module has been reloaded

[Django]

#10933: Avoid " TypeError: Cannot convert Decimal("0.") to Decimal  " when 
the
decimal module has been reloaded
---+
  Reporter:  gagravarr | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by lukeplant):

 If you could reproduce the error using a reload() statement in a test
 (probably put it in regressiontests/model_fields/tests.py), that would be
 great.  After that we could decide on a fix.  The fix above is probably
 OK.  I'd really like to know why 'decimal' is being reloaded, but given
 that this is causing genuine problems for people, it's better to fix it
 than leave it until we know the root cause.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11732: ModelAdmin.get_changelist_form should use ModelAdmin.form

[Django]

#11732: ModelAdmin.get_changelist_form should use ModelAdmin.form
-+--
  Reporter:  edcrypt | Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  django.contrib.admin|   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by lukeplant):

  * stage:  Unreviewed => Design decision needed

Comment:

 That's a really bad idea, and would cause lots of breakages, because many
 people will be assuming that the Form they have created will be used only
 for the change form, and not the change list.  We need a new attribute
 like 'changelist_form', if anything.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11692: CSRF middleware causing contrib.auth password change tests to fail

[Django]

#11692: CSRF middleware causing contrib.auth password change tests to fail
+---
  Reporter:  jdriscoll  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  SVN   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by lukeplant):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => wontfix
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 You have to run the tests with the middleware disabled.  None of the tests
 use proper browser emulation (i.e. posting hidden fields that are in the
 forms), and so will fail to get through the CSRF checks which rely on a
 hidden field.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11212: Don't encode emails with base64/qp

[Django]

#11212: Don't encode emails with base64/qp
---+
  Reporter:  phr   | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  django.core.mail  |   Version:  SVN  
Resolution:|  Keywords:  send_mail
 Stage:  Unreviewed| Has_patch:  1
Needs_docs:  0 |   Needs_tests:  1
Needs_better_patch:  0 |  
---+
Comment (by lukeplant):

 You need to update and add to the tests in
 tests/regressiontests/mail/tests.py, which fail with the above change.
 You should add tests that show what happens with 7bit and 8bit data.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11375: Redirect to another url in admin add view

[Django]

#11375: Redirect to another url in admin add view
---+
  Reporter:  slurms| Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by lukeplant):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 The normal way to achieve this is by overriding `ModelAdmin.response_add`.
 Therefore closing WONTFIX.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11183: BaseForm init leaves pointers pointing back to base_fields when widget is a Select

[Django]

#11183: BaseForm init leaves pointers pointing back to base_fields when widget 
is a
Select
-+--
  Reporter:  margieroginski  | Owner:  nobody
Status:  new | Milestone:
 Component:  Uncategorized   |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by lukeplant):

  * needs_better_patch:  => 0
  * needs_tests:  => 1
  * needs_docs:  => 0

Old description:

> == High Level Description ==
> When we create a form class, I think the deepcopy that is done does not
> do enough to correctly copy the class in the case when the widget is a
> Select widget.  The result is that parts of the class are left pointing
> back to the base_fields data, and when one tries to override the queryset
> at during render(), it is not possible due pointers that are incorrectly
> pointing back to base_fields data.
>
> == Detail ==
> When a base_field in a form points to a Select widget, the widget
> contains a choices attribute.  During initialiazation of a
> !ModelChoiceField, a !ModelChoiceIterator is created and the widget's
> choices attribute is set to point to it.  This is all done by the
> following line from !ModelChoiceField::__init__();
> self.queryset = queryset
>
> When BaseForm:__init__() runs, it does a deepcopy of self.base_fields.
> When copying the fields, we call the Widget::__deepcopy__() method.
> However, this method copies only the attributes and does not copy the
> !ModelChoiceIterator that a select widget points to.  I think that a copy
> should be made of this !ModelChoiceIterator, and furthermore, I think
> that after making the copy, the newly copied !ModelChoiceIterator's
> 'field' attribute needs to be updated so that it points to the copied
> field whose deepcopy caused it to be copied.
>
> I encountered this issue when I tried to override the queryset for a
> !ModelChoiceField with a line like this in the render() function of a
> widget that derives from a Select widget.  Here is some example code that
> my usage:
>
> {{{
> class OwnerSelectWidget(widgets.Select):
> def __init__(self, rel, attrs=None):
> self.rel = rel
> super(OwnerSelectWidget, self).__init__(attrs)
>

> def render(self, name, value, attrs=None):
> key = self.rel.get_related_field().name
> self.choices.field.queryset =
> self.rel.to._default_manager.filter(**{key: value})  <<=== important
> rendered = super(OwnerSelectWidget, self).render(name, value,
> attrs)
>
> }}}
>
> When the self.choices.field.queryset assignment is made, it references
> through the !ModelChoiceIterator to the field associated with the widget.
> In the current code base, at this point int the code, the widget has been
> copied, but it still references the original !ModelChoiceIterator, which
> references the !ModelChoiceField that is in base_fields, which references
> the original "base_fields" widget.  This is different than the 'self'
> widget, which is the copied version.  The result is that the
> self.choices.field.queryset assignment updates the wrong widget (the one
> from base_fields) with the new queryset.
>
> I made a patch to my code that seems to work.  However, I find the patch
> kind of ugly and I suspect someone that understands the code better than
> me might want to do this a different way.  I did two things:
>   * Created a __deepcopy__() method for the Select widget, which does the
> same thin that Widget::__deepcopy__() does, but also calls copy on the
> self.choices field
>   * Created a small loop that follows the deepcopy in
> BaseForm:__init__(), which runs through all fields that were copied, and
> if the field contains a'widget' attribute and  that widget attribute
> contains a 'choices' attribute and that 'choices' attribute contains a
> 'field' attribute, then it sets that 'field' attribute point to the newly
> copied field.  This is the part that I think is pretty ugly.
>
> The attached svn diff shows the patch.
>
> I ran the django testsuite with the command ./runtests.py
> --settings=settings and all tests passed and I have verified via my own
> debugging that this solves my problem.
> }}}

New description:

 == High Level Description ==
 When we create a form class, I think the deepcopy that is done does not do
 enough to correctly copy the class in the case when the widget is a Select
 widget.  The result is that parts of the class are left pointing back to
 the base_fields data, and when one tries to override the queryset at
 during render(), it is not possible due pointers that are incorrectly
 pointing back to base_fields data.

 == Detail ==
 When a base_field 

[Changeset] r11498 - in django/trunk: django/forms tests/regressiontests/forms

[noreply]

Author: lukeplant
Date: 2009-09-11 05:47:40 -0500 (Fri, 11 Sep 2009)
New Revision: 11498

Modified:
   django/trunk/django/forms/forms.py
   django/trunk/tests/regressiontests/forms/error_messages.py
Log:
Fixed #10968 - Form.errors should use Form.error_class.
 
Thanks for report and initial patch, matehat.


Modified: django/trunk/django/forms/forms.py
===
--- django/trunk/django/forms/forms.py  2009-09-11 09:42:17 UTC (rev 11497)
+++ django/trunk/django/forms/forms.py  2009-09-11 10:47:40 UTC (rev 11498)
@@ -243,13 +243,13 @@
 value = getattr(self, 'clean_%s' % name)()
 self.cleaned_data[name] = value
 except ValidationError, e:
-self._errors[name] = e.messages
+self._errors[name] = self.error_class(e.messages)
 if name in self.cleaned_data:
 del self.cleaned_data[name]
 try:
 self.cleaned_data = self.clean()
 except ValidationError, e:
-self._errors[NON_FIELD_ERRORS] = e.messages
+self._errors[NON_FIELD_ERRORS] = self.error_class(e.messages)
 if self._errors:
 delattr(self, 'cleaned_data')
 

Modified: django/trunk/tests/regressiontests/forms/error_messages.py
===
--- django/trunk/tests/regressiontests/forms/error_messages.py  2009-09-11 
09:42:17 UTC (rev 11497)
+++ django/trunk/tests/regressiontests/forms/error_messages.py  2009-09-11 
10:47:40 UTC (rev 11498)
@@ -358,4 +358,42 @@
 Traceback (most recent call last):
 ...
 ValidationError: [u'4 IS INVALID CHOICE']
+
+# Subclassing ErrorList ###
+
+>>> from django.utils.safestring import mark_safe
+>>>
+>>> class TestForm(Form):
+...  first_name = CharField()
+...  last_name = CharField()
+...  birthday = DateField()
+...
+...  def clean(self):
+...  raise ValidationError("I like to be awkward.")
+...
+>>> class CustomErrorList(util.ErrorList):
+...  def __unicode__(self):
+...  return self.as_divs()
+...  def as_divs(self):
+...  if not self: return u''
+...  return mark_safe(u'%s'
+...% ''.join([u'%s' % e for e in self]))
+...
+
+This form should print errors the default way.
+
+>>> form1 = TestForm({'first_name': 'John'})
+>>> print form1['last_name'].errors
+This field is required.
+>>> print form1.errors['__all__']
+I like to be awkward.
+
+This one should wrap error groups in the customized way.
+
+>>> form2 = TestForm({'first_name': 'John'}, error_class=CustomErrorList)
+>>> print form2['last_name'].errors
+This field is required.
+>>> print form2.errors['__all__']
+I like to be awkward.
+
 """


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10968: Appears like there's something missing when subclassing django.forms' ErrorList

[Django]

#10968: Appears like there's something missing when subclassing django.forms'
ErrorList
-+--
  Reporter:  matehat | Owner:  lukeplant
Status:  assigned| Milestone:   
 Component:  Forms   |   Version:  1.0  
Resolution:  |  Keywords:   
 Stage:  Unreviewed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by lukeplant):

  * owner:  matehat => lukeplant
  * status:  new => assigned

Comment:

 The patch misses using `error_class` for the `__all__` error, and the
 tests rely on dictionary key order.  I've fixed these things, and will
 apply soon, thanks.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10990: Admin templates that extend base_site.html and override extrahead or extrastyle should include block.super last

[Django]

#10990: Admin templates that extend base_site.html and override extrahead or
extrastyle should include block.super last
---+
  Reporter:  kit1980   | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by lukeplant):

 This is not necessarily a simple decision -- what if the admin templates
 are themselves overriding CSS that is included in base_site.html (or want
 to in the future)?  Or if a developer wants to inherit from one of the
 'lower' templates and do CSS/javascript overriding, rather than customise
 base_site.html?

 For CSS, an alternative solution is `!important` declarations.  For
 javascript, can you do some hackery where my_urlify.js waits for the page
 to load and then monkey patches?  I just want to investigate
 alternatives...

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10917: admin/base.html should contain messages block

[Django]

#10917: admin/base.html should contain messages block
---+
  Reporter:  anonymous | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  1.1-beta-1 
   
Resolution:|  Keywords:  admin 
customization block messages
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  1 |  
---+
Changes (by lukeplant):

  * needs_better_patch:  0 => 1
  * needs_tests:  1 => 0

Comment:

 Patch needs to be "unified" style.  Using svn diff from base django
 directory is the easiest.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11497 - in django/trunk/django/contrib/admin: . templatetags

[noreply]

Author: lukeplant
Date: 2009-09-11 04:42:17 -0500 (Fri, 11 Sep 2009)
New Revision: 11497

Modified:
   django/trunk/django/contrib/admin/templatetags/admin_list.py
   django/trunk/django/contrib/admin/widgets.py
Log:
Fixed #11502 - wrong escaping in admin.
 
Thanks Tomasz Elendt.


Modified: django/trunk/django/contrib/admin/templatetags/admin_list.py
===
--- django/trunk/django/contrib/admin/templatetags/admin_list.py
2009-09-11 09:08:07 UTC (rev 11496)
+++ django/trunk/django/contrib/admin/templatetags/admin_list.py
2009-09-11 09:42:17 UTC (rev 11497)
@@ -265,7 +265,7 @@
 day_lookup = cl.params.get(day_field)
 year_month_format, month_day_format = get_partial_date_formats()
 
-link = lambda d: mark_safe(cl.get_query_string(d, [field_generic]))
+link = lambda d: cl.get_query_string(d, [field_generic])
 
 if year_lookup and month_lookup and day_lookup:
 day = datetime.date(int(year_lookup), int(month_lookup), 
int(day_lookup))

Modified: django/trunk/django/contrib/admin/widgets.py
===
--- django/trunk/django/contrib/admin/widgets.py2009-09-11 09:08:07 UTC 
(rev 11496)
+++ django/trunk/django/contrib/admin/widgets.py2009-09-11 09:42:17 UTC 
(rev 11497)
@@ -7,6 +7,7 @@
 from django import forms
 from django.forms.widgets import RadioFieldRenderer
 from django.forms.util import flatatt
+from django.utils.html import escape
 from django.utils.text import truncate_words
 from django.utils.translation import ugettext as _
 from django.utils.safestring import mark_safe
@@ -148,7 +149,7 @@
 def label_for_value(self, value):
 key = self.rel.get_related_field().name
 obj = self.rel.to._default_manager.get(**{key: value})
-return ' %s' % truncate_words(obj, 14)
+return ' %s' % escape(truncate_words(obj, 14))
 
 class ManyToManyRawIdWidget(ForeignKeyRawIdWidget):
 """


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11861: TypeError: object.__init__() takes no parameters

[Django]

#11861: TypeError: object.__init__() takes no parameters
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  SVN   
Resolution:  fixed  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by lukeplant):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => fixed
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 This was fixed in r11496.  It's specific to Python 2.6 and higher, sorry
 for problem.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11703: Added missing Super calls to 2 widget classes

[Django]

#11703: Added missing Super calls to 2 widget classes
+---
  Reporter:  Rupe   | Owner:  nobody
 
Status:  closed | Milestone:
 
 Component:  Forms  |   Version:  SVN   
 
Resolution:  fixed  |  Keywords:  forms widget super 
multiple-inheritance
 Stage:  Ready for checkin  | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by lukeplant):

  * status:  reopened => closed
  * needs_better_patch:  1 => 0
  * resolution:  => fixed

Comment:

 Because of the way `object.__init__()` works in Python 2.6 and later,
 classes which inherit from object directly should not call
 `super(...).__init__()`, because it can accept no arguments and is
 pointless.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r11496 - django/trunk/django/forms

[noreply]

Author: lukeplant
Date: 2009-09-11 04:08:07 -0500 (Fri, 11 Sep 2009)
New Revision: 11496

Modified:
   django/trunk/django/forms/widgets.py
Log:
Fixed Widget.__init__() for Python 2.6 and greater.  Refs #11703


Modified: django/trunk/django/forms/widgets.py
===
--- django/trunk/django/forms/widgets.py2009-09-10 22:49:05 UTC (rev 
11495)
+++ django/trunk/django/forms/widgets.py2009-09-11 09:08:07 UTC (rev 
11496)
@@ -139,7 +139,6 @@
 self.attrs = attrs.copy()
 else:
 self.attrs = {}
-super(Widget, self).__init__(attrs)
 
 def __deepcopy__(self, memo):
 obj = copy.copy(self)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #11862: Hebrew translation mistake

[Django]

#11862: Hebrew translation mistake
-+--
 Reporter:  adamri...@gmail.com  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Translations | Version:  1.1   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 The Hebrew translation of the string:
 "{{{%(name)s object with primary key %(key)r does not exist.}}}"
 is wrong.

 It should be:
 "{{{הפריט %(name)s עם המפתח הראשי %(key)r אינו קיים.}}}"

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11502: Wrong escaping in admin

[Django]

#11502: Wrong escaping in admin
--+-
  Reporter:  Tomasz Elendt   | Owner:  
nobody
Status:  new  | Milestone:  
  
 Component:  django.contrib.admin |   Version:  
SVN   
Resolution:   |  Keywords:  
  
 Stage:  Accepted | Has_patch:  
1 
Needs_docs:  0|   Needs_tests:  
0 
Needs_better_patch:  0|  
--+-
Comment (by Tomasz Elendt ):

 One of the fixes in this patch has been pushed into trunk in r11486
 (Ticket #11252). Attached patch need to be changed so that could be aplied
 on trunk in current state.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11703: Added missing Super calls to 2 widget classes

[Django]

#11703: Added missing Super calls to 2 widget classes
+---
  Reporter:  Rupe   | Owner:  nobody
 
Status:  reopened   | Milestone:
 
 Component:  Forms  |   Version:  SVN   
 
Resolution: |  Keywords:  forms widget super 
multiple-inheritance
 Stage:  Ready for checkin  | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  1  |  
+---
Changes (by terrex):

 * cc: guillermo.gutier...@uca.es (added)
  * needs_better_patch:  0 => 1

Comment:

 The same issue here. object.__init__() takes no parameters, so call it
 without it.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---