Re: [Django] #22047: Cannot resolve keyword u'group_ptr' into field. Choices are: group, id, name, permissions, user

[Django]

#22047: Cannot resolve keyword u'group_ptr' into field. Choices are: group, id,
name, permissions, user
-+-
 Reporter:  ctcbmw   |Owner:  mondone
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by ctcbmw):

 Thanks for discovering the real issue, I'll ensure there are no field and
 related name clashes,  the error didnt help much in seeing that issue.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.d583a9626e039a9dd22b83c61512b98a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22062: Problem in modwsgi deployment document

[Django]

#22062: Problem in modwsgi deployment document
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 Hello,

 I spent 10 hours trying to figure out why my static files weren't properly
 being pulled into my app, despite following all the instructions on the
 "serving files" part of this page:

 https://docs.djangoproject.com/en/1.6/howto/deployment/wsgi/modwsgi
 /#serving-files

 I finally realized it was because "Allow from all" in your example needed
 to be "Require all granted" as is outlined in the example at the top of
 the page. It was very frustrating trying to work this out, and I strongly
 recommend consistency between the two examples.

 Thanks!

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.383ddc3f6d545e7a58617a8597651070%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21941: document kwargs parameter to url()

[Django]

#21941: document kwargs parameter to url()
--+
 Reporter:  cjerdonek |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:  url,kwargs| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by mkaurkhalsa@…):

 == The url function can be explained as ==

 A convenient way to return the url pattern is url function :

 {{{
 url(regex, view, kwargs=None, name=None, prefix='')
 }}}


 Most of these are optional though. Lets demonstrate the use of all and few
 arguments in here

 {{{
 url(r'^index/$', index_view),
 url(r'^index/$', index_view, name="main-view"),
 url(r'^archive-summary/(\d{4})/$', archive, {'summary': True}, name="arch-
 summary"),
 url(r'^archive-summary/(\d{4})/$', archive, {'summary': True}, name="arch-
 summary" prefix='myapp'),
 }}}

 * The first url function has mandatory arguments where a url pattern
 points to some view named index_view.
 * It’s fairly common to use the same view function in multiple URL
 patterns in your URLconf. In those cases the second url function that is
 Naming URL Pattern([https://docs.djangoproject.com/en/dev/topics/http/urls
 /#naming-url-patterns]) is used.
 * In third url function, kwarg argument is used. url function can take an
 other optional argument which should be a dictionary of extra keyword
 arguments to pass to the view function.(Refer :
 [https://docs.djangoproject.com/en/dev/topics/http/urls/#passing-extra-
 options-to-view-functions] )
 * In the fourth url function prefix argument is used. When you name your
 URL patterns, make sure you use names that are unlikely to clash with any
 other application’s choice of names. If you call your URL pattern comment,
 and another application does the same thing, there’s no guarantee which
 URL will be inserted into your template when you use this name. Putting a
 prefix on your URL names, perhaps derived from the application name, will
 decrease the chances of collision. We recommend something like myapp-
 comment instead of comment.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.bec970313504736951ae17f71fcb4632%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22059: Either this tutorial, or the 1.4.5 release is totally worthless

[Django]

#22059: Either this tutorial, or the 1.4.5 release is totally worthless
-+--
 Reporter:  steve@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Release blocker  |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by anonymous):

 Interesting theory.. but that's all it is.  I'm simply reporting what's
 happened to me in the last two days.  Version 1.4.5, as installed by yum
 on Fedora 18, creates invalid default sites.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/077.e622869b3af00aa88b11691d39ee5609%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22059: Either this tutorial, or the 1.4.5 release is totally worthless

[Django]

#22059: Either this tutorial, or the 1.4.5 release is totally worthless
-+--
 Reporter:  steve@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Release blocker  |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by timo):

 1.4 was released nearly 2 years ago. If the tutorial were completely
 worthless, I don't think you'd be the first to discover it.

 Anyway, this ticket tracker isn't a support channel. You can find ways to
 get help [https://docs.djangoproject.com/en/dev/#getting-help here].

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/077.3cd06139921d630bf39a7216f5154b42%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22002: AppConfig.ready() and tests

[Django]

#22002: AppConfig.ready() and tests
--+
 Reporter:  mjtamlyn  |Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by jonash):

 If it's not terribly difficult to implement then I'd like to advocate the
 "explicit error" way of solving this issue. These kind of things are
 easily overseen and difficult to debug and/or can cause severe damage in
 your database. (People will abuse the `ready()` method for all kinds of
 things you'd never dream about...)

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.42d4303b3f8338bcd5fede150577c412%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22034: Checks for ModelAdmin ForeignKeys fail with GenericInlineModelAdmin

[Django]

#22034: Checks for ModelAdmin ForeignKeys fail with GenericInlineModelAdmin
-+
 Reporter:  jwa  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  checks   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by russellm):

 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 This is a newly added system check, so it's a release blocker.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.ce371ebe9a51f8555e93bab56642d323%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21553: InterfaceError in Postgres

[Django]

#21553: InterfaceError in Postgres
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   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 Connor23):

 The fix proposed in comment ticket:21553#comment:4 works great.

 I was having the exact same issue but ONLY when using persistent
 connections with Postgres.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f2afcd5315885e4fd937b1fde8b1a484%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22061: Increase visibility of translated documentation sets

[Django]

#22061: Increase visibility of translated documentation sets
+
   Reporter:  russellm  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Django Docs has the ability to host translations, and we have a French
 translation hosted. However, this translation is almost invisible unless
 you know it exists.

 A simple fix: include a top level navigation links in the sidebar.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.ef2f8be2e12fd063a8ce0df3b36d5d13%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22059: Either this tutorial, or the 1.4.5 release is totally worthless

[Django]

#22059: Either this tutorial, or the 1.4.5 release is totally worthless
-+--
 Reporter:  steve@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Release blocker  |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by anonymous):

 Nope 1.4 version; 1.4.5 software.

 I have an abundance of kind words for software documentation that helps,
 instead of wastes two days of it's user's time.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/077.6809e5b3f39dd683150e4e1794f9eb8d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22059: Either this tutorial, or the 1.4.5 release is totally worthless

[Django]

#22059: Either this tutorial, or the 1.4.5 release is totally worthless
-+--
 Reporter:  steve@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Release blocker  |   Resolution:  worksforme
 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 timo):

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


Comment:

 Thank-you for the kind words. Perhaps you are not using the version of the
 tutorial that matches the version of Django you are using.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/077.afcff862943f1191902d1dff06685195%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22060: Error with Postgresql persistent connections after DB fail/restart

[Django]

#22060: Error with Postgresql persistent connections after DB fail/restart
-+-
 Reporter:  Connor23 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  persistent,  |  Unreviewed
  connection, psycopg2, postgresql,  |  Needs documentation:  0
  pool, db, database, error, fail|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 Duplicate of #21553 I think.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.f67a039fc1915db476962cadb1a23676%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21553: InterfaceError in Postgres

