[Django] #14100: Spelling error

[Django]

#14100: Spelling error
---+
 Reporter:  tom_simpson|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Re: http://docs.djangoproject.com/en/dev/ref/contrib/comments/models/

 Hi,

 Just a spelling error within the second line below... [Nothing too
 serious] :)

 user_email
 The email of the user who posteed the comment.

 Thanks,
 Tom

-- 
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-upda...@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] #14099: modelformset not using _should_delete_form

[Django]

#14099: modelformset not using _should_delete_form
-+--
  Reporter:  kenth   | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by kenth):

  * version:  1.2 => SVN
  * component:  Uncategorized => Forms

-- 
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-upda...@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] #14099: modelformset not using _should_delete_form

[Django]

#14099: modelformset not using _should_delete_form
+---
  Reporter:  kenth  | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kenth):

  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * 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-upda...@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] #14099: modelformset not using _should_delete_form

[Django]

#14099: modelformset not using _should_delete_form
---+
 Reporter:  kenth  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The `BaseModelFormSet` class doesn't use the `BaseFormSet` method
 `_should_delete_form` when deciding if a form should be deleted. Instead
 it roots around in the form raw_data for the field that `BaseFormSet`
 added. This also makes it difficult to override `_should_delete_form`.

 This patch makes `BaseModelFormSet` use the `BaseFormSet` method.

-- 
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-upda...@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] #14090: Many sql queries needed to display change user form

[Django]

#14090: Many sql queries needed to display change user form
+---
  Reporter:  Suor   | Owner:  Suor
Status:  assigned   | Milestone:  
 Component:  Authentication |   Version:  1.2 
Resolution: |  Keywords:  
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by Suor):

  * stage:  Accepted => Ready for checkin

-- 
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-upda...@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] #14097: Add "--skip" option to inspectdb.

[Django]

#14097: Add "--skip" option to inspectdb.
+---
  Reporter:  adamv  | Owner:  nobody
Status:  closed | Milestone:
 Component:  django-admin.py inspectdb  |   Version:  1.2   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by adamv):

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

Comment:

 Sorry for the duplicate.

-- 
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-upda...@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] #14098: Add "--skip" option to inspectdb.

[Django]

#14098: Add "--skip" option to inspectdb.
---+
 Reporter:  adamv  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  django-admin.py inspectdb  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 If you're inspecting a MySQL db, and it has a view that references missing
 columns, then inspectdb will stop with an exception while inspecting that
 database.

 Add a "--skip" option to inspectdb to skip over tables that throw errors
 instead of aborting.

-- 
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-upda...@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] #14097: Add "--skip" option to inspectdb.

[Django]

#14097: Add "--skip" option to inspectdb.
---+
 Reporter:  adamv  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  django-admin.py inspectdb  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 If you're inspecting a MySQL db, and it has a view that references missing
 columns, then inspectdb will stop with an exception while inspecting that
 database.

 Add a "--skip" option to inspectdb to skip over tables that throw errors
 instead of aborting.

-- 
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-upda...@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] #14096: Insert code generated by models using multiple inheritance is incorrect and fails in postgresql

[Django]

#14096: Insert code generated by models using multiple inheritance is incorrect 
and
fails in postgresql
---+
  Reporter:  pembo13   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:  orm   
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by pembo13):

  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * 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-upda...@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] #13559: Need a contextprocessor for current site

[Django]

#13559: Need a contextprocessor for current site
---+
  Reporter:  tonnzor   | Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by gabrielhurley):

 This patch looks good to me, with the one exception: it probably needs a
 backwards incompatibility note for those spots where you removed the site
 variable being manually added to the context. If someone was relying on
 that variable being available in those specific cases and doesn't add the
 context processor they're going to find their code is suddenly broken.

-- 
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-upda...@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] #14096: Insert code generated by models using multiple inheritance is incorrect and fails in postgresql

[Django]

#14096: Insert code generated by models using multiple inheritance is incorrect 
and
fails in postgresql
--+-
 Reporter:  pembo13   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.2   
 Keywords:  orm   |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 When a model with multiple concrete parents is saved (inserted) the
 parents are saved first. Currently, the first parent is saved and its
 primary key is also set as the primary key of the yet unsaved top model.
 Any parent following uses the new primary key of 'self' and explicitly
 inserts the PK into the parent models table

 There is no reason to explicitly set the PK of any of the parent classes,
 the code already handles retrieval of the DB assigned PK.

 While other DBs let this pass, PostgreSQL does not. The problem comes not
 on the offending .save() but subsequent inserts to the table, this time
 '''without''' an explicit PK. The DB's internal counter has not advanced,
 so the next chosen PK already exists and yields a database error due to
 duplicate of a key field.

 There is no apparent need to explicitly set any of the PK on insert. I
 believe that changing the following code block within
 source:django/trunk/django/db/models/base.py#13538 , line 533 ,
 Model.save_base(...) can solve the problem:

 from
 {{{
 #!python
 if update_pk:
 setattr(self, meta.pk.attname, result)
 }}}

 to
 {{{
 #!python
 if update_pk and cls == self.__class__:
 setattr(self, meta.pk.attname, result)
 }}}

 I have attached a sample site ('minherit') with app ('data') and a test
 case in a ZIP file.

