[Django] #17623: Put Those Celebrities to Work For You

[Django]

#17623: Put Those Celebrities to Work For You
+
 Reporter:  markvarner97@…  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Uncategorized   |Version:  1.3
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 These alerts can make you aware of in mint condition to the job links to
 your place, when someone uses an article you have posted, or if bloggers
 and others are talking about you.You'll imitation timepiecees see quite a
 the minority names you'll recognize, some of who will be on your hold
 list.They couldn't be further than on or after the genuineness.Build
 options relatively than rigid positions.The
 [http://rolexreplicawatch.weebly.com timepiece imitations] money you earn
 is timepiece imitation pure profit on or after period 1.If you do evident
 publicity annually, that is a great way to see the benefits all day.but in
 the back of our minds we KNOW folks are making money hands-over-fist
 timepiece imitation silver on the internet everyday.You will need to
 market your site as distinctly, and imitation timepiece this could work
 distinctly for two people, individual making and individual selling
 online; 2.Affiliate marketing has been around on behalf of a extended
 spell.And it works used in support timepiece imitation of almost entirely
 companies because of a distinctive report.Through vast examine, the
 explanation fundamentals are identified.If someone buys a merchandise you
 promoted, you search out a commission.Now, having recognized the threat to
 energy refuge, sustainable economic growth, and the surroundings with the
 aim of is posed by rapid energy demand growth, China has placed energy
 efficiency and conservation as imitation timepiece timepiece its highest
 priority energy strategy.The sanctioned U.If you are new or do not know
 how to make currency with membership site, you can simply follow the
 following guide to learn about it.The tips with the intention of have been
 certain below will help your servers labor effectively.On imitation
 timepiece the same websites you know how to list navy for whatever type of
 online service you know how to offer.How All This Comes to Bite Your
 Online Presence AssThis is cheap timepiece imitation timepiece how I
 tolerate seen ancestors get caught for not paying as much as necessary
 attention to their sales/use tax responsibilities.What timepiece imitation
 is their underhanded?You should be gifted to be in the indication and
 communicate to endure.

-- 
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] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
--+
 Reporter:  etianen   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by saxix):

 * cc: saxix.rome@… (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.

[Changeset] r17415 - django/trunk

[noreply]

Author: carljm
Date: 2012-01-31 20:25:30 -0800 (Tue, 31 Jan 2012)
New Revision: 17415

Modified:
   django/trunk/AUTHORS
Log:
Fixed #17622 - Added Justin Myles Holmes to AUTHORS.

Modified: django/trunk/AUTHORS
===
--- django/trunk/AUTHORS2012-01-31 20:36:11 UTC (rev 17414)
+++ django/trunk/AUTHORS2012-02-01 04:25:30 UTC (rev 17415)
@@ -241,6 +241,7 @@
 hipertrac...@gmail.com
 Deryck Hodge 
 Brett Hoerner 
+Justin Myles Holmes 
 Eric Holscher 
 Ian Holsman 
 Kieran Holland 
@@ -515,6 +516,7 @@
 Makoto Tsuyuki 
 t...@gurgle.no
 David Tulig 
+Justine Tunney 
 Amit Upadhyay 
 Adam Vandenberg
 Geert Vanderkelen
@@ -556,7 +558,6 @@
 Gasper Zejn 
 Jarek Zgoda 
 Cheng Zhang
-Justine Tunney 
 
 A big THANK YOU goes to:
 

-- 
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] #17622: Request to be added to AUTHORS

[Django]

#17622: Request to be added to AUTHORS
---+
 Reporter:  jMyles |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Uncategorized  |Version:  1.3
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  0
UI/UX:  0  |
---+
Changes (by carljm):

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


Comment:

 In [17415]:
 {{{
 #!CommitTicketReference repository="" revision="17415"
 Fixed #17622 - Added Justin Myles Holmes to AUTHORS.
 }}}

-- 
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] #10045: Improve documentation of .annotate() / .filter() ordering quirks

[Django]

#10045: Improve documentation of .annotate() / .filter() ordering quirks
--+
 Reporter:  alex@…|Owner:
 Type:  Cleanup/optimization  |   Status:  reopened
Component:  Documentation |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by SmileyChris):

 (anon was me)

 In the project test, I create two `Publisher`s, and assign three `Book`s
 to the first publisher, two above a rating of `3.0`. Running
 