[Django]

#21553: InterfaceError in Postgres
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   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 timo):

 #22060 was a 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.7d5bb69645c3fcf45165274a07552186%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22060: Error with Postgresql persistent connections after DB fail/restart

[Django]

#22060: Error with Postgresql persistent connections after DB fail/restart
-+-
 Reporter:  Connor23 |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:  1.6
  (models, ORM)  |   Keywords:  persistent, connection,
 Severity:  Normal   |  psycopg2, postgresql, pool, db,
 Triage Stage:  Unreviewed   |  database, error, fail
Easy pickings:  0|  Has patch:  0
 |  UI/UX:  0
-+-
 Hi,

 When using persistent connections with PostgreSQL if the DB fails or is
 restarted Django will return the following error:

 {{{
 2014-02-15 14:33:07 [24868] [ERROR] Error handling request
 Traceback (most recent call last):
   File "/srv/webapps/myapp/local/lib/python2.7/site-
 packages/gunicorn/workers/sync.py", line 131, in handle_request
 respiter = self.wsgi(environ, resp.start_response)
   File "/srv/webapps/myapp/local/lib/python2.7/site-
 packages/django/core/handlers/wsgi.py", line 194, in __call__
 signals.request_started.send(sender=self.__class__)
   File "/srv/webapps/myapp/local/lib/python2.7/site-
 packages/django/dispatch/dispatcher.py", line 185, in send
 response = receiver(signal=self, sender=sender, **named)
   File "/srv/webapps/myapp/local/lib/python2.7/site-
 packages/django/db/__init__.py", line 94, in close_old_connections
 conn.close_if_unusable_or_obsolete()
   File "/srv/webapps/myapp/local/lib/python2.7/site-
 packages/django/db/backends/__init__.py", line 462, in
 close_if_unusable_or_obsolete
 if self.is_usable():
   File "/srv/webapps/myapp/local/lib/python2.7/site-
 packages/django/db/backends/postgresql_psycopg2/base.py", line 192, in
 is_usable
 self.connection.cursor().execute("SELECT 1")
 InterfaceError: connection already closed

 }}}

 Not sure if this is Django related or psycopg2 related.



 Here are few details about my configuration:

 Django==1.6.2
 gunicorn==18.0
 psycopg2==2.5.2


 CONN_MAX_AGE is set to 600

 Is this a bug? Any ideas?

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.55624b5aec5afa449b0325ca99bf96f3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22059: Either this tutorial, or the 1.4.5 release is totally worthless

[Django]

#22059: Either this tutorial, or the 1.4.5 release is totally worthless
-+
 Reporter:  steve@…  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Documentation|Version:  1.4
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Any beginning tutorial that completely fails to work should be expunged or
 changed.  I could not browse to http://127.0.0.1:8000 because the urls.py
 file is completely wrong, or because the tutorial is incorrect.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.a385d1101a136b2a80174cad7d516e9b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 9db427: Fixed bad comparison logic introduced in d97bf2e9c...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9db4271bd11ac23a5a5652bbcdf8fb6d4b997651
  
https://github.com/django/django/commit/9db4271bd11ac23a5a5652bbcdf8fb6d4b997651
  Author: Baptiste Mispelon 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/template/context.py
M tests/template_tests/test_context.py

  Log Message:
  ---
  Fixed bad comparison logic introduced in 
d97bf2e9c8971764690caaf81a0914bc368d6b02.

Refs #21765.

Thanks to kezabelle for the quick report and to onjin
for providing the patch.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ffe37e20f30_b3ed27d3c859ab%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22058: Add `Http405` exception class and `handler405` view (simillar to 404, 403 and 500)

[Django]

#22058: Add `Http405` exception class and `handler405` view (simillar to 404, 
403
and 500)
-+
 Reporter:  debanshuk|  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Core (URLs)  |Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 With class based views it's not straight forward to to raise a `Http404`
 error if the view doesn't support HTTP method (i.e. a 405 error), with
 function based views it was. So, in such cases clients (users) see a blank
 page with 405 response code, but with no message to tell them where to go
 from there. I guess Django should raise and handle `Http405` exception and
 use a default `handler405` view (which of course can be overridden) to
 return response to user in such a case, as it does in case of 404, 403 and
 500 errors.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.e397ab5174ad0a930bdbaf0f5a7db455%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21905: Add check for default=now() on Date/Time/DateTimeFields

[Django]

#21905: Add check for default=now() on Date/Time/DateTimeFields
--+---
 Reporter:  taishi@…  |Owner:  mamun
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  1.7-alpha-1
 Severity:  Normal|   Resolution:
 Keywords:  check | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+---

Comment (by AeroNotix):

 @mamun patch incoming?

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.91932f76b0b4b60b01a2e9a410d55ddc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22057: Importing `reverse_lazy` in settings.py leads to ImportError

[Django]

#22057: Importing `reverse_lazy` in settings.py leads to ImportError
-+
 Reporter:  dfunckt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  master
 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
-+
Changes (by dfunckt):

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


Comment:

 Marking as accepted as discussed with apollo13

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.497e1a28960a4197c5824ed3c6537a8e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22057: Importing `reverse_lazy` in settings.py leads to ImportError

[Django]

#22057: Importing `reverse_lazy` in settings.py leads to ImportError
-+
 Reporter:  dfunckt  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Uncategorized|Version:  master
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Create a new project, add an app with a model and import reverse_lazy in
 settings.py. Running {{{./manage.py sqlall myapp}}} raises ImportError
 with the following traceback:

 {{{
 $ ./manage.py sqlall myapp
 Traceback (most recent call last):
   File "/settings.py", line 2, in 
 from .settings_local import *
   File "/settings_local.py", line 1, in 
 from .settings_base import *
   File "/settings_base.py", line 5, in 
 from django.core.urlresolvers import reverse_lazy
   File "/src/django/django/core/urlresolvers.py", line 15, in
 
 from django.http import Http404
   File "/src/django/django/http/__init__.py", line 4, in
 
 from django.http.response import (HttpResponse, StreamingHttpResponse,
   File "/src/django/django/http/response.py", line 17, in
 
 from django.core.serializers.json import DjangoJSONEncoder
   File "/src/django/django/core/serializers/__init__.py", line
 23, in 
 from django.core.serializers.base import SerializerDoesNotExist
   File "/src/django/django/core/serializers/base.py", line 6,
 in 
 from django.db import models
 ImportError: cannot import name models
 }}}

 Marking as a release blocker as discussed with apollo13 in IRC.

 Cause of this regression is commit:
 
https://github.com/django/django/commit/0242134d32aa99a54442211ed05576b7061866d1

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.53b228c3b08b06588db883a1d43a010d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22056: Empty directories shouldn't be included to test modules

[Django]

#22056: Empty directories shouldn't be included to test modules
-+-
 Reporter:  sebastian.pawlus@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Testing framework|  1.7-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by AeroNotix):

 * type:  Uncategorized => Cleanup/optimization


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.3659bf14e4ec35444815e123797f7f30%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21725: Javascript translations fail with non-BMP characters