-- 
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-upda...@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] #10046: ModPythonHandler class should check for IOError when writing response

[Django]

#10046: ModPythonHandler class should check for IOError when writing response
-+--
  Reporter:  ewoudenberg | Owner:  nobody
Status:  new | Milestone:
 Component:  HTTP handling   |   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by edevil):

 * cc: andre.cruz+djang...@co.sapo.pt (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-upda...@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] #10046: ModPythonHandler class should check for IOError when writing response

[Django]

#10046: ModPythonHandler class should check for IOError when writing response
-+--
  Reporter:  ewoudenberg | Owner:  nobody
Status:  new | Milestone:
 Component:  HTTP handling   |   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by edevil):

 I also get these errors dozens of times per day. The problem lies not only
 when writing the response but when requesting POST parameters on a POST
 multipart request. If the request is not complete or the response cannot
 be written django should have an option to continue silently. Here is an
 example traceback from the CSRF middleware:

 {{{
 Traceback (most recent call last):

  File "/servers/python-2.6/lib/python2.6/site-
 packages/Django-1.2.1-py2.6.egg/django/core/handlers/base.py", line 95, in
 get_response
response = middleware_method(request, callback, callback_args,
 callback_kwargs)

  File "/servers/python-2.6/lib/python2.6/site-
 packages/Django-1.2.1-py2.6.egg/django/middleware/csrf.py", line 158, in
 process_view
request_csrf_token = request.POST.get('csrfmiddlewaretoken', None)

  File "/servers/python-2.6/lib/python2.6/site-
 packages/Django-1.2.1-py2.6.egg/django/core/handlers/wsgi.py", line 171,
 in _get_post
self._load_post_and_files()

  File "/servers/python-2.6/lib/python2.6/site-
 packages/Django-1.2.1-py2.6.egg/django/core/handlers/wsgi.py", line 137,
 in _load_post_and_files
self._post, self._files = self.parse_file_upload(self.META,
 self.environ['wsgi.input'])

  File "/servers/python-2.6/lib/python2.6/site-
 packages/Django-1.2.1-py2.6.egg/django/http/__init__.py", line 124, in
 parse_file_upload
return parser.parse()

  File "/servers/python-2.6/lib/python2.6/site-
 packages/Django-1.2.1-py2.6.egg/django/http/multipartparser.py", line 192,
 in parse
for chunk in field_stream:

  File "/servers/python-2.6/lib/python2.6/site-
 packages/Django-1.2.1-py2.6.egg/django/http/multipartparser.py", line 314,
 in next
output = self._producer.next()

  File "/servers/python-2.6/lib/python2.6/site-
 packages/Django-1.2.1-py2.6.egg/django/http/multipartparser.py", line 468,
 in next
for bytes in stream:

  File "/servers/python-2.6/lib/python2.6/site-
 packages/Django-1.2.1-py2.6.egg/django/http/multipartparser.py", line 314,
 in next
output = self._producer.next()

  File "/servers/python-2.6/lib/python2.6/site-
 packages/Django-1.2.1-py2.6.egg/django/http/multipartparser.py", line 375,
 in next
data = self.flo.read(self.chunk_size)

  File "/servers/python-2.6/lib/python2.6/site-
 packages/Django-1.2.1-py2.6.egg/django/http/multipartparser.py", line 405,
 in read
return self._file.read(num_bytes)

 IOError: request data read error


 ,
 POST:,
 COOKIES:{'_shibsession_49445349642e7361706f2e7074': '_f0',
 '_swa_uv': '3346690041278958258',
 '_swa_v': '4056487021281436498',
 'csrftoken': 'abe42a7836f8c63796897ba2b487982c',
 'sessionid': '7aef0bea88'},
 META:{'AUTH_TYPE': 'shibboleth',
 'CONTENT_LENGTH': '694660',
 'CONTENT_TYPE': 'multipart/form-data;
 boundary=WebKitFormBoundarysimXQBqzPfkcD9Mq',
 'CSRF_COOKIE': 'abe42a7836f8c63796897ba2b487982c',
 'DOCUMENT_ROOT': '/servers/profiles',
 'GATEWAY_INTERFACE': 'CGI/1.1',
 'HTTPS': '1',
 'HTTP_ACCEPT':
 
'application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5',
 'HTTP_ACCEPT_CHARSET': 'ISO-8859-1,utf-8;q=0.7,*;q=0.3',
 'HTTP_ACCEPT_ENCODING': 'gzip,deflate,sdch',
 'HTTP_ACCEPT_LANGUAGE': 'pt-PT,pt;q=0.8,en-US;q=0.6,en;q=0.4',
 'HTTP_CACHE_CONTROL': 'max-age=0',
 'HTTP_CONNECTION': 'keep-alive',
 'HTTP_HOST': 'id.sapo.pt',
 'HTTP_SHIB_APPLICATION_ID': 'IDSAPO',
 'HTTP_SHIB_ASSERTION_COUNT': '',
 'HTTP_SHIB_AUTHENTICATION_INSTANT': '2010-08-10T10:57:19.911Z',
 'HTTP_SHIB_AUTHENTICATION_METHOD':
 'urn:oasis:names:tc:SAML:1.0:am:unspecified',
 'HTTP_SHIB_AUTHNCONTEXT_CLASS':
 'urn:oasis:names:tc:SAML:1.0:am:unspecified',
 'HTTP_SHIB_AUTHNCONTEXT_DECL': '',
 'HTTP_USER_AGENT': 'Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US)
 AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.125 Safari/533.4',
 'PATH_INFO': u'/a/upload_avatar',
 'QUERY_STRING': '',
 'REQUEST_METHOD': 'POST',
 'REQUEST_URI': '/a/upload_avatar',
 'SCRIPT_NAME': u'',
 'SCRIPT_URI': 'https://id.sapo.pt/a/upload_avatar',
 'SCRIPT_URL': '/a/upload_avatar',
 'SERVER_PROTOCOL': 'HTTP/1.1',
 'SERVER_SIGNATURE': '',
 'SERVER_SOFTWARE': 'Apache',
 'SSL_CIPHER': 'RC4-MD5',
 'SSL_CIPHER_ALGKEYSIZE': '128',
 'SSL_CIPHER_EXPORT': 'false',
 'SSL_CIPHER_USEKEYSIZE': '128',
 'SSL_CLIENT_VERIFY': 'NONE',

Re: [Django] #13933: add ModelBackend inheritence to custom auth backend doc to enable Permissions

[Django]

#13933: add ModelBackend inheritence to custom auth backend doc to enable
Permissions
-+--
  Reporter:  mbg | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Documentation   |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ramiro):

  * stage:  Unreviewed => Design decision needed

Comment:

 Replying to [ticket:13933 mbg]:
 > On http://docs.djangoproject.com/en/dev/topics/auth/#writing-an-
 authentication-backend please consider adding some text describing how and
 when one might want to inherit ModelBackend in a custom authorization
 backend. Without ModelBackend the User Permissions are not set as expected
 from configuration seen in .../admin/auth/user/, e.g.
 get_all_permissions() returns [] unless ModelBackend is inherited or the
 code rolls its own Permissions.

 I think that is precisely what the 'Handling authorization in custom
 backend' section in that document says: The custom backend needs to
 implement its own custom authorization policies by implementing the
 `get_group_permissions()`, `get_all_permissions()`, `has_perm()` and
 `has_module_perms()` methods.

 (Granted, unfortunately there is a nomenclature gray area here because
 what Django calls authentication backends [both built-in and external]
 handle in reality both authentication and authorization.)

 IIRC one of the design guidelines followed when creating this pluggable
 backends machinery was to allow the use of classical Python techniques
 like duck typing instead of inheritance and this is the idea is conveyed
 by the text of the document. Adding an example using inheritance wouldn't
 be consistent with this philosophy.

 Leaving ticket open open but moving to DDN.

-- 
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-upda...@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] #14047: CommonMiddleware documentation tweak

[Django]

#14047: CommonMiddleware documentation tweak
+---
  Reporter:  Leon Matthews   | Owner:  
nobody
Status:  new| Milestone:

 Component:  Documentation  |   Version:  SVN   

Resolution: |  Keywords:  
middleware
 Stage:  Unreviewed | Has_patch:  1 

Needs_docs:  0  |   Needs_tests:  0 

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

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

Comment:

 Patch has had no attention, so I probably should have written a better
 summary...  Here goes:

 The docstring describing CommonMiddleware.process_response() doesn't match
 what the method is actually doing -- presumably it's a historical
 artifact.  Contrary to the docstring, no flatpage checking is done in
 process_response().  However broken link emails may be sent, something not
 mentioned in the docstring at all.

 The attached patch fixes the methods docstring, as well as adding a note
 about the conditional sending of broken link emails in
 docs/ref/middleware.txt

-- 
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-upda...@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] #13902: When using a ManyToMany in list_filter, results may apper more than once

[Django]

#13902: When using a ManyToMany in list_filter, results may apper more than once
---+
  Reporter:  rasca | Owner:  rasca  
 
Status:  new   | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  admin change_list 
list_filter manytomany
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by CarstenF):

 * cc: CarstenF (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-upda...@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] #11577: PLNIPField validation error when empty