`Publisher.objects.annotate(num_books=Count('book')).filter(book__rating__gt=3.0)[0].num_books`
 returns **6**.

-- 
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] #10045: Improve documentation of .annotate() / .filter() ordering quirks

[Django]

#10045: Improve documentation of .annotate() / .filter() ordering quirks
--+
 Reporter:  alex@…|Owner:
 Type:  Cleanup/optimization  |   Status:  reopened
Component:  Documentation |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by anonymous):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 This seems more than documenting a "quirk". The very example given in the
 docs is 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-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] #17622: Request to be added to AUTHORS

[Django]

#17622: Request to be added to AUTHORS
---+
 Reporter:  jMyles |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 I've submitted a few patches to trunk which have been committed.  carljm
 told me to open a ticket with a patch adding myself to AUTHORS. Doing
 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-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] #17621: django.utils.translation.activate() issue

[Django]

#17621: django.utils.translation.activate() issue
--+
 Reporter:  tomasz.zawadzinski@…  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Internationalization  |Version:  1.3
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 django.utils.translation.activate() doesn't affect on form instances.
 Strings defined in a class of form (ex label, error_messages etc), are
 translated only in a result of setting a proper cookie or 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-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] #17620: Chrome fails with additional Content-Disposition header

[Django]

#17620: Chrome fails with additional Content-Disposition header
---+--
 Reporter:  jbauer@…   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by jbauer@…):

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


Comment:

 This apparently fails only with certain kinds of filenames (embedded
 spaces, commas), so I'm going to mark it as invalid.

-- 
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] #17620: Chrome fails with additional Content-Disposition header

[Django]

#17620: Chrome fails with additional Content-Disposition header
---+
 Reporter:  jbauer@…   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Later versions of Chrome will fail to render content if you follow this
 example by assigning an addition {{{ Content-Disposition }}} header, e.g.

 {{{ response['Content-Disposition'] = 'attachment;
 filename=somefilename.pdf' }}}

 The Chrome browser returns:

 '''Duplicate headers received from server'''

 The response from the server contained duplicate headers. This problem is
 generally the result of a misconfigured website or proxy. Only the website
 or proxy administrator can fix this issue.

 Error 349 (net::ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION):
 Multiple Content-Disposition headers received. This is disallowed to
 protect against HTTP response splitting attacks.

-- 
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] #17619: MemoryError when deleting objects with many generic relations

[Django]

#17619: MemoryError when deleting objects with many generic relations
-+-
 Reporter:  bjourne@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.3
  contrib.contenttypes   |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 While investigating this, I could not reproduce any extra queries using
 the test suite models.

 I am closing this as invalid. If you find out that there is reason to
 believe there is an bug in Django, then reopen this ticket.

-- 
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] #17619: MemoryError when deleting objects with many generic relations

[Django]

#17619: MemoryError when deleting objects with many generic relations
-+-
 Reporter:  bjourne@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.3
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by bjourne):

 I have found the cause for this. For the child model in the
 GenericRelation, I'm replacing the default manager with a custom one. That
 manager has some slight magic, like overriding the __getattr__ method
 which may be what is triggering the bug. I will investigate some more and
 see if it's just PEBKAC or if Django does something wrong.

-- 
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] #17619: MemoryError when deleting objects with many generic relations

[Django]

#17619: MemoryError when deleting objects with many generic relations
-+-
 Reporter:  bjourne@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.3
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 Looking at the stack trace, I think I see the error: The copy.copy() in
 db_manager() is causing the cache to be filled, in other words, the query
 is executed, without any filters. That is not good!

 I haven't verified anything about this yet. The reason is I am having a
 hard time to set up generic relations, as the documentation doesn't give
 me a copy-paste example. Could you provide this, and I will see what I can
 find out.

-- 
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] #14030: Use F() objects in aggregates(), annotates() and values()

[Django]

#14030: Use F() objects in aggregates(), annotates() and values()
-+
 Reporter:  delfick  |Owner:  nate_b
 Type:  New feature  |   Status:  assigned
Component:  ORM aggregation  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by akaariai):

 * needs_better_patch:  0 => 1
 * version:  1.2 =>


