Re: [Django] #19172: test_poisoned_http_host* tests failing when having ADMINS settings populated

[Django]

#19172: test_poisoned_http_host* tests failing when having ADMINS settings
populated
-+-
 Reporter:  bernardofontes   |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.4
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  unit tests, auth,| Triage Stage:  Accepted
  admin, mail|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by anonymous):

 I've just downloaded Django 1.3 from the official site and have the same
 problem. While status of this task is "fixed".
 Am I doing smth wrong?

 std output is below:

 ==
 FAIL: test_poisoned_http_host
 (django.contrib.auth.tests.views.PasswordResetTest)
 Poisoned HTTP_HOST headers can't be used for reset emails
 --
 Traceback (most recent call last):
   File "/Library/Python/2.7/site-
 packages/django/contrib/auth/tests/views.py", line 99, in
 test_poisoned_http_host
 self.assertEqual(len(mail.outbox), 0)
 AssertionError: 1 != 0

 ==
 FAIL: test_poisoned_http_host_admin_site
 (django.contrib.auth.tests.views.PasswordResetTest)
 Poisoned HTTP_HOST headers can't be used for reset emails on admin views
 --
 Traceback (most recent call last):
   File "/Library/Python/2.7/site-
 packages/django/contrib/auth/tests/views.py", line 109, in
 test_poisoned_http_host_admin_site
 self.assertEqual(len(mail.outbox), 0)
 AssertionError: 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7145: 'NoneType' object has no attribute 'year' in admin change list when using date_hierarchy with a date field with null values

[Django]

#7145: 'NoneType' object has no attribute 'year' in admin change list when using
date_hierarchy with a date field with null values
-+-
 Reporter:  Eric Walstad |Owner:  nobody
     |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by dfraser@…):

 I had this problem and the cause turned out to be a date of -00-00 and
 thus an exception at

 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/django/contrib/admin/templatetags/admin_list.py in
 date_hierarchy, line 350

 occurred because of the None value at the head of the list of possible
 years.  The relevant column in the table was defined as NOT NULL, so this
 is a MySQL related issue due to its defaults and the complexity resulting
 from them.  Forcing a crash would be good because it makes one clean up
 the data, but a date of -00-00 might be valid in some sense, so
 perhaps the code in admin_list.py should change?

 I decided having a value of "unknown" was more appropriate given how the
 field was used, so I decided not to use the date_hierarchy feature.

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

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

Re: [Django] #18127: Make *all* DeprecationWarnings stacklevel=2 or greater

[Django]

#18127: Make *all* DeprecationWarnings stacklevel=2 or greater
-+-
 Reporter:  MostAwesomeDude@…|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.4
Component:  Uncategorized|   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|
-+-

Comment (by aaugustin):

 The fix for this ticket is included in
 https://github.com/django/django/pull/605.

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

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

Re: [Django] #19520: Docs suggest wrong template_name_suffix

[Django]

#19520: Docs suggest wrong template_name_suffix
---+
 Reporter:  jnns   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  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 timo):

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


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

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

Re: [Django] #10405: quoted class names in foreign key definition causes 'str' object has no attribute '_default_manager'

[Django]

#10405: quoted class names in foreign key definition causes 'str' object has no
attribute '_default_manager'
-+-
 Reporter:  danbrwn  |Owner:  mitsuhiko
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
  foreign,key,quoted,dceu2011|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by ramiro):

 I've just tested this with a setup like comment:42 suggest: The one pasted
 in comment:8. I did it with both trunk as of now and 1.4.2. The
 problematic setup doesn't even allow me to run syncdb. If I change the
 models/modelform ordering to the one that works, run syncdb and then
 change it back to the problematic one the error message introduced with
 the fix for this ticket is shown inmediately when running the dev server.
 The message is always:

 `ValueError: Cannot create form field for 'ref' yet, because its related
 model 'ClassB' has not been loaded yet`

 I tested with DEBUG set both to True and False.

 Guys, you will need to provide much more detail, as in a simple setup that
 demonstrates the purported regression if you want anyone to dedicate any
 more time to this. Also, please open a new ticket for that, commenting on
 a closed ticket isn't a good way to get things going either.

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

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

Re: [Django] #19488: Locale middleware with settings.APPEND_SLASH enabled is buggy (doesn't redirect) with valid URLs not ending with slash

[Django]

#19488: Locale middleware with settings.APPEND_SLASH enabled is buggy (doesn't
redirect) with valid URLs not ending with slash
-+-
 Reporter:  danger@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  redirect, i18n,  | Triage Stage:
  locale middleware  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by danger@…):

 additional note: when you define the url pattern straight in the top-level
 urls.py file (in i18n_patterns), the redirect works fine. The problem
 seems to start when you go through the include() statement.

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

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