[Django]

#11577: PLNIPField validation error when empty
-+--
  Reporter:  amz | Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.localflavor  |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by anonymous):

 This ticket is sitting for over a year, maybe it will be good to accept
 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-upda...@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] #14094: Cannot define CharField with unlimited length

[Django]

#14094: Cannot define CharField with unlimited length
-+--
  Reporter:  millerdev   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Core framework  |   Version:  1.2   
Resolution:  invalid |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by akaariai):

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

Comment:

 You should use models.TextField, which is unlimited in size.

-- 
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-upda...@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] #14095: Objects not saved when readonly_fields is set for inline admin

[Django]

#14095: Objects not saved when readonly_fields is set for inline admin
---+
  Reporter:  si...@pewpewlabs.com  | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  1.2
   
Resolution:|  Keywords:  TabularInline, 
inline, readonly_fields
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by si...@pewpewlabs.com):

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

Comment:

 Addendum: The inlined `BalanceCode`s show up in the admin interface, but
 they are not saved to database.

-- 
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-upda...@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] #14095: Objects not saved when readonly_fields is set for inline admin

[Django]

#14095: Objects not saved when readonly_fields is set for inline admin
+---
 Reporter:  si...@pewpewlabs.com|   Owner:  nobody
   Status:  new |   Milestone:
Component:  django.contrib.admin| Version:  1.2   
 Keywords:  TabularInline, inline, readonly_fields  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 = Code =
 '''models.py:'''
 {{{
 class BalanceCode(models.Model):
 created_at = models.DateField(auto_now_add=True)
 code = models.CharField(max_length=BALANCE_CODE_LENGTH, unique=True,
 default=generate_balance_code, help_text=code_help)
 value =
 models.PositiveIntegerField(default=BALANCE_CODE_DEFAULT_VALUE)
 refill_series = models.ForeignKey(RefillSeries)
 used_by = models.ForeignKey(Student, null=True, blank=True)
 used_at = models.DateField(blank=True, null=True)
 }}}
 {{{
 class RefillSeries(models.Model):
 issued = models.DateField(default=default_issued)
 least_valid_until =
 models.DateField(default=default_least_valid_until)
 }}}

 '''admin.py:'''
 {{{
 class BalanceCodeInline(admin.TabularInline):
 readonly_fields = ('code', )
 model = BalanceCode
 extra = SERIES_CODE_COUNT
 max_num = SERIES_CODE_COUNT
 }}}
 {{{
 class BalanceCodeAdmin(admin.ModelAdmin):
 readonly_fields = ('code', )
 }}}
 {{{
 class RefillSeriesAdmin(admin.ModelAdmin):
 inlines = (BalanceCodeInline,)
 }}}

 = Problem Description =
 == Expected ==
 When a new `RefillSeries` is created, `SERIES_CODE_COUNT BalanceCode`s
 should
 be created as well.

 == Actual ==
 No `BalanceCode`s are created. When `readonly_fields` is unset,
 `SERIES_CODE_COUNT` objects are created, as expected.

 Creating new `BalanceCode`s directly (not inlined in the `RefillSeries`
 admin
 interface) works as expected when `readonly_fields` is set.

-- 
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-upda...@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] #13823: Regression from 1.2.1: admin.site.root_path is None and it breaks admin links

[Django]

#13823: Regression from 1.2.1: admin.site.root_path is None and it breaks admin
links
---+
  Reporter:  gruszczy  | Owner:  jacmkno
 
Status:  closed| Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:  worksforme|  Keywords:  root_path admin 
broken links
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by jacmkno):

  * status:  assigned => closed
  * resolution:  => worksforme

Comment:

 weird, there is no problem at all... Sorry about that

-- 
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-upda...@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] #13823: Regression from 1.2.1: admin.site.root_path is None and it breaks admin links

[Django]

#13823: Regression from 1.2.1: admin.site.root_path is None and it breaks admin
links
---+
  Reporter:  gruszczy  | Owner:  jacmkno
 
Status:  assigned  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  root_path admin 
broken links
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Comment (by jacmkno):

 hummm ramiro, seems to be right, I tested this in a brand-new install
 and... there is no problem weird... I'll test a bit further...

-- 
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-upda...@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] #14094: Cannot define CharField with unlimited length

[Django]

#14094: Cannot define CharField with unlimited length
+---
 Reporter:  millerdev   |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.2   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Model validation throws an error on CharField with a null max_length:


 {{{
 #!python
 class Test(Model):
 char_field = CharField(max_length=None)
 }}}


 '''
 One or more models did not validate:[[BR]]
 test.test: "char_field": CharFields require a "max_length" attribute that
 is a positive integer.
 '''


 CharField should allow max_length=None, which intuitively means there is
 no maximum length. This is a perfectly valid use case. Postgres, for
 example, supports varchar/text columns without a length limit, but Django
 appears to have no way to define such a column in a model class.


 The model validation code looks like this
 