Comment:

 I am wondering about the hack in the patch: that is, adding an empty
 Aggregate over the given F expression. I guess the reason is to make this
 work:
 {{{
 >>> q =
 Entry.objects.annotate(cpb_ratio=F('n_comments')*1.0/F('n_pingbacks'))
 }}}

 Now, I have been wondering about something similar. In fact, I have been
 thinking of creating expressions you can inject into the query by
 .annotate().
 {{{
 caseexpr = RawSQL("case when %s > 0 then 'has '||%s||' comments' else 'no
 comments' end",
   params=(F('n_comments'), F('n_comments')))
 }}}
 And you could then do
 {{{
 >>> q =
 Entry.objects.annotate(has_comments=caseexpr).order_by('has_comments')
 (or, in my dreams the .order_by parameter could be .order_by(RawSQL('%s
 asc nulls last', params=(F('has_comments'),))
 }}}
 In effect, you could get rid of most .extra() uses by the above
 annotations. I have some reason to believe that the above changes, if
 implemented correctly, would make the ORM both faster and easier to
 understand. Of course, without an actual patch it is easy to claim that...
 :)

 Now, my point here is that I really like the ability to use annotations
 for other expressions than aggregates. But I really, really do not like
 the idea of adding an empty aggregate that in fact is not an aggregate. I
 bet that will break under some complex query, because Django thinks you
 have an aggregate in the query, but in SQL you do not have one. So, +1 on
 the idea, -1 on the current implementation.

 BTW: I am clearing the version field, from the documentation it seems the
 version field "Finally, it is possible to use the version attribute to
 indicate in which version the reported bug was identified.". Now, I read
 that as if there is no bug, there should not be any version either.
 Learning this as I write, so please correct if I am wrong.

-- 
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] #17469: `StartProject.test_custom_project_template_from_tarball_by_url` fails under Windows

[Django]

#17469: `StartProject.test_custom_project_template_from_tarball_by_url` fails 
under
Windows
-+-
 Reporter:  aaugustin|Owner:  jezdez
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.4-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 This test fails because the live server is unable to serve the
 `/admin_scripts/custom_templates/project_template.tgz`; instead, it runs
 into an infinite redirection loop.

 This problem occurs with any existing file, it isn't specific to
 `project_template.tgz`.

 {{{
 C:\Documents and Settings\Administrator\Desktop>C:\Python25\python.exe
 "\\vmware-host\Shared Folders\django-trunk\tests\runtests.py"
 --settings=tests.test_sqlite
 admin_scripts.StartProject.test_custom_project_template_from_tarball_by_url
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 > \\vmware-host\shared folders\django-
 
trunk\tests\regressiontests\admin_scripts\tests.py(1479)test_custom_project_template_from_tarball_by_url()
 -> self.assertTrue(os.path.exists(os.path.join(testproject_dir,
 'run.py')))
 (Pdb) p args
 ['startproject', '--template',
 'http://localhost:8081/admin_scripts/custom_templates/project_template.tgz',
 'urltestproject']
 (Pdb) import urllib2; urllib2.urlopen(args[2])
 *** HTTPError: HTTP Error 302: The HTTP server returned a redirect error
 that would lead to an infinite loop.
 The last 30x error message was:
 FOUND
 (Pdb) import urllib2;
 
urllib2.urlopen('http://localhost:8081/admin_scripts/custom_templates/project_template/manage.py')
 *** HTTPError: HTTP Error 302: The HTTP server returned a redirect error
 that would lead to an infinite loop.
 The last 30x error message was:
 FOUND
 (Pdb) import urllib2; urllib2.urlopen('http://localhost:8081/')
 *** HTTPError: HTTP Error 404: NOT FOUND
 }}}

 It appears that `django.views.static.serve` receives a "Windows-style"
 path instead of an "URL-style"path:
 {{{
 C:\Documents and Settings\Administrator\Desktop>C:\Python25\python.exe
 "\\vmware-host\Shared Folders\django-trunk\tests\runtests.py"
 --settings=tests.test_sqlite
 admin_scripts.StartProject.test_custom_project_template_from_tarball_by_url
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 > \\vmware-host\shared folders\django-
 trunk\django\views\static.py(33)serve()
 -> path = posixpath.normpath(urllib.unquote(path))
 (Pdb) path
 u'\\admin_scripts\\custom_templates\\project_template.tgz'
 (Pdb) request.path
 u'/admin_scripts/custom_templates/project_template.tgz'
 (Pdb) bt
   c:\python25\lib\threading.py(462)__bootstrap()
 -> self.__bootstrap_inner()
   c:\python25\lib\threading.py(486)__bootstrap_inner()
 -> self.run()
   \\vmware-host\shared folders\django-
 trunk\django\test\testcases.py(1062)run()
 -> self.httpd.serve_forever()
   \\vmware-host\shared folders\django-
 trunk\django\test\testcases.py(943)serve_forever()
 -> self._handle_request_noblock()
   \\vmware-host\shared folders\django-
 trunk\django\test\testcases.py(982)_handle_request_noblock()
 -> self.process_request(request, client_address)
   c:\python25\lib\socketserver.py(241)process_request()
 -> self.finish_request(request, client_address)
   c:\python25\lib\socketserver.py(254)finish_request()
 -> self.RequestHandlerClass(request, client_address, self)
   \\vmware-host\shared folders\users\myk\documents\dev\django-
 trunk\django\core\servers\basehttp.py(139)__init__()
   c:\python25\lib\socketserver.py(522)__init__()
 -> self.handle()
   c:\python25\lib\wsgiref\simple_server.py(138)handle()
 -> handler.run(self.server.get_app())
   c:\python25\lib\wsgiref\handlers.py(92)run()
 -> self.result = application(self.environ, self.start_response)
   \\vmware-host\shared folders\users\myk\documents\dev\django-
 trunk\django\contrib\staticfiles\handlers.py(67)__call__()
   \\vmware-host\shared folders\users\myk\documents\dev\django-
 trunk\django\contrib\staticfiles\handlers.py(68)__call__()
   \\vmware-host\shared folders\users\myk\documents\dev\django-
 trunk\django\core\handlers\wsgi.py(241)__call__()
   \\vmware-host\shared folders\users\myk\documents\dev\django-
 trunk\django\contrib\staticfiles\handlers.py(58)get_response()
   \\vmware-host\shared folders\django-
 trunk\django\test\testcases.py(1002)serve()
 -> document_root=self.get_base_dir())
 > \\vmware-host\shared folders\django-
 tru

Re: [Django] #17618: Variables names in template must not start with an underscore.

[Django]

#17618: Variables names in template must not start with an underscore.
--+
 Reporter:  cguillemette@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * version:  1.3 => SVN
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * 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.

[Django] #17619: MemoryError when deleting objects with many generic relations

[Django]

#17619: MemoryError when deleting objects with many generic relations
--+
 Reporter:  bjourne@… |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.contenttypes  |Version:  1.3
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 When I delete an object which has several generic relations pointing to
 it, I get a memory error. It seems like there is some memory leak or
 infinite recursion going on because the process just locks up for a few
 seconds while the Python process grows to 3gb in size and then terminates
 with the MemoryError.

 I don't have an isolated test case for it, but the problem is easy for me
 to reproduce and I can provide more details if requested. Here is the full
 traceback:


 {{{
 In [9]: g = Game.objects.get(id = 34519)

 In [10]: g.delete()

 MemoryError   Traceback (most recent call
 last)

 /app/tngfooty/ in ()

 /usr/local/lib/python2.7/dist-packages/django/db/models/base.pyc in
 delete(self, using)
 578
 579 collector = Collector(using=using)
 --> 580 collector.collect([self])
 581 collector.delete()
 582

 /usr/local/lib/python2.7/dist-packages/django/db/models/deletion.pyc in
 collect(self, objs, source, nullable, collect_related, source_attr,
 reverse_dependency)
 176 for relation in model._meta.many_to_many:
 177 if not relation.rel.through:
 --> 178 sub_objs =
 relation.bulk_related_objects(new_objs, self.using)
 179 self.collect(sub_objs,
 180  source=model,

 /usr/local/lib/python2.7/dist-
 packages/django/contrib/contenttypes/generic.pyc in
 bulk_related_objects(self, objs, using)
 183
 184 """
 --> 185 return
 self.rel.to._base_manager.db_manager(using).filter(**{
 186 "%s__pk" % self.content_type_field_name:
 187
 ContentType.objects.db_manager(using).get_for_model(self.model).pk,

 /usr/local/lib/python2.7/dist-packages/django/db/models/manager.pyc in
 db_manager(self, using)
  90
  91 def db_manager(self, using):
 ---> 92 obj = copy.copy(self)
  93 obj._db = using
  94 return obj

 /usr/lib/python2.7/copy.pyc in copy(x)
  86 reductor = getattr(x, "__reduce_ex__", None)
  87 if reductor:
 ---> 88 rv = reductor(2)
  89 else:
  90 reductor = getattr(x, "__reduce__", None)

 /usr/local/lib/python2.7/dist-packages/django/db/models/query.pyc in
 __getstate__(self)
  60 """
  61 # Force the cache to be fully populated.

 ---> 62 len(self)
  63
  64 obj_dict = self.__dict__.copy()

 /usr/local/lib/python2.7/dist-packages/django/db/models/query.pyc in
 __len__(self)
  80 self._result_cache = list(self._iter)
  81 else:
 ---> 82 self._result_cache = list(self.iterator())
  83 elif self._iter:
  84 self._result_cache.extend(self._iter)

 /usr/local/lib/python2.7/dist-packages/django/db/models/query.pyc in
 iterator(self)
 284 else:
 285 # Omit aggregates in object creation.

 --> 286 obj = model(*row[index_start:aggregate_start])
 287
 288 # Store the source database of the object


 /usr/local/lib/python2.7/dist-packages/django/db/models/base.pyc in
 __init__(self, *args, **kwargs)
 274
 275 def __init__(self, *args, **kwargs):
 --> 276 signals.pre_init.send(sender=self.__class__, args=args,
 kwargs=kwargs)
 277
 278 # Set up the storage for instance state


 /usr/local/lib/python2.7/dist-packages/django/dispatch/dispatcher.pyc in
 send(self, sender, **named)
 170
 171 for receiver in self._live_receivers(_make_id(sender)):
 --> 172 response = receiver(signal=self, sender=sender,
 **named)
 173 responses.append((receiver, response))
 174 return responses

 MemoryError:

 }}}

-- 
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
 Type:  Bug   |   Status:  reopened
Component:  File uploads/storage  |  Version:  1.1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 Thanks for those tests!

 What worries me in your patch, Cody, is that you are excluding cStringIO
 not only for !ContentFile, but for the plain File class. I guess that
 !ContentFile is mainly used in tests, where performance is less a concern
 (I see only one use in Django code, related to the collectstatic
 management command).

 That's why I think the code which should also be tested performance-wise
 is the __iter__ method of the File object.

-- 
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] #17618: Variables names in template must not start with an underscore.

[Django]

#17618: Variables names in template must not start with an underscore.
+
 Reporter:  cguillemette@…  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Documentation   |Version:  1.3
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 The doc (https://docs.djangoproject.com/en/dev/ref/templates/api/) says
 "Variable names must consist of any letter (A-Z), any digit (0-9), an
 underscore or a dot.".

 It can be misleading, because in fact, variable names can consist of
 underscores but can't start with one.

-- 
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] #16921: Add assertHTMLEqual and related assert methods to TestCase

[Django]

#16921: Add assertHTMLEqual and related assert methods to TestCase
-+-
 Reporter:  carljm   |Owner:
 Type:  New feature  |  gregmuellegger
Component:  Testing framework|   Status:  closed
 Severity:  Normal   |  Version:  SVN
 Keywords:  form-rendering   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by carljm):

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


Comment:

 In [17414]:
 {{{
 #!CommitTicketReference repository="" revision="17414"
 Fixed #16921 -- Added assertHTMLEqual and assertHTMLNotEqual assertions,
 and converted Django tests to use them where appropriate. Thanks Greg
 Müllegger.
 }}}

-- 
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
 Type:  Bug   |   Status:  reopened
Component:  File uploads/storage  |  Version:  1.1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by codysoyland):

 I did some really basic benchmarks that show the first patch, which
 removes the cStringIO module completely, is much faster on unicode data,
 but slower on binary data than the second patch, which wraps the cStringIO
 module. I don't know how conclusive these tests are though, because they
 are with small datasets.

 Test script (unicode):

 {{{
 from django.core.files.base import ContentFile
 import timeit
 print timeit.timeit(lambda: ContentFile(u'test').read())
 }}}

 Test script (bytes):

 {{{
 from django.core.files.base import ContentFile
 import timeit
 print timeit.timeit(lambda: ContentFile('test').read())
 }}}

 I ran each script 3 times on each patch. timeit runs the function
 1,000,000 times and returns the number of seconds elapsed.

 11739_with_test.diff (No cStringIO)

 {{{
 Unicode results:
 7.600399017333984
 7.397403955459595
 7.361830949783325

 Bytes results:
 8.416419982910156
 7.377918004989624
 7.391348123550415
 }}}


 11739-3.diff (Wrapped cStringIO)

 {{{
 Unicode results:
 14.868388175964355
 14.914705991744995
 14.742434024810791

 Bytes results:
 5.290870904922485
 4.712155818939209
 5.349420070648193
 }}}

-- 
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] r17413 - django/trunk/tests/modeltests/timezones