[Django]

#21725: Javascript translations fail with non-BMP characters
-+-
 Reporter:  nedbatchelder|Owner:  MattBlack
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.6
  Internationalization   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by nedbatchelder):

 Is this really a full fix?  Why does this function replace BMP characters
 with four-digit \u escapes, but allow non-BMP characters through
 unchanged?  I would have thought that Javascript would need surrogate
 pairs.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.7193596eb7109ca6073ab6c3066390c2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21630: Simplify find_management_module

[Django]

#21630: Simplify find_management_module
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 Is this too much simplification?

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1b36d9e4d1cb383c77588a081dee3db4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] f46ef7: Split line and added indentation for better readab...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f46ef750b9d08ef6081ab57428201028d77adb53
  
https://github.com/django/django/commit/f46ef750b9d08ef6081ab57428201028d77adb53
  Author: Aleksander Budzinski 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/contrib/admin/utils.py

  Log Message:
  ---
  Split line and added indentation for better readability.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ffbf30d6246_6d2511bbd4441327%40hookshot-fe10-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 94b5bc: Fixed #22002 -- Documented avoiding database inter...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 94b5bc361aef2ae2d46a49dbfe32d9271c185800
  
https://github.com/django/django/commit/94b5bc361aef2ae2d46a49dbfe32d9271c185800
  Author: Zbigniew Siciarz 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M AUTHORS
M docs/ref/applications.txt
M docs/topics/testing/overview.txt

  Log Message:
  ---
  Fixed #22002 -- Documented avoiding database interaction in AppConfig.ready().

Thanks Marc Tamlyn for the suggestion.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ffb6ff70445_54ef75d3c49197%40hookshot-fe9-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22002: AppConfig.ready() and tests

[Django]

#22002: AppConfig.ready() and tests
--+
 Reporter:  mjtamlyn  |Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"94b5bc361aef2ae2d46a49dbfe32d9271c185800"]:
 {{{
 #!CommitTicketReference repository=""
 revision="94b5bc361aef2ae2d46a49dbfe32d9271c185800"
 Fixed #22002 -- Documented avoiding database interaction in
 AppConfig.ready().

 Thanks Marc Tamlyn for the suggestion.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.fb024463b1ccb6972a6ed75c053ddfeb%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] cd7f37: Corrected a pair of flake8 violations

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cd7f37b6471dc947f06a40149e6c9789531e50a0
  
https://github.com/django/django/commit/cd7f37b6471dc947f06a40149e6c9789531e50a0
  Author: Alex Gaynor 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/core/urlresolvers.py
M django/views/debug.py

  Log Message:
  ---
  Corrected a pair of flake8 violations


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ffb508e3d72_751713a7d3819635%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #11929: manage.py dumpdata outputs YAML in unhelpful order

[Django]

#11929: manage.py dumpdata outputs YAML in unhelpful order
-+-
 Reporter:  sampablokuper|Owner:  AeroNotix
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.1
Component:  Core |   Resolution:
  (Serialization)| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by timo):

 * has_patch:  0 => 1
 * type:  Bug => Cleanup/optimization
 * needs_tests:  0 => 1


Comment:

 The current [https://github.com/django/django/pull/2296 PR] needs a test.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.a2fce243d6eba304978f6014ab37504b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1c1dff: Fixed #21725 -- Fixed JavaScript quoting encoding.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1c1dffca757b0b6acaf99d893d68847250ab4146
  
https://github.com/django/django/commit/1c1dffca757b0b6acaf99d893d68847250ab4146
  Author: MattBlack85 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/utils/text.py
M tests/utils_tests/test_text.py

  Log Message:
  ---
  Fixed #21725 -- Fixed JavaScript quoting encoding.

Thanks to nedbatchelder for the report.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ffb470bdb1f_75ff11a1d4040fe%40hookshot-fe7-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21725: Javascript translations fail with non-BMP characters

[Django]

#21725: Javascript translations fail with non-BMP characters
-+-
 Reporter:  nedbatchelder|Owner:  MattBlack
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.6
  Internationalization   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"1c1dffca757b0b6acaf99d893d68847250ab4146"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1c1dffca757b0b6acaf99d893d68847250ab4146"
 Fixed #21725 -- Fixed JavaScript quoting encoding.

 Thanks to nedbatchelder for the report.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.babf4123ee458f34481e9df85d073538%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 14366e: [1.6.x] Fixed #22013 -- Documented difference betw...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 14366ed33e4473c8c2f321f224dd62221adc7629
  
https://github.com/django/django/commit/14366ed33e4473c8c2f321f224dd62221adc7629
  Author: Zbigniew Siciarz 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  [1.6.x] Fixed #22013 -- Documented difference between SERVER_EMAIL and 
DEFAULT_FROM_EMAIL.

Backport of 44814e78cc from master


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ffb23d91406_13301271d38983ea%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22013: Explain difference between SERVER_EMAIL and DEFAULT_FROM_EMAIL, and link to one another

[Django]

#22013: Explain difference between SERVER_EMAIL and DEFAULT_FROM_EMAIL, and 
link to
one another
--+
 Reporter:  ellisd23@…|Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"14366ed33e4473c8c2f321f224dd62221adc7629"]:
 {{{
 #!CommitTicketReference repository=""
 revision="14366ed33e4473c8c2f321f224dd62221adc7629"
 [1.6.x] Fixed #22013 -- Documented difference between SERVER_EMAIL and
 DEFAULT_FROM_EMAIL.

 Backport of 44814e78cc from master
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.bf07567eb97fc8d5908f3ce511060756%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22013: Explain difference between SERVER_EMAIL and DEFAULT_FROM_EMAIL, and link to one another

[Django]

#22013: Explain difference between SERVER_EMAIL and DEFAULT_FROM_EMAIL, and 
link to
one another
--+
 Reporter:  ellisd23@…|Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Zbigniew Siciarz ):

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


Comment:

 In [changeset:"44814e78ccd3a54da41c1b77ba3504c648ef4e89"]:
 {{{
 #!CommitTicketReference repository=""
 revision="44814e78ccd3a54da41c1b77ba3504c648ef4e89"
 Fixed #22013 -- Documented difference between SERVER_EMAIL and
 DEFAULT_FROM_EMAIL.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.e81de6a7208df333dd406bd758c0675c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 44814e: Fixed #22013 -- Documented difference between SERV...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 44814e78ccd3a54da41c1b77ba3504c648ef4e89
  
https://github.com/django/django/commit/44814e78ccd3a54da41c1b77ba3504c648ef4e89
  Author: Zbigniew Siciarz 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  Fixed #22013 -- Documented difference between SERVER_EMAIL and 
DEFAULT_FROM_EMAIL.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ffb228dd38a_6f39621d44665f8%40hookshot-fe10-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21725: Javascript translations fail with non-BMP characters

[Django]

#21725: Javascript translations fail with non-BMP characters
-+-
 Reporter:  nedbatchelder|Owner:  MattBlack
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.6
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by MattBlack):

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


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.07dd494d86e75bde29bb18d019f7b8dd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21739: When running tests, the fixture loading process has verbosity = 0 hardcoded

[Django]

#21739: When running tests, the fixture loading process has verbosity = 0 
hardcoded
-+-
 Reporter:  camilo.lopez.a@… |Owner:  Olek
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  test fixture | Triage Stage:  Accepted
  verbosity  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Olek):

 Working (but ugly) solution was moved into:
 https://github.com/django/django/pull/2299

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/082.77999219813ffae6b3f6baf38e15465e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8408: Add a new meta option: don't do count(*) in admin

[Django]

#8408: Add a new meta option: don't do count(*) in admin
---+
 Reporter:  lidaobing  |Owner:  oinopion
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by oinopion):

 I'm working on this feature in my branch here:
 https://github.com/oinopion/django/compare/nocountpagination

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1177e389d31a9ec3f8519635ad2af6c1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22013: Explain difference between SERVER_EMAIL and DEFAULT_FROM_EMAIL, and link to one another

[Django]

#22013: Explain difference between SERVER_EMAIL and DEFAULT_FROM_EMAIL, and 
link to
one another
--+
 Reporter:  ellisd23@…|Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by zsiciarz):

 I clarified the difference between these two. PR here:
 https://github.com/django/django/pull/2298

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.dc57c1646764b8eb35a9f22ee27189e4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21183: Filter block on the right covers information in admin

[Django]

#21183: Filter block on the right covers information in admin
-+-
 Reporter:  Tuttle   |Owner:  viciu
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, filter,   | Triage Stage:  Accepted
  collapse   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  1
Easy pickings:  0|
-+-

Comment (by viciu):

 Selenium tests 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.425343f7380db76af8d6698b8828380c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18745: When passing a tuple to signing.dumps, I get a list back after calling signing.loads

[Django]

#18745: When passing a tuple to signing.dumps, I get a list back after calling
signing.loads
--+-
 Reporter:  lee@… |Owner:  anonymous
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  Version:  1.4
 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):

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


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.f29cf3ea6b0864688258a998306497de%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21939: Deprecate loading ssi/url tags from future

[Django]

#21939: Deprecate loading ssi/url tags from future
--+
 Reporter:  timo  |Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Template system   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by zsiciarz):

 * status:  new => assigned
 * owner:   => zsiciarz


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.d5de4aedb0da3d9e5bd820a3a3f70a63%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21765: Contexts cannot be compared for equality.