([http://code.djangoproject.com/browser/django/tags/releases/1.2.1/django/core/management/validation.py#L40
 django/core/management/validation.py:40]):



 {{{
 #!python
 if isinstance(f, models.CharField):
 try:
 max_length = int(f.max_length)
 if max_length <= 0:
 e.add(opts, '"%s": CharFields require a "max_length"
 attribute that is a positive integer.' % f.name)
 except (ValueError, TypeError):
 e.add(opts, '"%s": CharFields require a "max_length" attribute
 that is a positive integer.' % f.name)
 }}}


 It should be changed to something this:


 {{{
 #!python
 if isinstance(f, models.CharField) and f.max_length is not None:
 ...
 }}}


 The FileField does not happen to throw this error because it is not a
 derivative of CharField. However, the SQL generated for FileField is not
 correct when max_length=None, so that would need to be addressed as well.

-- 
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-upda...@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] #13933: add ModelBackend inheritence to custom auth backend doc to enable Permissions

[Django]

#13933: add ModelBackend inheritence to custom auth backend doc to enable
Permissions
+---
  Reporter:  mbg| Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 Reverting anonymous close as fixed since I don't see any evidence this has
 been addressed.

-- 
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-upda...@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] r13573 - in django/branches/soc2010/app-loading: django/core tests/appcachetests

[noreply]

Author: arthurk
Date: 2010-08-11 07:26:15 -0500 (Wed, 11 Aug 2010)
New Revision: 13573

Modified:
   django/branches/soc2010/app-loading/django/core/apps.py
   django/branches/soc2010/app-loading/tests/appcachetests/runtests.py
Log:
[soc2010/app-loading] store normalized version of INSTALLED_APPS in appcache

Modified: django/branches/soc2010/app-loading/django/core/apps.py
===
--- django/branches/soc2010/app-loading/django/core/apps.py 2010-08-11 
12:02:40 UTC (rev 13572)
+++ django/branches/soc2010/app-loading/django/core/apps.py 2010-08-11 
12:26:15 UTC (rev 13573)
@@ -40,6 +40,11 @@
 # List of App instances
 app_instances = [],
 
+# Normalized list of INSTALLED_APPS
+# This stores the module name of settings.INSTALLED_APPS
+# e.g. 'django.contrib.auth' for 'django.contrib.auth.AuthApp'
+installed_apps = [],
+
 # Mapping of app_labels to a dictionary of model names to model code.
 app_models = SortedDict(),
 
@@ -105,11 +110,13 @@
 app_instance = self.find_app(app_name)
 if not app_instance:
 if '.' in app_name:
+# get the app label from the full path
 app_instance_name = app_name.rsplit('.', 1)[1]
 else:
 app_instance_name = app_name
 app_instance = app_class(app_instance_name)
 self.app_instances.append(app_instance)
+self.installed_apps.append(app_name)
 
 # check if the app instance specifies a path to models
 # if not, we use the models.py file from the package dir

Modified: django/branches/soc2010/app-loading/tests/appcachetests/runtests.py
===
--- django/branches/soc2010/app-loading/tests/appcachetests/runtests.py 
2010-08-11 12:02:40 UTC (rev 13572)
+++ django/branches/soc2010/app-loading/tests/appcachetests/runtests.py 
2010-08-11 12:26:15 UTC (rev 13573)
@@ -42,6 +42,7 @@
 # because thread.RLock is un(deep)copyable
 cache.app_models = SortedDict()
 cache.app_instances = []
+cache.installed_apps = []
 
 cache.loaded = False
 cache.handled = {}