[noreply]

Author: aaugustin
Date: 2012-01-31 11:47:40 -0800 (Tue, 31 Jan 2012)
New Revision: 17413

Modified:
   django/trunk/tests/modeltests/timezones/tests.py
Log:
Skipped the test introduced at r17403 on Python 2.5, because it requires 
warnings.catch_warnings.


Modified: django/trunk/tests/modeltests/timezones/tests.py
===
--- django/trunk/tests/modeltests/timezones/tests.py2012-01-31 19:23:09 UTC 
(rev 17412)
+++ django/trunk/tests/modeltests/timezones/tests.py2012-01-31 19:47:40 UTC 
(rev 17413)
@@ -262,6 +262,7 @@
 self.assertEqual(event.dt, dt.replace(tzinfo=EAT))
 
 @requires_tz_support
+@skipIf(sys.version_info < (2, 6), "this test requires Python >= 2.6")
 def test_datetime_from_date(self):
 dt = datetime.date(2011, 9, 1)
 with warnings.catch_warnings(record=True) as recorded:

-- 
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] #17604: Make use of assertTemplateUsed and assertTemplateNotUsed as ContextManagers

[Django]

#17604: Make use of assertTemplateUsed and assertTemplateNotUsed as 
ContextManagers
-+-
 Reporter:  gregmuellegger   |Owner:
 Type:  New feature  |  gregmuellegger