[Django]

#21765: Contexts cannot be compared for equality.
-+-
 Reporter:  Keryn Knight |Owner:  onjin
   |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Template system  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Keryn Knight ):

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


Comment:

 Re-opening with permission:
 The fix as committed is not entirely correct, I don't think, as it only
 compares the '''last''' state change of a given context, so comparisons
 can incorrectly return as equal if context states drift and then re-align,
 for example:
 {{{
 >>> import django
 >>> from django.template import Context
 >>> a = Context()
 >>> b = Context()
 >>> a == b
 True
 }}}
 the above is correct; from here on out, the contexts are continuations of
 the above example:
 {{{
 >>> a.update({'a': 1})
 >>> a == b
 False
 }}}
 that's also correct.
 {{{
 >>> a.update({'c': 3})
 >>> b.update({'c': 3})
 >>> a == b
 True
 }}}
 This is where the incorrectness appears. They are ''not equal'', but their
 last push to the stack was, so they're being treated as equal. Based on
 the commit in question (`d97bf2e9c8971764690caaf81a0914bc368d6b02`), the
 change would be going from:
 {{{
 return self.dicts[-1] == other.dicts[-1]
 }}}
 to
 {{{
 return self.dicts == other.dicts
 }}}
 which would at least ensure the rest of the context is taken into account,
 though that fix in itself may not be as correct as it should be -- it is
 '''strict''' in the sense that the entire history of the contexts being
 compared must be aligned, where it should perhaps instead squash the stack
 into one dictionary for both sides and compare ''them'' for equality.

 (Whether or not strictness is a benefit or problem is probably a DDN, and
 like testing equality for context subclasses which differ (or have
 different attrs, for things like `RenderContext`) could probably be
 tracked in separate tickets, though.)

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/095.772c4faffd611fb3e5aca8bfb82e9661%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22013: Explain difference between SERVER_EMAIL and DEFAULT_FROM_EMAIL, and link to one another

[Django]

#22013: Explain difference between SERVER_EMAIL and DEFAULT_FROM_EMAIL, and 
link to
one another
--+
 Reporter:  ellisd23@…|Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by zsiciarz):

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


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.7f84144c1fd9b4cd3dd7c425a1d9c5c6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18418: Debug doesn't catch exception instead complains views does not exist

[Django]

#18418: Debug doesn't catch exception instead complains views does not exist
-+
 Reporter:  yeukhon  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  debug| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by gnosek):

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


Comment:

 It's already fixed by:

 {{{
 commit 367bfaa5226eaae3278989e63f16063d5cc46cd8
 Author: Florian Apolloner 
 Date:   Tue Aug 14 21:12:08 2012 +0200

 Don't swallow AttributeError in core.urlresolvers.get_callable.
 }}}

 which made its way into 1.5

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.2bbd745842a9e8cf5520628d5aafd176%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18418: Debug doesn't catch exception instead complains views does not exist

[Django]

#18418: Debug doesn't catch exception instead complains views does not exist
-+
 Reporter:  yeukhon  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  debug| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by gnosek):

 How can I reproduce it?

 {{{
 # app18418/forms.py
 from django import forms

 class SubmitButtonField(forms.Field):
 pass

 class AForm(forms.Form):
 save_button = forms.SubmitButtonField(required=False)

 # cat app18418/views.py
 import app18418.forms

 def a_view(request):
 form = app18418.forms.AForm()

 # app18418/urls.py
 from django.conf.urls import patterns, include, url
 from django.contrib import admin

 urlpatterns = patterns('',
 url(r'^$', 'app18418.views.a_view', name='home'),
 )
 }}}

 Visiting / properly raises the exception:

 {{{
 AttributeError at /
 'module' object has no attribute 'SubmitButtonField'
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.e7e5da2c586858fe6ef3e9928cc5de41%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 0b6f9f: Improved fix for #18373 -- backward compatibility

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0b6f9f7c6fb3589157c3231f28409c97c5c451ab
  
https://github.com/django/django/commit/0b6f9f7c6fb3589157c3231f28409c97c5c451ab
  Author: Grzegorz Nosek 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/core/urlresolvers.py
M django/views/debug.py
M tests/urlpatterns_reverse/tests.py

  Log Message:
  ---
  Improved fix for #18373 -- backward compatibility

Commit 79558c78 cleaned up the (undocumented) interface of Resolver404
exception, which breaks compatibility with code messing with .args[0]
directly. Revert the cleanup part and simply leave the fix itself.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff9c0279fcd_6e978b7d38718f6%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21939: Deprecate loading ssi/url tags from future

[Django]

#21939: Deprecate loading ssi/url tags from future
--+
 Reporter:  timo  |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by zsiciarz):

 * status:  assigned => new
 * owner:  zsiciarz =>


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.0172015a09c283965a69814245590e55%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21939: Deprecate loading ssi/url tags from future

[Django]

#21939: Deprecate loading ssi/url tags from future
--+
 Reporter:  timo  |Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Template system   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by zsiciarz):

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


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.7581680b023cbb4f8f1f9ddbf27990d8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21742: Unable to prevent creation of a database during test runs

[Django]

#21742: Unable to prevent creation of a database during test runs
---+
 Reporter:  yscumc |Owner:
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  1.5
 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 marcov):

 * status:  assigned => new
 * owner:  marcov =>


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.214f1fe9780b4c87bfc786b2b4fc07e9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22002: AppConfig.ready() and tests