@@ -272,6 +273,15 @@
 """
 self.assertRaises(ImportError, cache.load_app, 'garageland')
 
+def test_installed_apps(self):
+"""
+Test that the installed_apps attribute is populated correctly
+"""
+settings.INSTALLED_APPS = ('model_app', 'nomodel_app.MyApp',)
+# populate cache
+cache.get_app_errors()
+self.assertEqual(cache.installed_apps, ['model_app', 'nomodel_app',])
+
 class RegisterModelsTests(AppCacheTestCase):
 """Tests for the register_models function"""
 

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13690: django admin use 102 SQL querys when i set the permission of a user!

[Django]

#13690: django admin use 102 SQL querys when i set the permission of a user!
---+
  Reporter:  lsc20051...@163.com   | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.2   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 #14090 reported this again and did propose a fix.

-- 
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-upda...@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] #14090: Many sql queries needed to display change user form

[Django]

#14090: Many sql queries needed to display change user form
-+--
  Reporter:  Suor| Owner:  Suor
Status:  assigned| Milestone:  
 Component:  Authentication  |   Version:  1.2 
Resolution:  |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

  * stage:  Unreviewed => Accepted

Comment:

 This is #13690 with a proposed fix, thanks. In a quick test on a random
 project the suggested change reduces the number of SQL queries for
 bringing up a change user page from 109 to 8.

-- 
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-upda...@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] r13572 - django/trunk/django/conf/locale/es_AR/LC_MESSAGES

[noreply]

Author: ramiro
Date: 2010-08-11 07:02:40 -0500 (Wed, 11 Aug 2010)
New Revision: 13572

Modified:
   django/trunk/django/conf/locale/es_AR/LC_MESSAGES/django.mo
   django/trunk/django/conf/locale/es_AR/LC_MESSAGES/django.po
Log:
Fixed typos in es_AR translation.

Modified: django/trunk/django/conf/locale/es_AR/LC_MESSAGES/django.mo
===
(Binary files differ)

Modified: django/trunk/django/conf/locale/es_AR/LC_MESSAGES/django.po
===
--- django/trunk/django/conf/locale/es_AR/LC_MESSAGES/django.po 2010-08-11 
11:15:00 UTC (rev 13571)
+++ django/trunk/django/conf/locale/es_AR/LC_MESSAGES/django.po 2010-08-11 
12:02:40 UTC (rev 13572)
@@ -7,7 +7,7 @@
 "Project-Id-Version: Django\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2010-08-06 15:38-0300\n"
-"PO-Revision-Date: 2010-08-06 16:02-0300\n"
+"PO-Revision-Date: 2010-08-11 09:00-0300\n"
 "Last-Translator: Ramiro \n"
 "Language-Team: Django-I18N \n"
 "Language: es_AR\n"
@@ -881,7 +881,7 @@
 #: contrib/admin/templates/admin/auth/user/change_password.html:35
 #: contrib/auth/forms.py:17 contrib/auth/forms.py:61 contrib/auth/forms.py:186
 msgid "Password"
-msgstr "Contraseña:"
+msgstr "Contraseña"
 
 #: contrib/admin/templates/admin/auth/user/change_password.html:41
 #: contrib/admin/templates/registration/password_change_form.html:37
@@ -1251,7 +1251,7 @@
 
 #: contrib/auth/forms.py:14 contrib/auth/forms.py:48 contrib/auth/forms.py:60
 msgid "Username"
-msgstr "Nombre de usuario:"
+msgstr "Nombre de usuario"
 
 #: contrib/auth/forms.py:15 contrib/auth/forms.py:49
 msgid "Required. 30 characters or fewer. Letters, digits and @/./+/-/_ only."

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14093: Unable to create a new session key on higher traffic

[Django]

#14093: Unable to create a new session key on higher traffic
-+--
 Reporter:  szy...@mwg.pl|   Owner:  nobody
   Status:  new  |   Milestone:
Component:  django.contrib.sessions  | Version:  1.2   
 Keywords:  session, cache, session key  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 Hi,

 We are using Django 1.2.1, cache session backend and from time to time, on
 higher traffic (but not so much, ~600 online users in 5 minutes) a few
 requests ends with exception:

 Traceback (most recent call last):

  File "/usr/lib64/python2.6/site-packages/django/core/handlers/base.py",
 line 80, in get_response
response = middleware_method(request)

  File "/home/wonderlife/app/request.py", line 78, in process_request
if request.user.is_authenticated():

  File "/usr/lib64/python2.6/site-
 packages/django/contrib/auth/middleware.py", line 9, in __get__
request._cached_user = get_user(request)

  File "/usr/lib64/python2.6/site-
 packages/django/contrib/auth/__init__.py", line 97, in get_user
user_id = request.session[SESSION_KEY]

  File "/usr/lib64/python2.6/site-
 packages/django/contrib/sessions/backends/base.py", line 46, in
 __getitem__
return self._session[key]

  File "/usr/lib64/python2.6/site-
 packages/django/contrib/sessions/backends/base.py", line 172, in
 _get_session
self._session_cache = self.load()

  File "/usr/lib64/python2.6/site-
 packages/django/contrib/sessions/backends/cache.py", line 16, in load
self.create()

  File "/usr/lib64/python2.6/site-
 packages/django/contrib/sessions/backends/cache.py", line 33, in create
raise RuntimeError("Unable to create a new session key.")

 RuntimeError: Unable to create a new session key.

-- 
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-upda...@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] r13571 - in django/branches/soc2010/app-loading: django/core tests/appcachetests

[noreply]

Author: arthurk
Date: 2010-08-11 06:15:00 -0500 (Wed, 11 Aug 2010)
New Revision: 13571

Modified:
   django/branches/soc2010/app-loading/django/core/apps.py
   django/branches/soc2010/app-loading/tests/appcachetests/runtests.py
Log:
[soc2010/app-loading] raise ImproperlyConfigured when trying to register models 
to an app that isnt listed in INSTALLED_APPS

Modified: django/branches/soc2010/app-loading/django/core/apps.py
===
--- django/branches/soc2010/app-loading/django/core/apps.py 2010-08-11 
01:39:37 UTC (rev 13570)
+++ django/branches/soc2010/app-loading/django/core/apps.py 2010-08-11 
11:15:00 UTC (rev 13571)
@@ -173,12 +173,8 @@
 def get_apps(self):
 "Returns a list of all installed modules that contain models."
 self._populate()
-
-# Ensure the returned list is always in the same order (with new apps
-# added at the end). This avoids unstable ordering on the admin app
-# list page, for example.
 return [app.models_module for app in self.app_instances\
-if app.models_module]
+if hasattr(app, 'models_module')]
 
 def get_app(self, app_label, emptyOK=False):
 """