Component:  Testing framework|   Status:  closed
 Severity:  Normal   |  Version:  1.3
 Keywords:  assertTemplateUsed,  |   Resolution:  fixed
  assertTemplateNotUsed, | Triage Stage:  Accepted
  contextmanager |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by carljm):

 Oops, my bad :-) Thanks for the pointer on getting the patch applied
 properly.

-- 
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] r17412 - in django/trunk: django/test docs/releases docs/topics tests/regressiontests/test_utils tests/regressiontests/test_utils/templates tests/regressiontests/test_utils/templates/temp

[noreply]

Author: carljm
Date: 2012-01-31 11:23:09 -0800 (Tue, 31 Jan 2012)
New Revision: 17412

Added:
   django/trunk/tests/regressiontests/test_utils/templates/
   django/trunk/tests/regressiontests/test_utils/templates/template_used/
   
django/trunk/tests/regressiontests/test_utils/templates/template_used/alternative.html
   
django/trunk/tests/regressiontests/test_utils/templates/template_used/base.html
   
django/trunk/tests/regressiontests/test_utils/templates/template_used/extends.html
   
django/trunk/tests/regressiontests/test_utils/templates/template_used/include.html
Modified:
   django/trunk/django/test/testcases.py
   django/trunk/docs/releases/1.4.txt
   django/trunk/docs/topics/testing.txt
   django/trunk/tests/regressiontests/test_utils/tests.py