[Django]

#22002: AppConfig.ready() and tests
--+
 Reporter:  mjtamlyn  |Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by zsiciarz):

 I added mjtamlyn's suggestions to AppConfig docs as a warning note.
 Relevant PR: https://github.com/django/django/pull/2294

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.29ad24fa9bff2bbbeee3f58abf861086%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] d01335: Fixed #22047 -- detecting related_name clash with ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d0133504e57589dc8983a20bf488e069bddd772c
  
https://github.com/django/django/commit/d0133504e57589dc8983a20bf488e069bddd772c
  Author: Christopher Medrela 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/db/models/fields/related.py
M tests/invalid_models_tests/test_relative_fields.py

  Log Message:
  ---
  Fixed #22047 -- detecting related_name clash with inheritance

Thanks to mondone for fruitful colaboration.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff94b4464b7_754eb63d3492228%40hookshot-fe7-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22047: Cannot resolve keyword u'group_ptr' into field. Choices are: group, id, name, permissions, user

[Django]

#22047: Cannot resolve keyword u'group_ptr' into field. Choices are: group, id,
name, permissions, user
-+-
 Reporter:  ctcbmw   |Owner:  mondone
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"d0133504e57589dc8983a20bf488e069bddd772c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d0133504e57589dc8983a20bf488e069bddd772c"
 Fixed #22047 -- detecting related_name clash with inheritance

 Thanks to mondone for fruitful colaboration.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.da3c28cf60a54251b5d1f1d04234dc91%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 65b421: Fixed some flake8 errors from recent commits.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 65b421c6613dab85039d5d7b9601528ad9e6038c
  
https://github.com/django/django/commit/65b421c6613dab85039d5d7b9601528ad9e6038c
  Author: Tim Graham 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/contrib/admin/checks.py
M django/core/urlresolvers.py
M django/views/debug.py

  Log Message:
  ---
  Fixed some flake8 errors from recent commits.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff940d2e686_6e978b7d38710e1%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13559: Need a contextprocessor for current site

[Django]

#13559: Need a contextprocessor for current site
---+
 Reporter:  tonnzor|Owner:  chrismedrela
 Type:  New feature|   Status:  assigned
Component:  contrib.sites  |  Version:  master
 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
---+
Changes (by chrismedrela):

 * needs_better_patch:  1 => 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.e60591caa7a11ba0773d113d7ce3e4fb%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 115005: Fixed #21912 -- Improved error message if a view r...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1150053b994a6de665db51a18a07b992bd6714f1
  
https://github.com/django/django/commit/1150053b994a6de665db51a18a07b992bd6714f1
  Author: Aaron France 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/core/handlers/base.py
M tests/middleware_exceptions/tests.py

  Log Message:
  ---
  Fixed #21912 -- Improved error message if a view returns None.

Thanks brycenesbitt for the report.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff935296100_4b1092bd3c376e6%40hookshot-fe8-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21912: Improve error message "The view ___ didn't return an HttpResponse object."

[Django]

#21912: Improve error message "The view ___ didn't return an HttpResponse 
object."
-+-
 Reporter:  brycenesbitt |Owner:  AeroNotix
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Core (Other) |  1.7-alpha-1
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"1150053b994a6de665db51a18a07b992bd6714f1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1150053b994a6de665db51a18a07b992bd6714f1"
 Fixed #21912 -- Improved error message if a view returns None.

 Thanks brycenesbitt for the report.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.43aa9b21b4db86836bb4cf7ef9af4f82%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21765: Contexts cannot be compared for equality.

[Django]

#21765: Contexts cannot be compared for equality.
-+-
 Reporter:  Keryn Knight |Owner:  onjin
   |   Status:  closed
 Type:  New feature  |  Version:  master
Component:  Template system  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"d97bf2e9c8971764690caaf81a0914bc368d6b02"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d97bf2e9c8971764690caaf81a0914bc368d6b02"
 Fixed #21765 -- Added support for comparing Context instances
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/095.191842c5301979f97820843b12c28250%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] d97bf2: Fixed #21765 -- Added support for comparing Contex...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d97bf2e9c8971764690caaf81a0914bc368d6b02
  
https://github.com/django/django/commit/d97bf2e9c8971764690caaf81a0914bc368d6b02
  Author: Marek Wywiał 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/template/context.py
M tests/template_tests/test_context.py
M tests/template_tests/tests.py

  Log Message:
  ---
  Fixed #21765 -- Added support for comparing Context instances


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff92834028a_769cb1fd3c411af%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21884: field lookup docs don't say exact is default behavior

[Django]

#21884: field lookup docs don't say exact is default behavior
--+
 Reporter:  cjerdonek |Owner:  chomik
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by chomik ):

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