@@ -266,13 +262,10 @@
 Register a set of models as belonging to an app.
 """
 app_instance = self.find_app(app_label)
-
-# Create a new App instance if the ModelBase tries to register
-# an app that isn't listed in INSTALLED_APPS
 if not app_instance:
-app_instance = App(app_label)
-self.app_instances.append(app_instance)
-
+raise ImproperlyConfigured('Could not find App instance with label 
"%s". '
+   'Please check your INSTALLED_APPS 
setting'
+   % app_label)
 for model in models:
 # Store as 'name: model' pair in a dictionary
 # in the models list of the App instance

Modified: django/branches/soc2010/app-loading/tests/appcachetests/runtests.py
===
--- django/branches/soc2010/app-loading/tests/appcachetests/runtests.py 
2010-08-11 01:39:37 UTC (rev 13570)
+++ django/branches/soc2010/app-loading/tests/appcachetests/runtests.py 
2010-08-11 11:15:00 UTC (rev 13571)
@@ -5,12 +5,11 @@
 from django.conf import settings
 from django.utils.datastructures import SortedDict
 from django.core.exceptions import ImproperlyConfigured
-from django.core.apps import MultipleInstancesReturned
+from django.core.apps import cache, MultipleInstancesReturned
 
 # remove when tests are integrated into the django testsuite
 settings.configure()
 
-from django.db.models.loading import cache
 
 class AppCacheTestCase(unittest.TestCase):
 """
@@ -41,17 +40,15 @@
 
 # we cannot copy() the whole cache.__dict__ in the setUp function
 # because thread.RLock is un(deep)copyable
-cache.app_store = SortedDict()
 cache.app_models = SortedDict()
-cache.app_errors = {}
+cache.app_instances = []
+
 cache.loaded = False
 cache.handled = {}
 cache.postponed = []
 cache.nesting_level = 0
 cache.write_lock = threading.RLock()
 cache._get_models_cache = {}