Log:
Fixed #17604 - Added context-manager capability to assertTemplateUsed and 
assertTemplateNotUsed. Thanks Greg M?\195?\188llegger.

Modified: django/trunk/django/test/testcases.py
===
--- django/trunk/django/test/testcases.py   2012-01-30 08:27:50 UTC (rev 
17411)
+++ django/trunk/django/test/testcases.py   2012-01-31 19:23:09 UTC (rev 
17412)
@@ -3,6 +3,7 @@
 import os
 import re
 import sys
+from copy import copy
 from functools import wraps
 from urlparse import urlsplit, urlunsplit
 from xml.dom.minidom import parseString, Node
@@ -28,8 +29,10 @@
 from django.http import QueryDict
 from django.test import _doctest as doctest
 from django.test.client import Client
+from django.test.signals import template_rendered
 from django.test.utils import (get_warnings_state, restore_warnings_state,
 override_settings)
+from django.test.utils import ContextList
 from django.utils import simplejson, unittest as ut2
 from django.utils.encoding import smart_str, force_unicode
 from django.views.static import serve
@@ -260,8 +263,53 @@
 )
 
 
+class _AssertTemplateUsedContext(object):
+def __init__(self, test_case, template_name):
+self.test_case = test_case
+self.template_name = template_name
+self.rendered_templates = []
+self.rendered_template_names = []
+self.context = ContextList()
+
+def on_template_render(self, sender, signal, template, context, **kwargs):
+self.rendered_templates.append(template)
+self.rendered_template_names.append(template.name)
+self.context.append(copy(context))
+
+def test(self):
+return self.template_name in self.rendered_template_names
+
+def message(self):
+return u'%s was not rendered.' % self.template_name
+
+def __enter__(self):
+template_rendered.connect(self.on_template_render)
+return self
+
+def __exit__(self, exc_type, exc_value, traceback):
+template_rendered.disconnect(self.on_template_render)
+if exc_type is not None:
+return
+
+if not self.test():
+message = self.message()
+if len(self.rendered_templates) == 0:
+message += u' No template was rendered.'
+else:
+message += u' Following templates were rendered: %s' % (
+', '.join(self.rendered_template_names))
+self.test_case.fail(message)
+
+
+class _AssertTemplateNotUsedContext(_AssertTemplateUsedContext):
+def test(self):
+return self.template_name not in self.rendered_template_names
+
+def message(self):
+return u'%s was rendered.' % self.template_name
+
+
 class SimpleTestCase(ut2.TestCase):