Comment:

 In [changeset:"985ae732b2fbb073a7c98ff857f463449345df27"]:
 {{{
 #!CommitTicketReference repository=""
 revision="985ae732b2fbb073a7c98ff857f463449345df27"
 Fixed #21884 -- Mentioned that exact is the defaut QuerySet lookup type

 Thanks to cjerdonek for the suggestion.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.367f5fda1157c23f62c95b1261fdc27f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 985ae7: Fixed #21884 -- Mentioned that exact is the defaut...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 985ae732b2fbb073a7c98ff857f463449345df27
  
https://github.com/django/django/commit/985ae732b2fbb073a7c98ff857f463449345df27
  Author: chomik 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M docs/ref/models/querysets.txt

  Log Message:
  ---
  Fixed #21884 -- Mentioned that exact is the defaut QuerySet lookup type

Thanks to cjerdonek for the suggestion.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff91e3a52d7_491d1183d40391f9%40hookshot-fe11-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22056: Empty directories shouldn't be included to test modules

[Django]

#22056: Empty directories shouldn't be included to test modules
-+-
 Reporter:  sebastian.pawlus@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Testing framework|  Version:
 Severity:  Normal   |  1.7-alpha-1
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:
  Needs tests:  0|  Unreviewed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by timo):

 This may be find. Personally, I use a post-checkout hook:
 {{{
 # Delete .pyc files and empty directories.
 find . -name "*.pyc" -delete
 find . -type d -empty -delete
 }}}
 We could at least document that if there's any drawback to the PR.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.2322e61c8d6816b2dc3e77985c5074ae%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #11929: manage.py dumpdata outputs YAML in unhelpful order

[Django]

#11929: manage.py dumpdata outputs YAML in unhelpful order
-+-
 Reporter:  sampablokuper|Owner:  AeroNotix
 Type:  Bug  |   Status:  assigned
Component:  Core |  Version:  1.1
  (Serialization)|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by AeroNotix):

 * owner:  ladyrassilon => AeroNotix
 * status:  new => assigned


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.3613ef05a7814dc8fc43b29d05bfe4e3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21884: field lookup docs don't say exact is default behavior

[Django]

#21884: field lookup docs don't say exact is default behavior
--+
 Reporter:  cjerdonek |Owner:  chomik
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by chomik):

 Pull request https://github.com/django/django/pull/2293 waiting for review
 and acceptance.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.80775645e5a6ff40464b9c4ab959ad96%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21183: Filter block on the right covers information in admin

[Django]

#21183: Filter block on the right covers information in admin
-+-
 Reporter:  Tuttle   |Owner:  viciu
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, filter,   | Triage Stage:  Accepted
  collapse   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_tests:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 Selenium tests are required for a change like this.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.c1f8b93a4e554f1b17f3a14aa41ff0d3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21183: Filter block on the right covers information in admin

[Django]

#21183: Filter block on the right covers information in admin
-+-
 Reporter:  Tuttle   |Owner:  viciu
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, filter,   | Triage Stage:  Ready for
  collapse   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by oinopion):

 * stage:  Accepted => Ready for checkin


Comment:

 I reviewed the PR and it look good.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.273535f732ae05ec51325f7aafe87c14%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21183: Filter block on the right covers information in admin

[Django]

#21183: Filter block on the right covers information in admin
-+-
 Reporter:  Tuttle   |Owner:  viciu
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, filter,   | Triage Stage:  Accepted
  collapse   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by viciu):

 * keywords:   => admin, filter, collapse
 * has_patch:  0 => 1


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.c522a8347f335148486bb42291cd582e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21183: Filter block on the right covers information in admin

[Django]

#21183: Filter block on the right covers information in admin
---+
 Reporter:  Tuttle |Owner:  viciu
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 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:  1
---+

Comment (by viciu):

 Pull request here: https://github.com/django/django/pull/2290/

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.2ae2bba8f8d225a16709e348bfc2c77d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22056: Empty directories shouldn't be included to test modules

[Django]

#22056: Empty directories shouldn't be included to test modules
-+-
 Reporter:  sebastian.pawlus@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Testing framework|  Version:
 Severity:  Normal   |  1.7-alpha-1
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:
  Needs tests:  0|  Unreviewed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by sebastian.pawlus):

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


Comment:

 Pull request
 https://github.com/django/django/pull/2292

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.f99fe7f40870069a3c8703d604226284%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22056: Empty directories shouldn't be included to test modules

[Django]

#22056: Empty directories shouldn't be included to test modules
+-
 Reporter:  sebastian.pawlus@…  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Testing framework   |Version:  1.7-alpha-1
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+-
 Currently empty directories are included to the tests modules. It's
 incredibly annoying especially when switching branches and git leaves
 empty directories.

 To reproduce just create an empty directory inside django/tests/

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.02ad32f97130db2b4674e746295cc360%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18373: Thoroughly misleading error page when resolve() fails on a different URL

[Django]

#18373: Thoroughly misleading error page when resolve() fails on a different URL
--+
 Reporter:  anonymous |Owner:  gnosek
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (URLs)   |  Version:  1.3
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Honza Král ):

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


Comment:

 In [changeset:"79558c787ebfd0fe723acb061a375b19a27f18cd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="79558c787ebfd0fe723acb061a375b19a27f18cd"
 Fixed #18373 - improved handling of Resolver404s from views

 When django.core.urlresolvers.resolve was called from a view, failed
 and the exception was propagated and rendered by technical_404_response,
 the URL mentioned on the page was the current URL instead of the URL
 passed to resolve().

 Fixed by using the path attribute from the Resolver404 exception instead
 of request.path_info. Also cleaned up the exceptions to use standard
 named parameters instead of stuffing a dict in args[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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.456fd574df88b5ce85f3e7ed7b721219%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 79558c: Fixed #18373 - improved handling of Resolver404s f...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 79558c787ebfd0fe723acb061a375b19a27f18cd
  
https://github.com/django/django/commit/79558c787ebfd0fe723acb061a375b19a27f18cd
  Author: Grzegorz Nosek 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/core/urlresolvers.py
M django/views/debug.py
M tests/urlpatterns_reverse/tests.py
M tests/view_tests/tests/test_debug.py
M tests/view_tests/views.py

  Log Message:
  ---
  Fixed #18373 - improved handling of Resolver404s from views

When django.core.urlresolvers.resolve was called from a view, failed
and the exception was propagated and rendered by technical_404_response,
the URL mentioned on the page was the current URL instead of the URL
passed to resolve().

Fixed by using the path attribute from the Resolver404 exception instead
of request.path_info. Also cleaned up the exceptions to use standard
named parameters instead of stuffing a dict in args[0]


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff8170a72a8_7c50e7fd38139e9%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21884: field lookup docs don't say exact is default behavior

[Django]

#21884: field lookup docs don't say exact is default behavior
--+
 Reporter:  cjerdonek |Owner:  chomik
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by chomik):

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


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.8bb71b408fe0bdefcd004e209191%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21912: Improve error message "The view ___ didn't return an HttpResponse object."

[Django]

#21912: Improve error message "The view ___ didn't return an HttpResponse 
object."
-+-
 Reporter:  brycenesbitt |Owner:  AeroNotix
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Core (Other) |  1.7-alpha-1
 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 AeroNotix):

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


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.f8df735a767d8aabfc5b5967bf81c7b0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 8bbdcc: Fixed #19299 -- Fixed Nullification of Foreign Key...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8bbdcc76e4a84cde92b8dbfd01581d098bd2187d
  
https://github.com/django/django/commit/8bbdcc76e4a84cde92b8dbfd01581d098bd2187d
  Author: Albert Wang 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M AUTHORS
M django/db/models/fields/related.py
M django/db/models/query.py
M tests/model_fields/models.py
M tests/model_fields/tests.py

  Log Message:
  ---
  Fixed #19299 -- Fixed Nullification of Foreign Keys To CharFields

Thanks tunixman for the report and Baptiste Mispelon and
Shai Berger for reviews.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff7e0cb35f4_3daaabd38437a5%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19299: Foreign keys using to_field and having legitimate empty string values fail with NULL errors