Re: [Django] #19488: Locale middleware with settings.APPEND_SLASH enabled is buggy (doesn't redirect) with valid URLs not ending with slash

[Django]

#19488: Locale middleware with settings.APPEND_SLASH enabled is buggy (doesn't
redirect) with valid URLs not ending with slash
-+-
 Reporter:  danger@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  redirect, i18n,  | Triage Stage:
  locale middleware  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by danger@…):

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


Comment:

 I have attached a sample project which demonstrates my problem.

 When you try accessing /index.html I belive it should redirect to
 /en/index.html the same way as it does when you access /ok and you get
 redirected to /en/ok/

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

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

[Django] #19520: Docs suggest wrong template_name_suffix

[Django]

#19520: Docs suggest wrong template_name_suffix
---+
 Reporter:  jnns   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 The [https://docs.djangoproject.com/en/dev/ref/class-based-views/generic-
 editing/ page about generic class based editing views] state that adding a
 template name suffix should end with ".html" whereas this would result in
 django looking for a template ending with ".html.html".


 '''template_name_suffix'''

 The DeleteView page displayed to a GET request uses a template_name_suffix
 of '_confirm_delete.html'. For example, changing this attribute to
 '_check_delete'''.html for a view deleting objects for the the example
 Author model would cause the the default template_name to be
 'myapp/author_check_delete'''.html.

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

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

Re: [Django] #19516: Fix broken sphinx references in docs

[Django]

#19516: Fix broken sphinx references in docs
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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:  0
--+

Comment (by Tim Graham ):

 In [changeset:"1c1df12388e394b7f1dc3949d23b99fa80cf6f6a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1c1df12388e394b7f1dc3949d23b99fa80cf6f6a"
 [1.5.X] Fixed more broken links. refs #19516

 Backport of 9c5a6adf33 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1c1df1: [1.5.X] Fixed more broken links. refs #19516

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 1c1df12388e394b7f1dc3949d23b99fa80cf6f6a
  
https://github.com/django/django/commit/1c1df12388e394b7f1dc3949d23b99fa80cf6f6a
  Author: Tim Graham 
  Date:   2012-12-25 (Tue, 25 Dec 2012)

  Changed paths:
M docs/ref/contrib/gis/gdal.txt
M docs/ref/models/fields.txt
M docs/ref/models/options.txt
M docs/ref/models/querysets.txt
M docs/ref/settings.txt
M docs/releases/1.1-alpha-1.txt
M docs/releases/1.1.txt
M docs/releases/1.3-alpha-1.txt
M docs/releases/1.4.txt

  Log Message:
  ---
  [1.5.X] Fixed more broken links. refs #19516

Backport of 9c5a6adf33 from master



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

Re: [Django] #19516: Fix broken sphinx references in docs

[Django]

#19516: Fix broken sphinx references in docs
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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:  0
--+

Comment (by Tim Graham ):

 In [changeset:"9c5a6adf3341c59efee4ca6d0037f8069185e0e3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9c5a6adf3341c59efee4ca6d0037f8069185e0e3"
 Fixed more broken links. refs #19516
 }}}

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

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

[django/django] 9c5a6a: Fixed more broken links. refs #19516

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9c5a6adf3341c59efee4ca6d0037f8069185e0e3
  
https://github.com/django/django/commit/9c5a6adf3341c59efee4ca6d0037f8069185e0e3
  Author: Tim Graham 
  Date:   2012-12-25 (Tue, 25 Dec 2012)

  Changed paths:
M docs/ref/contrib/gis/gdal.txt
M docs/ref/models/fields.txt
M docs/ref/models/options.txt
M docs/ref/models/querysets.txt
M docs/ref/settings.txt
M docs/releases/1.1-alpha-1.txt
M docs/releases/1.1.txt
M docs/releases/1.3-alpha-1.txt
M docs/releases/1.4.txt

  Log Message:
  ---
  Fixed more broken links. refs #19516



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

Re: [Django] #19519: Django fails to close db connections at end of request-response cycle

[Django]

#19519: Django fails to close db connections at end of request-response cycle
-+-
 Reporter:  amosonn@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  connection,  |  Unreviewed
  managment, closing, mysql, |  Needs documentation:  0
  innodb, signal, generator  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 I remember making some fixes in this area when I introduced explicit
 support for streaming responses. If this is indeed related to streaming
 responses it's most likely fixed in 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.