-
 def save_warnings_state(self):
 """
 Saves the state of the warnings module
@@ -612,14 +660,25 @@
 self.fail(msg_prefix + "The form '%s' was not used to render the"
   " response" % form)
 
-def assertTemplateUsed(self, response, template_name, msg_prefix=''):
+def assertTemplateUsed(self, response=None, template_name=None, 
msg_prefix=''):
 """
 Asserts that the template with the provided name was used in rendering
-the response.
+the response. Also useable as context manager.
 """
+if response is None and template_name is None:
+raise TypeError(u'response and/or template_name argument must be 
provided')
+
 if msg_prefix:
 msg_prefix += ": "
 
+# use assertTemplateUsed as context manager
+if not hasattr(response, 'templates') or (response is None and 
template_name):
+if response:
+template_name = response
+response = None
+context = _AssertTemplateUsedContext(self, template_name)
+return context
+
 template_names = [t.name for t in response.templates]
 if not template_names:
 self.fail(msg_prefix + "No templates used to render the response")
@@ -628,14 +687,25 @@
 " the response. Actual template(s) used: %s" %
 (template_name, u', '.join(templa

Re: [Django] #17604: Make use of assertTemplateUsed and assertTemplateNotUsed as ContextManagers

[Django]

#17604: Make use of assertTemplateUsed and assertTemplateNotUsed as 
ContextManagers
-+-
 Reporter:  gregmuellegger   |Owner:
 Type:  New feature  |  gregmuellegger
Component:  Testing framework|   Status:  closed
 Severity:  Normal   |  Version:  1.3
 Keywords:  assertTemplateUsed,  |   Resolution:  fixed
  assertTemplateNotUsed, | Triage Stage:  Accepted
  contextmanager |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by carljm):

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


Comment:

 In [17412]:
 {{{
 #!CommitTicketReference repository="" revision="17412"
 Fixed #17604 - Added context-manager capability to assertTemplateUsed and
 assertTemplateNotUsed. Thanks Greg Müllegger.
 }}}

-- 
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] #17604: Make use of assertTemplateUsed and assertTemplateNotUsed as ContextManagers

[Django]

#17604: Make use of assertTemplateUsed and assertTemplateNotUsed as 
ContextManagers
-+-
 Reporter:  gregmuellegger   |Owner:
 Type:  New feature  |  gregmuellegger
Component:  Testing framework|   Status:  new
 Severity:  Normal   |  Version:  1.3
 Keywords:  assertTemplateUsed,  |   Resolution:
  assertTemplateNotUsed, | Triage Stage:  Accepted
  contextmanager |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by gregmuellegger):

 * needs_better_patch:  1 => 0


Comment:

 Did you applied the patch with "patch -p1 <
 t17604-assertTemplateUsed.2.diff"? I tried so and had the same problem,
 since it doesn't create the two empty files:
 {{{
 tests/regressiontests/test_utils/templates/template_used/base.html
 tests/regressiontests/test_utils/templates/template_used/alternative.html
 }}}

 Use {{{git apply t17604-assertTemplateUsed.2.diff}}} instead or create
 those empty files by hand.
 Sorry, I don't know how to make the patch work otherwise :-(

-- 
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] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
--+
 Reporter:  etianen   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by charettes):

 * cc: charette.s@… (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] #17604: Make use of assertTemplateUsed and assertTemplateNotUsed as ContextManagers

[Django]

#17604: Make use of assertTemplateUsed and assertTemplateNotUsed as 
ContextManagers
-+-
 Reporter:  gregmuellegger   |Owner:
 Type:  New feature  |  gregmuellegger
Component:  Testing framework|   Status:  new
 Severity:  Normal   |  Version:  1.3
 Keywords:  assertTemplateUsed,  |   Resolution:
  assertTemplateNotUsed, | Triage Stage:  Accepted
  contextmanager |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by carljm):

 * needs_better_patch:  0 => 1


Comment:

 I'm seeing three errors and one failure in the tests with the latest
 patch: http://paste.pocoo.org/show/543635/

-- 
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] #17246: title localization

[Django]

#17246: title localization
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  reopened
  Cleanup/optimization   |  Version:  1.3
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  title main.py|  Needs documentation:  0
  base.html  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  1
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by shelldweller):

 The problem described here is string interpolation. In some languages
 simply sticking the verbose name into a template results in grammatically
 incorrect phrase.

 Ramiro's proposal mentioned above does not really address this problem as
 it primarily deals with pluralization.

 While this is a real problem, I'd say it should be marked as "won't fix"
 for 3 reasons:

 1) Language generation is a rather non-trivial problem that is not
 specific to Django.

 2) There is a simple but someone ugly workaround. Translators may choose
 to localize the offending template string in such a way that interpolating
 generic verbose form works for their locale. The resulting phrase often
 looks rather artificial but is at least grammatically correct (e.g.,
 "Select object to change: user" instead of "Select user to change").

 3) The proposed solution is ineffective. Whether we localize this in code
 (`Select %s to change`) or in template (`Select {{ title }} to change`) -
 the result is still the same.

-- 
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] #15339: Please document the behaviour of RelatedManager when the same object is added twice

[Django]

#15339: Please document the behaviour of RelatedManager when the same object is
added twice
---+
 Reporter:  jammon |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.3-beta
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by jammon):

 * status:  new => closed
 * ui_ux:   => 0
 * resolution:   => wontfix
 * easy:   => 0


Comment:

 Sorry, please forget it. It was a linguistic problem on my side. (It's
 just the way sets 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] #23: Add support for ValidationWarning

[Django]

#23: Add support for ValidationWarning
-+
 Reporter:  adrian   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by guettli):

 * cc: hv@… (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] #3591: add support for custom app_label and verbose_name

[Django]

#3591: add support for custom app_label and verbose_name
-+-
 Reporter:  jkocherhans  |Owner:  adrian
 Type:  New feature  |   Status:  reopened
Component:  Core (Other) |  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Fixed on
Has patch:  1|  a branch
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  1
-+-
Changes (by aav):

 * cc: aav (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] #5964: utils: urlunquote

[Django]

#5964: utils: urlunquote
-+-
 Reporter:  Thomas Güttler   |Owner:  aaugustin
  (Home) < > |   Status:  closed
 Type:  New feature  |  Version:  SVN
Component:  Core (Other) |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Well, sorry for the delay...

-- 
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] #5964: utils: urlunquote

[Django]

#5964: utils: urlunquote
-+-
 Reporter:  Thomas Güttler   |Owner:  aaugustin
  (Home) < > |   Status:  closed
 Type:  New feature  |  Version:  SVN
Component:  Core (Other) |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by guettli):

 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] #17617: Middleware Loader swallows useful stacktraces

[Django]

#17617: Middleware Loader swallows useful stacktraces
--+
 Reporter:  davedash  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Core (Other)
 * needs_tests:   => 0
 * version:  1.3 => SVN
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Maybe just letting the !ImportError uncatched? What is the value added by
 the encapsulation in a !ImproperlyConfigured exception?

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