[Django]

#19299: Foreign keys using to_field and having legitimate empty string values 
fail
with NULL errors
-+-
 Reporter:  evan@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"8bbdcc76e4a84cde92b8dbfd01581d098bd2187d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8bbdcc76e4a84cde92b8dbfd01581d098bd2187d"
 Fixed #19299 -- Fixed Nullification of Foreign Keys To CharFields

 Thanks tunixman for the report and Baptiste Mispelon and
 Shai Berger for reviews.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.78615e3078fe71c68a14da3ef3672651%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22047: Cannot resolve keyword u'group_ptr' into field. Choices are: group, id, name, permissions, user

[Django]

#22047: Cannot resolve keyword u'group_ptr' into field. Choices are: group, id,
name, permissions, user
-+-
 Reporter:  ctcbmw   |Owner:  mondone
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mondone):

 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.99c8ec41ce9cb0c9f0b4b46b6978d195%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22055: 404 page does not display stack trace when Resolver404 is raised from a view

[Django]

#22055: 404 page does not display stack trace when Resolver404 is raised from a
view
---+--
 Reporter:  gnosek |Owner:  gnosek
 Type:  Uncategorized  |   Status:  new
Component:  Core (URLs)|  Version:  1.6
 Severity:  Normal |   Resolution:
 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 gnosek):

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


Comment:

 See #18373 for the use case.

 If you're calling resolve('/some-url') that fails, you're not raising an
 Http404 explicitly. It's just a function call that fails, just like the
 ORM or whatever.

 I agree that manually raised Http404s should not trigger the stack trace
 and this ticket is not about it. It's just about treating exceptions from
 resolve() failure just like every other exception.

 IMO, the right thing to do is:
   * Failing to resolve an URL from Django core -> no stack trace
   * Raising Http404 from a view -> no stack trace
   * Failing to resolve an URL from a view -> stack trace (and arguably 500
 response code but there's backwards compatibility to worry about)

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.6384209efa8b1a1a14b193e449344849%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22047: Cannot resolve keyword u'group_ptr' into field. Choices are: group, id, name, permissions, user

[Django]

#22047: Cannot resolve keyword u'group_ptr' into field. Choices are: group, id,
name, permissions, user
-+-
 Reporter:  ctcbmw   |Owner:  mondone
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 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|
-+-
Changes (by chrismedrela):

 * status:  closed => new
 * has_patch:  0 => 1
 * resolution:  invalid =>
 * stage:  Unreviewed => Accepted


Comment:

 @AeroNotix, you're right, but the clash should be detected by system check
 framework. I and mondone have written a patch:
 https://github.com/django/django/pull/2289.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.2dfd477c59cbf6fcfd52d96d1c5ec371%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21936: Add delete message mixin

[Django]

#21936: Add delete message mixin
+--
 Reporter:  david.fischer.ch@…  |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  contrib.messages|  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  mixin   | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by AeroNotix):

 * needs_better_patch:   => 0
 * needs_tests:   => 1
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.68e9ddb5f83395fbc934d53cccfa29a2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21949: Django doesn't log much at high verbosity levels

[Django]

#21949: Django doesn't log much at high verbosity levels
---+--
 Reporter:  gcc|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  logging| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by AeroNotix):

 * keywords:   => logging


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.42d533872c6ba76c83dea9c9befefdb7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22047: Cannot resolve keyword u'group_ptr' into field. Choices are: group, id, name, permissions, user

[Django]

#22047: Cannot resolve keyword u'group_ptr' into field. Choices are: group, id,
name, permissions, user
-+-
 Reporter:  ctcbmw   |Owner:  mondone
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   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 AeroNotix):

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


Comment:

 https://docs.djangoproject.com/en/dev/topics/db/models/#fields mentions
 that one should not create fields which clash with the API. You create a
 field which clashes with the API. Ergo, it doesn't 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.7d0a58b418f70b5776b8c8a552c643b7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21671: model_inheritance_same_model_name tests fail in isolation

[Django]

#21671: model_inheritance_same_model_name tests fail in isolation
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 Would it be acceptable that those tests are skipped when
 `model_inheritance` app is not tested/installed (as of attached patch)?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.c9caaf8dd18898e958131f756adb8772%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22055: 404 page does not display stack trace when Resolver404 is raised from a view

[Django]

#22055: 404 page does not display stack trace when Resolver404 is raised from a
view
---+--
 Reporter:  gnosek |Owner:  gnosek
 Type:  Uncategorized  |   Status:  closed
Component:  Core (URLs)|  Version:  1.6
 Severity:  Normal |   Resolution:  wontfix
 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 AeroNotix):

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


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.ecce0bc00ba0d336233113276027e922%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22055: 404 page does not display stack trace when Resolver404 is raised from a view

[Django]

#22055: 404 page does not display stack trace when Resolver404 is raised from a
view
---+--
 Reporter:  gnosek |Owner:  gnosek
 Type:  Uncategorized  |   Status:  assigned
Component:  Core (URLs)|  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by AeroNotix):

 Hi,

 What kind of useful information could you gain from a 404 page with a
 stacktrace? If you're explicitly creating a 404 exception then you want
 that to happen.

 Could you convince this list of the usefulness in changing this behaviour,
 please?

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.8cadccd8576c5561102ed9318109e3e3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 4d4e0e: Fixed two typos.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4d4e0ea461e381b437c3e585b19f2f6e24e2f645
  
https://github.com/django/django/commit/4d4e0ea461e381b437c3e585b19f2f6e24e2f645
  Author: Rodolfo Carvalho 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/apps/config.py
M django/core/checks/compatibility/django_1_6_0.py

  Log Message:
  ---
  Fixed two typos.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff76d8ab256_7711cc5d442751d%40hookshot-fe7-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] fd4d8f: Fixed typo in comment.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fd4d8f0f520021186681dd0a0d413ed83f4d10f9
  
https://github.com/django/django/commit/fd4d8f0f520021186681dd0a0d413ed83f4d10f9
  Author: Rodolfo Carvalho 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/contrib/gis/tests/distapp/tests.py

  Log Message:
  ---
  Fixed typo in comment.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff7691cf652_d53d85d381139%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22055: 404 page does not display stack trace when Resolver404 is raised from a view

[Django]

#22055: 404 page does not display stack trace when Resolver404 is raised from a
view
---+--
 Reporter:  gnosek |Owner:  gnosek
 Type:  Uncategorized  |   Status:  assigned
Component:  Core (URLs)|  Version:  1.6
 Severity:  Normal |   Resolution:
 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 gnosek):

 * owner:  nobody => gnosek
 * needs_docs:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_better_patch:   => 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.811ec2bca77dec4faf87b4cc777f6d4c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22055: 404 page does not display stack trace when Resolver404 is raised from a view

[Django]