-
-cache.app_instances = []
 
 class AppCacheReadyTests(AppCacheTestCase):
 """
@@ -65,9 +62,9 @@
 
 def test_load_app(self):
 """Should return False after executing the load_app function"""
-cache.load_app('django.contrib.comments')
+cache.load_app('nomodel_app')
 self.assertFalse(cache.app_cache_ready())
-cache.load_app('django.contrib.comments', can_postpone=True)
+cache.load_app('nomodel_app', can_postpone=True)
 self.assertFalse(cache.app_cache_ready())
 
 class GetAppsTests(AppCacheTestCase):
@@ -75,12 +72,16 @@
 
 def test_get_apps(self):
 """Test that the correct models modules are returned"""
-settings.INSTALLED_APPS = ('django.contrib.auth',
+settings.INSTALLED_APPS = ('django.contrib.sites',
+   'django.contrib.contenttypes',
+   'django.contrib.auth',
'django.contrib.flatpages',)
 apps = cache.get_apps()
-self.assertEqual(len(apps), 2)
+self.assertEqual(len(apps), 4)
 self.assertTrue(apps[0], 'django.contrib.auth.models')
 self.assertTrue(apps[1], 'django.contrib.flatpages.models')
+self.assertTrue(apps[2], 'django.contrib.sites.models')
+self.assertTrue(apps[3], 'django.contrib.contenttypes.models')
 self.assertTrue(cache.app_cache_ready())
 
 def test_empty_models(self):
@@ -94,7 +95,8 @@
 
 def test_get_app(self):
 """Test that the correct module is returned"""
-settings.INSTALLED_APPS = 

Re: [Django] #13823: Regression from 1.2.1: admin.site.root_path is None and it breaks admin links

[Django]

#13823: Regression from 1.2.1: admin.site.root_path is None and it breaks admin
links
---+
  Reporter:  gruszczy  | Owner:  jacmkno
 
Status:  assigned  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  root_path admin 
broken links
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

  * stage:  Ready for checkin => Accepted

Comment:

 I cant' reproduce the initial issue reported here, and I suspect it isn't
 very common, otherwise we'd have dozens of report similar to this one
 already.

 I'm not saying the proposed workround/fix isn't necessary but IMHO it
 would be interesting to know what kind of setup leads to this issue. Can
 you create a reduced version of you admin config (urls.py url map entry
 and autodiscovery setup, admin model registration, ...) that still shows
 the problem?

 Also, are you migrating you project from pre 1.2-to 1.2 or is it a new,
 pristine project started with startproject/startapp?

-- 
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-upda...@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] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
-+--
  Reporter:  pixelcort   | Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by DrMeers):

 #13163 provides a simpler workaround for this -- each inline provides a
 link to the inline object provided it is also registered in that admin
 site, which allows you to edit its own inlines, etc. That way you can go
 as deep as you like. Not quite as easy as having it all rendered on the
 one page, but simple, robust and makes nested/recursive inlines navigable.

-- 
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-upda...@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] #13933: add ModelBackend inheritence to custom auth backend doc to enable Permissions

[Django]

#13933: add ModelBackend inheritence to custom auth backend doc to enable
Permissions
+---
  Reporter:  mbg| Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.2   
Resolution:  fixed  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => fixed
  * 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-upda...@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] #14090: Many sql queries needed to display change user form

[Django]

#14090: Many sql queries needed to display change user form
-+--
  Reporter:  Suor| Owner:  Suor
Status:  assigned| Milestone:  
 Component:  Authentication  |   Version:  1.2 
Resolution:  |  Keywords:  
 Stage:  Unreviewed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by Suor):

  * owner:  nobody => Suor
  * needs_better_patch:  => 0
  * status:  new => assigned
  * 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-upda...@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] #14092: ImageField should allow SVG

[Django]

#14092: ImageField should allow SVG
--+-
 Reporter:  graeme|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 A good many browsers now support SVG (and support is planned even for IE),
 so a good many uses of ImageField need SVG support.

-- 
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-upda...@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] #14091: PATCH: fix incorrect quoting in connection.queries for MySQL

[Django]

#14091: PATCH: fix incorrect quoting in connection.queries for MySQL
--+-
 Reporter:  danielr   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 The default implementation of `DatabaseOperations.last_executed_query`
 returns incorrectly quoted values for many common queries in MySQL. This
 means that  {{{connection.queries}}} does not properly reflect the query
 that was actually executed by the database, leading to hard-to-debug
 errors.

 For example, given this model:
 {{{
 class Foo(models.Model):
 name = models.CharField(max_length=10)
 added = models.DateTimeField()
 }}}

 doing this query:
 {{{
 Foo.objects.filter(added__lte=datetime.datetime.today())
 }}}

 gives this result from connection.queries:
 {{{
 [{'sql': "SELECT `foo_foo`.`id`, `foo_foo`.`name`, `foo_foo`.`added` FROM
 `foo_foo` WHERE `foo_foo`.`added` <= 2010-08-11 02:58:21  LIMIT 21",
   'time': '0.052'}]
 }}}
 which is invalid SQL because the timestamp is not quoted at all - although
 the query actually sent to the db is correctly quoted. More seriously,
 doing something like this:
 {{{
 values = ((u'1', '2010-08-09T15:55:28'),
   (u'2', '2010-08-10T15:55:28'),
   (u'3', '2010-08-11T15:55:28'))
 Foo.objects.extra(where=['(name, added) in %s'], params=[values])
 }}}
 wrongly reports that the `values` tuple has been correctly quoted:
 {{{
 [{'sql': "SELECT `foo_foo`.`id`, `foo_foo`.`name`, `foo_foo`.`added` FROM
 `foo_foo` WHERE (name, added) in ((u'0', '2010-08-08T15:55:28'),
 (u'1', '2010-08-09T15:55:28'), (u'2', '2010-08-10T15:55:28'), (u'3',
 '2010-08-11T15:55:28')) LIMIT 21",  'time': '0.052'}]
 }}}
 when in fact the query sent to the database is
 {{{
 SELECT `foo_foo`.`id`, `foo_foo`.`name`, `foo_foo`.`added` FROM `foo_foo`
 WHERE (name, added) in (("\'0\'", "\'2010-08-09T15:55:28\'"),
 ("\'0\'", "\'2010-08-09T15:55:28\'"), ("\'0\'",
 "\'2010-08-09T15:55:28\'"), ("\'0\'", "\'2010-08-09T15:55:28\'"),
 ("\'0\'", "\'2010-08-09T15:55:28\'"),
 ("\'0\'", "\'2010-08-09T15:55:28\'"), ("\'0\'",
 "\'2010-08-09T15:55:28\'"), ("\'0\'", "\'2010-08-09T15:55:28\'"),
 ("\'0\'", "\'2010-08-09T15:55:28\'"))
 }}}
 which is obviously not what was intended.

 The Postgres backend overrides the `last_executed_query` method to use the
 `cursor.query` atribute, ensuring that the query is correctly represented.
 MySQLdb actually provides a similar attribute, `cursor._executed`, and
 this should be used by the MySQL backend. Attached patch uses this, but
 falls back to the default implementation if the attribute is not populated
 (the current version of MySQLdb occasionally does not populate
 `_executed`, although this appears to be fixed in the forthcoming version
 2.)

 No tests attached, because I couldn't work out where to put them - happy
 to do so with some advice.

-- 
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-upda...@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] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
-+--
  Reporter:  pixelcort   | Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by hajbete):

 * cc: hajb...@idunbadboys.com (added)

Comment:

 Would love for this to be implemented!!

-- 
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-upda...@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.