#22055: 404 page does not display stack trace when Resolver404 is raised from a
view
---+
 Reporter:  gnosek |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Core (URLs)|Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Related to #18373, the 404 error page served when
 django.core.urlresolvers.resolve() fails does not contain the exception
 stack trace, which makes finding the failing call unnecessarily difficult.

 When the resolve() call fails in a view, the error should actually be 500
 (it's not the user's fault), but for backwards compatibility the response
 code will have to remain 404 (as discussed with Honza Kral last year).

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.b63dd0d2a40c848fb0d332a88da9180a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22018: Checks error on ModelAdmins with multiple fields in one line using lists

[Django]

#22018: Checks error on ModelAdmins with multiple fields in one line using lists
---+
 Reporter:  jwa|Owner:  jwa
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  checks | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"23b781cc3d17f12c5158f781b2c8cd9d47550c20"]:
 {{{
 #!CommitTicketReference repository=""
 revision="23b781cc3d17f12c5158f781b2c8cd9d47550c20"
 Fixed #22018 -- Fixed checks for ModelAdmin.fields not handling sub-lists.

 Flatten a level of sublists before checking for duplicate fields.

 When given sublists such as:

 ```python

 class FooAdmin(admin.ModelAdmin):
 fields = ('one', ('one', 'two'))
 ```

 The previous code did not correctly detect the duplicated 'one' field.

 Thanks to jwa for the report.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.c9c58afc52b05324ce1a1278aae9fbb1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 23b781: Fixed #22018 -- Fixed checks for ModelAdmin.fields...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 23b781cc3d17f12c5158f781b2c8cd9d47550c20
  
https://github.com/django/django/commit/23b781cc3d17f12c5158f781b2c8cd9d47550c20
  Author: Aaron France 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/contrib/admin/checks.py
M django/contrib/admin/utils.py
M tests/admin_checks/tests.py
M tests/admin_util/tests.py

  Log Message:
  ---
  Fixed #22018 -- Fixed checks for ModelAdmin.fields not handling sub-lists.

Flatten a level of sublists before checking for duplicate fields.

When given sublists such as:

```python

class FooAdmin(admin.ModelAdmin):
fields = ('one', ('one', 'two'))
```

The previous code did not correctly detect the duplicated 'one' field.

Thanks to jwa for the report.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff73faed5b0_717510e3d4016950%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18373: Thoroughly misleading error page when resolve() fails on a different URL

[Django]

#18373: Thoroughly misleading error page when resolve() fails on a different URL
--+
 Reporter:  anonymous |Owner:  gnosek
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (URLs)   |  Version:  1.3
 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
--+
Changes (by gnosek):

 * needs_better_patch:  1 => 0


Comment:

 Updated patch:

 https://github.com/django/django/pull/2287

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.5f87f6fdaa9bf2c4754af2b7b24f2db9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22002: AppConfig.ready() and tests

[Django]

#22002: AppConfig.ready() and tests
--+
 Reporter:  mjtamlyn  |Owner:  zsiciarz
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by zsiciarz):

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


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.68e38801880d079b2a8b63986f448e90%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21742: Unable to prevent creation of a database during test runs

[Django]

#21742: Unable to prevent creation of a database during test runs
---+
 Reporter:  yscumc |Owner:  marcov
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  1.5
 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 marcov):

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


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.72971b7f78ea71e2349d000e9c63859d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21840: LazyObject wrapped instances can no longer be coerced to Bool due to #20924

[Django]

#21840: LazyObject wrapped instances can no longer be coerced to Bool due to 
#20924
--+-
 Reporter:  gabejackson   |Owner:  bmispelon
 Type:  Bug   |   Status:  assigned
Component:  Utilities |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:  LazyObject utils  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by bmispelon):

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


Comment:

 The current PR is broken (which makes me glad I decided to hold off and
 write some tests) since not all dunder methods can be moved as-is (`repr`
 being one of them for example).

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.5fe2462b4bf9a4b7b179014448d0b495%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 2ebcce: Fixed typo in test docstring.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2ebccebf0609229317c2f5b9a76664dc216f27eb
  
https://github.com/django/django/commit/2ebccebf0609229317c2f5b9a76664dc216f27eb
  Author: Rodolfo Carvalho 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/contrib/gis/gdal/tests/test_ds.py

  Log Message:
  ---
  Fixed typo in test docstring.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff697fe7b3d_2e61081d34402d%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 825143: Moved relative URL handling added in refs #21177 t...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8251438cb8c1d47779e9fc33cfa84dad9851a774
  
https://github.com/django/django/commit/8251438cb8c1d47779e9fc33cfa84dad9851a774
  Author: Tim Graham 
  Date:   2014-02-15 (Sat, 15 Feb 2014)

  Changed paths:
M django/core/urlresolvers.py
M django/shortcuts.py

  Log Message:
  ---
  Moved relative URL handling added in refs #21177 to a better place.

Thanks apollo13: "reverse() shouldn't know about absolute/relative paths."


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52ff6404c4706_5f2adcdd4078439%40hookshot-fe12-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21177: redirect() doesn't support redirecting to relative urls

[Django]

#21177: redirect() doesn't support redirecting to relative urls
-+-
 Reporter:  acatton@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  redirect url | Triage Stage:  Accepted
  relative   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"8251438cb8c1d47779e9fc33cfa84dad9851a774"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8251438cb8c1d47779e9fc33cfa84dad9851a774"
 Moved relative URL handling added in refs #21177 to a better place.

 Thanks apollo13: "reverse() shouldn't know about absolute/relative paths."
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/079.be2af4d6651d348110db599636ff9ec0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22050: defer('related__subfield') and select_related() on proxy model raises error

[Django]

#22050: defer('related__subfield') and select_related() on proxy model raises 
error
---+--
 Reporter:  lovasb |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  defer,proxy,query  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by lovasb):

 Replying to [comment:2 bmispelon]:
 > Looks like there's one already:
 https://github.com/django/django/pull/2279


 Yeah, that's mine! :)

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.4cc964378ab326b638f82e677adf6dab%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22050: defer('related__subfield') and select_related() on proxy model raises error

[Django]

#22050: defer('related__subfield') and select_related() on proxy model raises 
error
---+--
 Reporter:  lovasb |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  defer,proxy,query  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by lovasb):

 Replying to [comment:1 bmispelon]:
 > Hi,
 >
 > Could you submit a pull request for this, or at least consolidate all
 the patches into one? It would make reviewing the ticket easier.
 >
 > Thanks.


 Hi,

 Here is my pull request: https://github.com/django/django/pull/2279/files

 Bence

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.656dfbcef5071892e698ce72537f1cda%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22050: defer('related__subfield') and select_related() on proxy model raises error

[Django]

#22050: defer('related__subfield') and select_related() on proxy model raises 
error
---+--
 Reporter:  lovasb |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  defer,proxy,query  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by bmispelon):

 Looks like there's one already: https://github.com/django/django/pull/2279

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.3dcdf1dd2f48c8d9875a341687af6f1a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.