[Django] #18270: Erroneous sample email template for password reset

[Django]

#18270: Erroneous sample email template for password reset
-+-
 Reporter:   |  Owner:  nobody
  schnippi   | Status:  new
 Type:   |Version:  1.4
  Uncategorized  |   Keywords:  password reset, email template,
Component:   |  sample
  Documentation  |  Has patch:  0
 Severity:  Normal   |  UI/UX:  0
 Triage Stage:   |
  Unreviewed |
Easy pickings:  0|
-+-
 The sample registration/password_reset_email.html email body template at
 [https://docs.djangoproject.com/en/1.4/topics/auth/#module-
 django.contrib.auth.views] is

 {{{
 Someone asked for password reset for email {{ email }}. Follow the link
 below:
 {{ protocol}}://{{ site_name }}{% url 'auth_password_reset_confirm'
 uidb36=uid token=token %}
 }}}

 but it should be

 {{{
 Someone asked for password reset for email {{ email }}. Follow the link
 below:
 {{ protocol }}://{{ domain }}{% url 'auth_password_reset_confirm'
 uidb36=uid token=token %}
 }}}

 Because '''site_name''' is a human readable description of the site and
 not a domain name. So the current example template will get the user to
 something like "http://My Site/accounts/...", which is not the desired
 effect.

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

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

Re: [Django] #4102: Allow UPDATE of only specific fields in model.save()

[Django]

#4102: Allow UPDATE of only specific fields in model.save()
-+-
 Reporter:  Collin Grady |Owner:  cgrady
   |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  update fields sql|  Patch needs improvement:  1
  row table modified |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by niwi):

 Thank you very much! It has helped me a lot to understand how git rebase
 works.

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

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

Re: [Django] #14681: Uploaded files should not set mode to None

[Django]

#14681: Uploaded files should not set mode to None
-+-
 Reporter:  bgreenlee|Owner:  bretth
 Type:  Bug  |   Status:  assigned
Component:  File |  Version:  master
  uploads/storage|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  sprintdec2010|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by moritzs):

 * cc: moritz.sichert@… (added)
 * stage:  Accepted => Ready for checkin


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

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

[Django] #18269: From __future__ import unicode_literals

[Django]

#18269: From __future__ import unicode_literals
+
   Reporter:  claudep   |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Python 3  |Version:  1.3
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 To the road to Python3, a possible next step would be to use the {{{ from
 __future__ import unicode_literals }}} and remove the `u''` prefixes, as
 it is not supported in Python3 (may be added in 3.3 for compatibility
 reasons).

 I made a branch which has strong inspiration from Vinay Sajip Python3
 branch of Django (https://bitbucket.org/vinay.sajip/django): [[BR]]
 https://github.com/claudep/django/tree/unicode_literals

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

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

[django/django] 11a535: Inserted more simplefilter calls to be sure warnin...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 11a5355517487eab56c34d92b45d7d67fde6dbd3
  
https://github.com/django/django/commit/11a5355517487eab56c34d92b45d7d67fde6dbd3
  Author: Claude Paroz 
  Date:   2012-05-03 (Thu, 03 May 2012)

  Changed paths:
M django/contrib/sessions/tests.py
M tests/regressiontests/logging_tests/tests.py
M tests/regressiontests/requests/tests.py
M tests/regressiontests/utils/text.py

  Log Message:
  ---
  Inserted more simplefilter calls to be sure warnings are emitted.

Thanks to Florian Apolloner for suggesting the patch.


diff --git a/django/contrib/sessions/tests.py b/django/contrib/sessions/tests.py
index 6311421..92ea6bb 100644
--- a/django/contrib/sessions/tests.py
+++ b/django/contrib/sessions/tests.py
@@ -352,6 +352,7 @@ class CacheSessionTests(SessionTestsMixin, 
unittest.TestCase):
 
 def test_load_overlong_key(self):
 with warnings.catch_warnings(record=True) as w:
+warnings.simplefilter("always")
 self.session._session_key = (string.ascii_letters + string.digits) 
* 20
 self.assertEqual(self.session.load(), {})
 self.assertEqual(len(w), 1)
diff --git a/tests/regressiontests/logging_tests/tests.py 
b/tests/regressiontests/logging_tests/tests.py
index e4c045b..887897a 100644
--- a/tests/regressiontests/logging_tests/tests.py
+++ b/tests/regressiontests/logging_tests/tests.py
@@ -43,6 +43,7 @@ def test_filter_added(self):
 config = copy.deepcopy(OLD_LOGGING)
 
 with warnings.catch_warnings(record=True) as w:
+warnings.simplefilter("always")
 compat_patch_logging_config(config)
 self.assertEqual(len(w), 1)
 
diff --git a/tests/regressiontests/requests/tests.py 
b/tests/regressiontests/requests/tests.py
index cf4c58b..5c49afb 100644
--- a/tests/regressiontests/requests/tests.py
+++ b/tests/regressiontests/requests/tests.py
@@ -415,6 +415,7 @@ def read(self, len=0):
'wsgi.input': ExplodingStringIO(payload)})
 
 with warnings.catch_warnings(record=True) as w:
+warnings.simplefilter("always")
 with self.assertRaises(UnreadablePostError):
 request.raw_post_data
 self.assertEqual(len(w), 1)
diff --git a/tests/regressiontests/utils/text.py 
b/tests/regressiontests/utils/text.py
index e749ccf..ad65ec8 100644
--- a/tests/regressiontests/utils/text.py
+++ b/tests/regressiontests/utils/text.py
@@ -73,6 +73,7 @@ def test_truncate_html_words(self):
 
 def test_old_truncate_words(self):
 with warnings.catch_warnings(record=True) as w:
+warnings.simplefilter("always")
 self.assertEqual(u'The quick brown fox jumped over the lazy dog.',
 text.truncate_words(u'The quick brown fox jumped over the lazy 
dog.', 10))
 self.assertEqual(u'The quick brown fox ...',
@@ -83,6 +84,7 @@ def test_old_truncate_words(self):
 
 def test_old_truncate_html_words(self):
 with warnings.catch_warnings(record=True) as w:
+warnings.simplefilter("always")
 self.assertEqual(u'The quick brown fox jumped over 
the lazy dog.',
 text.truncate_html_words('The quick brown fox 
jumped over the lazy dog.', 10))
 self.assertEqual(u'The quick brown fox 
...',




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

Re: [Django] #18268: no branches in new git repository?!?!

[Django]

#18268: no branches in new git repository?!?!
---+--
 Reporter:  jedie  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  invalid
 Keywords:  git| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 Thanks for the report. Porting the branches is a work in progress, and
 there isn't much the community can do to help, so it doesn't need a ticket
 in Trac.

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

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

[Django] #18268: no branches in new git repository?!?!

[Django]

#18268: no branches in new git repository?!?!
---+
 Reporter:  jedie  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  master
 Severity:  Normal |   Keywords:  git
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The old branches like 1.3.X, 1.4.X does only exist in
 https://github.com/django/django-old/ why not in the new
 https://github.com/django/django/ ?

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

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

Re: [Django] #18267: Clarify how to check if configuration is already called

[Django]

#18267: Clarify how to check if configuration is already called
---+--
 Reporter:  techtonik  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by techtonik):

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


Comment:

 Pull request - https://github.com/django/django/pull/43

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

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

[Django] #18267: Clarify how to check if configuration is already called

[Django]

#18267: Clarify how to check if configuration is already called
---+
 Reporter:  techtonik  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.2
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 [https://docs.djangoproject.com/en/dev/topics/settings/#either-configure-
 or-django-settings-module-is-required It is said] that `it's an error to
 call configure() more than once`, but no info how to check if settings
 were already configured.

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

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

Re: [Django] #17787: Clear setting-dependant caches when settings are overridden (in tests)

[Django]

#17787: Clear setting-dependant caches when settings are overridden (in tests)
---+--
 Reporter:  aaugustin  |Owner:  aaugustin
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4-beta-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 aaugustin):

 * owner:  nobody => aaugustin
 * status:  reopened => new


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

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

Re: [Django] #17787: Clear setting-dependant caches when settings are overridden (in tests)

[Django]

#17787: Clear setting-dependant caches when settings are overridden (in tests)
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Testing framework  |  Version:  1.4-beta-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 aaugustin):

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


Comment:

 I'd like to review a few more settings :)

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

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

[Django] #18266: Allow context processors to take the context as a second argument

[Django]

#18266: Allow context processors to take the context as a second argument
-+
 Reporter:  fberger  |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Template system  |Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 It would be very useful if context processors could do what their name
 suggests and process the existing context and manipulate it instead of
 just adding and potentially overriding some existing entries in the
 context.

 This would be useful for context processors that take entries contained in
 the context and compute an extra bit of information. If the entry is not
 there it wouldn't waste any time computing it for a view that doesn't need
 it and avoid extra db queries to get the data.

 No guarantee would be given as to the order in which processors run, they
 could only rely on context data provided by views.

 A workaround to achieve the same effect would be to set the context as
 field in the request.

 I've attached a basic patch that allows context processors to optionally
 take a context argument.

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

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

[django/django] 00c0d3: Made warning assertions work with or without -Wall...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 00c0d3c44ebc4e3461653ec96cd47023cc0a6e5b
  
https://github.com/django/django/commit/00c0d3c44ebc4e3461653ec96cd47023cc0a6e5b
  Author: Claude Paroz 
  Date:   2012-05-03 (Thu, 03 May 2012)

  Changed paths:
M django/contrib/sessions/tests.py
M tests/regressiontests/cache/tests.py
M tests/regressiontests/decorators/tests.py
M tests/regressiontests/requests/tests.py
M tests/regressiontests/utils/text.py

  Log Message:
  ---
  Made warning assertions work with or without -Wall python switch


diff --git a/django/contrib/sessions/tests.py b/django/contrib/sessions/tests.py
index f31c056..6311421 100644
--- a/django/contrib/sessions/tests.py
+++ b/django/contrib/sessions/tests.py
@@ -302,6 +302,7 @@ def test_exists_searches_cache_first(self):
 
 def test_load_overlong_key(self):
 with warnings.catch_warnings(record=True) as w:
+warnings.simplefilter("always")
 self.session._session_key = (string.ascii_letters + string.digits) 
* 20
 self.assertEqual(self.session.load(), {})
 self.assertEqual(len(w), 1)
diff --git a/tests/regressiontests/cache/tests.py 
b/tests/regressiontests/cache/tests.py
index f0e2977..780718b 100644
--- a/tests/regressiontests/cache/tests.py
+++ b/tests/regressiontests/cache/tests.py
@@ -469,11 +469,13 @@ def func(key, *args):
 
 try:
 with warnings.catch_warnings(record=True) as w:
+warnings.simplefilter("always")
 # memcached does not allow whitespace or control characters in 
keys
 self.cache.set('key with spaces', 'value')
 self.assertEqual(len(w), 2)
 self.assertTrue(isinstance(w[0].message, CacheKeyWarning))
 with warnings.catch_warnings(record=True) as w:
+warnings.simplefilter("always")
 # memcached limits key length to 250
 self.cache.set('a' * 251, 'value')
 self.assertEqual(len(w), 1)
diff --git a/tests/regressiontests/decorators/tests.py 
b/tests/regressiontests/decorators/tests.py
index 9755022..0c5b2e9 100644
--- a/tests/regressiontests/decorators/tests.py
+++ b/tests/regressiontests/decorators/tests.py
@@ -122,7 +122,7 @@ def test_cache_page_old_style(self):
 """
 def my_view(request):
 return "response"
-with warnings.catch_warnings(record=True) as w:
+with warnings.catch_warnings(record=True):
 my_view_cached = cache_page(my_view, 123)
 self.assertEqual(my_view_cached(HttpRequest()), "response")
 my_view_cached2 = cache_page(my_view, 123, key_prefix="test")
@@ -131,7 +131,6 @@ def my_view(request):
 self.assertEqual(my_view_cached3(HttpRequest()), "response")
 my_view_cached4 = cache_page()(my_view)
 self.assertEqual(my_view_cached4(HttpRequest()), "response")
-self.assertEqual(len(w), 4)
 
 def test_require_safe_accepts_only_safe_methods(self):
 """
diff --git a/tests/regressiontests/requests/tests.py 
b/tests/regressiontests/requests/tests.py
index d1c0896..cf4c58b 100644
--- a/tests/regressiontests/requests/tests.py
+++ b/tests/regressiontests/requests/tests.py
@@ -397,9 +397,8 @@ def test_raw_post_data_returns_body(self):
 'wsgi.input': StringIO(payload)
 })
 
-with warnings.catch_warnings(record=True) as w:
+with warnings.catch_warnings(record=True):
 self.assertEqual(request.body, request.raw_post_data)
-self.assertEqual(len(w), 1)
 
 def test_POST_connection_error(self):
 """
diff --git a/tests/regressiontests/utils/text.py 
b/tests/regressiontests/utils/text.py
index 6457845..e749ccf 100644
--- a/tests/regressiontests/utils/text.py
+++ b/tests/regressiontests/utils/text.py
@@ -79,7 +79,7 @@ def test_old_truncate_words(self):
 text.truncate_words('The quick brown fox jumped over the lazy 
dog.', 4))
 self.assertEqual(u'The quick brown fox ',
 text.truncate_words('The quick brown fox jumped over the lazy 
dog.', 4, ''))
-self.assertEqual(len(w), 3)
+self.assertGreater(len(w), 0)
 
 def test_old_truncate_html_words(self):
 with warnings.catch_warnings(record=True) as w:
@@ -91,7 +91,7 @@ def test_old_truncate_html_words(self):
 text.truncate_html_words('The quick brown fox 
jumped over the lazy dog.', 4, ''))
 self.assertEqual(u'The quick brown 
fox',
 text.truncate_html_words('The quick brown fox 
jumped over the lazy dog.', 4, None))
-self.assertEqual(len(w), 4)
+self.assertGreater(len(w), 0)
 
 def test_wrap(self):
 digits = '1234 67 9'




-- 
You received this 

Re: [Django] #18261: Clarify the term "project root directory"

[Django]

#18261: Clarify the term "project root directory"
-+-
 Reporter:  schnippi |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  project root, root   | Triage Stage:  Accepted
  directory, translation,|  Needs documentation:  0
  makemessages, compilemessages  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by carljm):

 I'm not familiar enough with the i18n toolchain to be sure where
 compilemessages/makemessages should be run, or why it would work in one
 place but not another, but we should _not_ document that `mysite/mysite`
 is the "project root directory". The latter is a confusing term that we
 should maybe just avoid using; if it should have any meaning, it should
 mean "the directory with `manage.py`", which would be just `mysite/`. The
 inner directory is the "project module", the outer directory could be
 called the "workspace" or "container" or "project root".

 In general, we want people running most command-line stuff in the
 workspace directory (the one with manage.py), because that will set up
 sys.path correctly for all their imports to work. This may not apply to
 compilemessages/makemessages 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16941: naturaltime documentation is misleading

[Django]

#16941: naturaltime documentation is misleading
---+--
 Reporter:  jaap3  |Owner:  antoviaque
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by H0ff1):

 * needs_docs:  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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17049: The test suite should be deprecation-warning clean

[Django]

#17049: The test suite should be deprecation-warning clean
--+
 Reporter:  carljm|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Testing framework |  Version:  master
 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
--+

Comment (by akaariai):

 FWIW all tests pass on Oracle 11g with no warnings.

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

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

Re: [Django] #16884: Add message level argument to ModelAdmin's message_user

[Django]

#16884: Add message level argument to ModelAdmin's message_user
---+
 Reporter:  shelldweller   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+
Changes (by H0ff1):

 * cc: H0ff1 (added)


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

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

Re: [Django] #16884: Add message level argument to ModelAdmin's message_user

[Django]

#16884: Add message level argument to ModelAdmin's message_user
---+
 Reporter:  shelldweller   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+
Changes (by H0ff1):

 * needs_docs:  1 => 0


Comment:

 attached documentation-patch

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

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

Re: [Django] #11331: Memcached backend closes connection after every request

[Django]

#11331: Memcached backend closes connection after every request
-+-
 Reporter:  booink@… |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.0
Component:  Core (Cache system)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

 * cc: trbs@… (added)


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

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

Re: [Django] #17049: The test suite should be deprecation-warning clean

[Django]

#17049: The test suite should be deprecation-warning clean
--+
 Reporter:  carljm|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Testing framework |  Version:  master
 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
--+

Comment (by claudep):

 Oh, and forgot to mention that Aymeric has added -Wall to
 http://ci.djangoproject.com test suites, so we can check in console output
 for uncatched warnings.

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

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

Re: [Django] #17787: Clear setting-dependant caches when settings are overridden (in tests)

[Django]

#17787: Clear setting-dependant caches when settings are overridden (in tests)
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.4-beta-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 claudep):

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


Comment:

 Several settings are now using the setting_changed signal. I don't think
 it's useful to get this one open.

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

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

Re: [Django] #17049: The test suite should be deprecation-warning clean

[Django]

#17049: The test suite should be deprecation-warning clean
--+
 Reporter:  carljm|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Testing framework |  Version:  master
 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 claudep):

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


Comment:

 Patch committed in 10cf3c64273db407402ea9723569dfc8d059e186

 I think the only remaining warnings/errors are related to gis tests, and
 there are exiting tickets for those: #17958 and #17959. So closing this
 one.

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

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

[django/django] 10cf3c: Used catch_warnings instead of save/restore method...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 10cf3c64273db407402ea9723569dfc8d059e186
  
https://github.com/django/django/commit/10cf3c64273db407402ea9723569dfc8d059e186
  Author: Claude Paroz 
  Date:   2012-05-03 (Thu, 03 May 2012)

  Changed paths:
M django/contrib/formtools/tests/__init__.py
M django/contrib/sessions/tests.py
M tests/regressiontests/cache/tests.py
M tests/regressiontests/decorators/tests.py
M tests/regressiontests/forms/tests/fields.py
M tests/regressiontests/generic_views/dates.py
M tests/regressiontests/i18n/patterns/tests.py
M tests/regressiontests/logging_tests/tests.py
M tests/regressiontests/requests/tests.py
M tests/regressiontests/staticfiles_tests/tests.py
M tests/regressiontests/test_client_regress/views.py
M tests/regressiontests/utils/text.py

  Log Message:
  ---
  Used catch_warnings instead of save/restore methods. Refs #17049.


diff --git a/django/contrib/formtools/tests/__init__.py 
b/django/contrib/formtools/tests/__init__.py
index 96d1dda..88828e8 100644
--- a/django/contrib/formtools/tests/__init__.py
+++ b/django/contrib/formtools/tests/__init__.py
@@ -7,16 +7,12 @@
 from django.contrib.formtools import preview, utils
 from django.contrib.formtools.wizard import FormWizard
 from django.test import TestCase
-from django.test.utils import get_warnings_state, restore_warnings_state
 from django.test.utils import override_settings
 from django.utils import unittest
 
 from django.contrib.formtools.tests.wizard import *
 from django.contrib.formtools.tests.forms import *
 
-warnings.filterwarnings('ignore', category=PendingDeprecationWarning,
-module='django.contrib.formtools.wizard')
-
 success_string = "Done was called!"
 
 class TestFormPreview(preview.FormPreview):
@@ -41,20 +37,12 @@ class PreviewTests(TestCase):
 
 def setUp(self):
 super(PreviewTests, self).setUp()
-self.save_warnings_state()
-warnings.filterwarnings('ignore', category=DeprecationWarning,
-
module='django.contrib.formtools.wizard.legacy')
-
 # Create a FormPreview instance to share between tests
 self.preview = preview.FormPreview(TestForm)
 input_template = ''
 self.input = input_template % (self.preview.unused_name('stage'), "%d")
 self.test_data = {'field1':u'foo', 'field1_':u'asdf'}
 
-def tearDown(self):
-super(PreviewTests, self).tearDown()
-self.restore_warnings_state()
-
 def test_unused_name(self):
 """
 Verifies name mangling to get uniue field name.
@@ -130,8 +118,9 @@ def test_bool_submit(self):
 self.test_data.update({'stage':2})
 hash = self.preview.security_hash(None, TestForm(self.test_data))
 self.test_data.update({'hash':hash, 'bool1':u'False'})
-response = self.client.post('/preview/', self.test_data)
-self.assertEqual(response.content, success_string)
+with warnings.catch_warnings(record=True):
+response = self.client.post('/preview/', self.test_data)
+self.assertEqual(response.content, success_string)
 
 def test_form_submit_good_hash(self):
 """
@@ -241,6 +230,16 @@ class WizardTests(TestCase):
 }
 )
 
+def setUp(self):
+super(WizardTests, self).setUp()
+self.save_warnings_state()
+warnings.filterwarnings('ignore', category=DeprecationWarning,
+module='django.contrib.formtools.wizard')
+
+def tearDown(self):
+super(WizardTests, self).tearDown()
+self.restore_warnings_state()
+
 def test_step_starts_at_zero(self):
 """
 step should be zero for the first form
diff --git a/django/contrib/sessions/tests.py b/django/contrib/sessions/tests.py
index dbcaea2..f31c056 100644
--- a/django/contrib/sessions/tests.py
+++ b/django/contrib/sessions/tests.py
@@ -12,11 +12,10 @@
 from django.contrib.sessions.backends.signed_cookies import SessionStore as 
CookieSession
 from django.contrib.sessions.models import Session
 from django.contrib.sessions.middleware import SessionMiddleware
-from django.core.cache.backends.base import CacheKeyWarning
 from django.core.exceptions import ImproperlyConfigured, SuspiciousOperation
 from django.http import HttpResponse
 from django.test import TestCase, RequestFactory
-from django.test.utils import override_settings, get_warnings_state, 
restore_warnings_state
+from django.test.utils import override_settings
 from django.utils import timezone
 from django.utils import unittest
 
@@ -302,12 +301,10 @@ def test_exists_searches_cache_first(self):
 self.assertTrue(self.session.exists(self.session.session_key))
 
 def test_load_overlong_key(self):
-warnings_state = get_warnings_state()
-warnings.filterwarnings('ignore',
-

Re: [Django] #4102: Allow UPDATE of only specific fields in model.save()

[Django]

#4102: Allow UPDATE of only specific fields in model.save()
-+-
 Reporter:  Collin Grady |Owner:  cgrady
   |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  update fields sql|  Patch needs improvement:  1
  row table modified |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by akaariai):

 I will take this ticket from here.

 We don't have any official guidelines on how to work on github, but here
 is an approach I like.
 {{{
 # Assume you have django/django as "upstream" remote in your local git
 repo.
 # (if not: git add remote upstream g...@github.com:django/django.git)

 # Start work on ticket.
 # Work in ticket_4102, make it track upstream/master branch.
 git checkout -b ticket_4102 upstream/master
 # do some commits:
 git add files
 git commit -m 'A commit message...'
 # check for whitespace errors
 git diff --check upstream/master

 # Spot some errors, correct files and commit
 git add files
 git commit -m 'DOH! whitespace error!'

 # The above commit should not go into Django's repository, so squash it
 # (HEAD~2 refers to last two commits on this branch)
 git rebase -i HEAD~2
 # pick the original commit ("A commit message..."), squash (s as first
 char on line) the "DOH!" commit.
 # reword commit messages, usually keep the first message as is, drop the
 second message.
 # Run (relevant) tests!
 # ok, seems the work is ready, push it to your github repo (assumed to be
 origin here)
 git push origin ticket_4102

 # make a pull request in github.
 # An annoying core-developer spots a world-ending issue (another
 whitespace error).
 # And, there have been some commits to the django/django repo too, so you
 need to update your patch to head.
 # In your local branch ticket_4102 rebase your work to current upstream
 master
 git fetch upstream
 git rebase
 # If conflicts above, correct & continue.
 # correct & commit the whitespace error, repeat the rebase -i step above
 # Run (relevant) tests!

 # Now, push again to origin. You have rebased your work. This changes the
 commit
 # history, and those who based their work on your work will hate you (they
 need to
 # rebase their work, too). However, this does not matter, as your branch
 is a
 # "topic branch" and nobody should trust your branch to be stable in
 commit history.
 # So force push changes:
 git push --force origin ticket_4102

 # You have your work in a single corrected commit in the original pull
 request!
 }}}
 The above isn't tested.

 Commit message guidelines (in short): A summary line of 50 chars.
 Separated with an empty line, paragraphs of 70 chars per line detailing
 the commit. Limits are soft, so if need be, break the characters per line
 rules.

 A single commit always? No, separate your work into logical "blocks". For
 this ticket, there is just one logical block, so a single commit.

 If the above seems confusing or a lot of work to do, here is another
 approach: At some point hand over your work to a committer who will finish
 it off.

 As said, the above isn't official Django workflow, just my approach...

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

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

[django/django] e9a566: Fixed broken URLs introduced in 1adc87cd32.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e9a56606e738c478373d052bbd876ff84afdb995
  
https://github.com/django/django/commit/e9a56606e738c478373d052bbd876ff84afdb995
  Author: Ramiro Morales 
  Date:   2012-05-03 (Thu, 03 May 2012)

  Changed paths:
M docs/faq/general.txt
M docs/ref/contrib/flatpages.txt
M docs/ref/contrib/gis/db-api.txt
M docs/ref/contrib/gis/geoquerysets.txt
M docs/ref/contrib/redirects.txt
M docs/ref/contrib/syndication.txt
M docs/ref/django-admin.txt
M docs/ref/settings.txt
M docs/topics/auth.txt
M docs/topics/db/queries.txt

  Log Message:
  ---
  Fixed broken URLs introduced in 1adc87cd32.


diff --git a/docs/faq/general.txt b/docs/faq/general.txt
index 71de888..771af8a 100644
--- a/docs/faq/general.txt
+++ b/docs/faq/general.txt
@@ -175,7 +175,7 @@ Technically, the docs on Django's site are generated from 
the latest development
 versions of those reST documents, so the docs on the Django site may offer more
 information than the docs that come with the latest Django release.
 
-.. _stored in revision control: 
https://github.com/django/django/tree/master/django/docs
+.. _stored in revision control: 
https://github.com/django/django/tree/master/docs/
 
 Where can I find Django developers for hire?
 
diff --git a/docs/ref/contrib/flatpages.txt b/docs/ref/contrib/flatpages.txt
index 0bba65c..6b5773b 100644
--- a/docs/ref/contrib/flatpages.txt
+++ b/docs/ref/contrib/flatpages.txt
@@ -147,7 +147,7 @@ Via the Python API
 which lives in `django/contrib/flatpages/models.py`_. You can access
 flatpage objects via the :doc:`Django database API `.
 
-.. _django/contrib/flatpages/models.py: 
https://github.com/django/django/tree/master/django/django/contrib/flatpages/models.py
+.. _django/contrib/flatpages/models.py: 
https://github.com/django/django/blob/master/django/contrib/flatpages/models.py
 
 .. currentmodule:: django.contrib.flatpages
 
diff --git a/docs/ref/contrib/gis/db-api.txt b/docs/ref/contrib/gis/db-api.txt
index eb364de..9c6eb03 100644
--- a/docs/ref/contrib/gis/db-api.txt
+++ b/docs/ref/contrib/gis/db-api.txt
@@ -215,7 +215,7 @@ Then distance queries may be performed as follows::
 >>> qs = SouthTexasCity.objects.filter(point__distance_gte=(pnt, D(mi=20)))
 >>> qs = SouthTexasCity.objects.filter(point__distance_gte=(pnt, 
D(chain=100)))
 
-__ 
https://github.com/django/django/tree/master/django/django/contrib/gis/tests/distapp/models.py
+__ 
https://github.com/django/django/blob/master/django/contrib/gis/tests/distapp/models.py
 
 .. _compatibility-table:
 
diff --git a/docs/ref/contrib/gis/geoquerysets.txt 
b/docs/ref/contrib/gis/geoquerysets.txt
index 7bd7fc8..7501fb3 100644
--- a/docs/ref/contrib/gis/geoquerysets.txt
+++ b/docs/ref/contrib/gis/geoquerysets.txt
@@ -736,7 +736,7 @@ the distance from the `Tasmanian`__ city of Hobart to every 
other
 in kilometers.  See the :ref:`ref-measure` for usage details and the list 
of
 :ref:`supported_units`.
 
-__ 
https://github.com/django/django/tree/master/django/django/contrib/gis/tests/distapp/models.py
+__ 
https://github.com/django/django/blob/master/django/contrib/gis/tests/distapp/models.py
 __ http://en.wikipedia.org/wiki/Tasmania
 
 ``length``
diff --git a/docs/ref/contrib/redirects.txt b/docs/ref/contrib/redirects.txt
index f527873..e34ba40 100644
--- a/docs/ref/contrib/redirects.txt
+++ b/docs/ref/contrib/redirects.txt
@@ -67,4 +67,4 @@ Via the Python API
 which lives in `django/contrib/redirects/models.py`_. You can access 
redirect
 objects via the :doc:`Django database API `.
 
-.. _django/contrib/redirects/models.py: 
https://github.com/django/django/tree/master/django/django/contrib/redirects/models.py
+.. _django/contrib/redirects/models.py: 
https://github.com/django/django/blob/master/django/contrib/redirects/models.py
diff --git a/docs/ref/contrib/syndication.txt b/docs/ref/contrib/syndication.txt
index 5b2b0db..6f89ee1 100644
--- a/docs/ref/contrib/syndication.txt
+++ b/docs/ref/contrib/syndication.txt
@@ -897,7 +897,7 @@ For example, to create an Atom 1.0 feed and print it to 
standard output::
 ...
 
 
-.. _django/utils/feedgenerator.py: 
https://github.com/django/django/tree/master/django/django/utils/feedgenerator.py
+.. _django/utils/feedgenerator.py: 
https://github.com/django/django/blob/master/django/utils/feedgenerator.py
 
 .. currentmodule:: django.contrib.syndication
 
diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt
index 3ddb390..0ea8252 100644
--- a/docs/ref/django-admin.txt
+++ b/docs/ref/django-admin.txt
@@ -926,7 +926,7 @@ with the ``--name`` option. The :class:`template context
 To work around this problem, you can use the :ttag:`templatetag`
 templatetag to "escape" the various parts of the template syntax.
 
-.. _source: 

Re: [Django] #4102: Allow UPDATE of only specific fields in model.save()

[Django]

#4102: Allow UPDATE of only specific fields in model.save()
-+-
 Reporter:  Collin Grady |Owner:  cgrady
   |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  update fields sql|  Patch needs improvement:  1
  row table modified |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by niwi):

 I tried your suggestion and give the desired results. Now the fields are
 no longer allowed m2n. I added the corresponding test.

 Regarding github and pull-requests ... always need to be all in a single
 commit? actually I'm a bit confused, and I hate to be opening pull-
 requests different each time you make a change or commit.

 With this change I created a new branch, with the 3 commits I've made for
 this issue. And upload the patch here.

 Unfortunately, documentation / paragraph in the release notes, I'll leave
 to you. I do not feel good ability to write this text.

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

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

Re: [Django] #18265: request.user cached value does not track request.session change

[Django]

#18265: request.user cached value does not track request.session change
--+--
 Reporter:  Tuttle|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by Tuttle):

 * needs_better_patch:   => 0
 * type:  Uncategorized => New feature
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #18265: request.user cached value does not track request.session change

[Django]

#18265: request.user cached value does not track request.session change
---+
 Reporter:  Tuttle |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  contrib.auth   |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 During the Single-Sign On technique implementation I came to the need of
 replacing request.session with a new session or just setting
 request.session = None.

 The descriptor in AuthenticationMiddleware nevertheless does not remember
 the session for which it sets the request._cached_user.

 IMHO, the descriptor should cache the session key when it saves the
 _cached_user and allow _cached_user to be used only when the session key
 did not unchange.

 Currently everyone who changes the session during the request processing
 HAS to dig into the AuthenticationMiddleware internals and modify the
 _cached_user to get valid request.user. That's hard to maintain.

 I can offer the patch, but would like to get some response first.

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

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

[django/django] ea28bc: Removed unused file from i18n regression tests.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ea28bc2688b44559787fc12a3b8fc7939ee86f9b
  
https://github.com/django/django/commit/ea28bc2688b44559787fc12a3b8fc7939ee86f9b
  Author: Ramiro Morales 
  Date:   2012-05-03 (Thu, 03 May 2012)

  Changed paths:
R tests/regressiontests/i18n/test_warnings.py

  Log Message:
  ---
  Removed unused file from i18n regression tests.


diff --git a/tests/regressiontests/i18n/test_warnings.py 
b/tests/regressiontests/i18n/test_warnings.py
deleted file mode 100644
index 8aac89d..000
--- a/tests/regressiontests/i18n/test_warnings.py
+++ /dev/null
@@ -1,44 +0,0 @@
-import warnings
-from os.path import join, normpath, abspath, dirname
-
-import django
-from django.conf import settings
-from django.test.utils import get_warnings_state, restore_warnings_state
-from django.utils.translation import _trans
-from django.utils.unittest import TestCase
-
-
-class DeprecationWarningTests(TestCase):
-
-def setUp(self):
-self.warning_state = get_warnings_state()
-self.old_settings_module = settings.SETTINGS_MODULE
-settings.SETTINGS_MODULE = 'regressiontests'
-self.old_locale_paths = settings.LOCALE_PATHS
-
-def tearDown(self):
-restore_warnings_state(self.warning_state)
-settings.SETTINGS_MODULE = self.old_settings_module
-settings.LOCALE_PATHS = self.old_locale_paths
-
-def test_warn_if_project_has_locale_subdir(self):
-"""Test that DeprecationWarning is generated when a deprecated project 
level locale/ subdir is present."""
-project_path = join(dirname(abspath(__file__)), '..')
-warnings.filterwarnings('error',
-"Translations in the project directory aren't supported 
anymore\. Use the LOCALE_PATHS setting instead\.",
-DeprecationWarning)
-_trans.__dict__ = {}
-self.assertRaises(DeprecationWarning, 
django.utils.translation.ugettext, 'Time')
-
-def test_no_warn_if_project_and_locale_paths_overlap(self):
-"""Test that DeprecationWarning isn't generated when a deprecated 
project level locale/ subdir is also included in LOCALE_PATHS."""
-project_path = join(dirname(abspath(__file__)), '..')
-settings.LOCALE_PATHS += (normpath(join(project_path, 'locale')),)
-warnings.filterwarnings('error',
-"Translations in the project directory aren't supported 
anymore\. Use the LOCALE_PATHS setting instead\.",
-DeprecationWarning)
-_trans.__dict__ = {}
-try:
-django.utils.translation.ugettext('Time')
-except DeprecationWarning:
-self.fail("DeprecationWarning shouldn't be raised when 
settings/project locale and a LOCALE_PATHS member point to the same file system 
location.")




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

Re: [Django] #18264: manage user ands groups in django project without admin site

[Django]

#18264: manage user ands groups in django project without admin site
---+--
 Reporter:  wirodriguez@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.3
 Severity:  Normal |   Resolution:  invalid
 Keywords:  admin, site| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 TicketClosingReasons/UseSupportChannels

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

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

[Django] #18264: manage user ands groups in django project without admin site

[Django]

#18264: manage user ands groups in django project without admin site
---+-
 Reporter:  wirodriguez@…  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.3
 Severity:  Normal |   Keywords:  admin, site
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 Hi working in a django project and i need manage users and groups but
 without using the admin site ..

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

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

[django/django] 1adc87: Updated some URLs in the documentation to point to...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1adc87cd324db6003ef2962e68e11ccc9b104658
  
https://github.com/django/django/commit/1adc87cd324db6003ef2962e68e11ccc9b104658
  Author: Ramiro Morales 
  Date:   2012-05-03 (Thu, 03 May 2012)

  Changed paths:
M docs/faq/general.txt
M docs/ref/contrib/flatpages.txt
M docs/ref/contrib/gis/db-api.txt
M docs/ref/contrib/gis/geoquerysets.txt
M docs/ref/contrib/redirects.txt
M docs/ref/contrib/syndication.txt
M docs/ref/django-admin.txt
M docs/ref/settings.txt
M docs/topics/auth.txt
M docs/topics/db/queries.txt

  Log Message:
  ---
  Updated some URLs in the documentation to point to the new repository.


diff --git a/docs/faq/general.txt b/docs/faq/general.txt
index 232f6e4..71de888 100644
--- a/docs/faq/general.txt
+++ b/docs/faq/general.txt
@@ -46,8 +46,8 @@ We've also recorded an `audio clip of the pronunciation`_.
 Is Django stable?
 -
 
-Yes, it's quite stable. World Online has been using Django for many years. 
Sites built on 
-Django have weathered traffic spikes of over one million hits an hour. 
+Yes, it's quite stable. World Online has been using Django for many years. 
Sites built on
+Django have weathered traffic spikes of over one million hits an hour.
 
 Does Django scale?
 --
@@ -175,7 +175,7 @@ Technically, the docs on Django's site are generated from 
the latest development
 versions of those reST documents, so the docs on the Django site may offer more
 information than the docs that come with the latest Django release.
 
-.. _stored in revision control: 
https://code.djangoproject.com/browser/django/trunk/docs
+.. _stored in revision control: 
https://github.com/django/django/tree/master/django/docs
 
 Where can I find Django developers for hire?
 
diff --git a/docs/ref/contrib/flatpages.txt b/docs/ref/contrib/flatpages.txt
index 8873c28..0bba65c 100644
--- a/docs/ref/contrib/flatpages.txt
+++ b/docs/ref/contrib/flatpages.txt
@@ -147,7 +147,7 @@ Via the Python API
 which lives in `django/contrib/flatpages/models.py`_. You can access
 flatpage objects via the :doc:`Django database API `.
 
-.. _django/contrib/flatpages/models.py: 
https://code.djangoproject.com/browser/django/trunk/django/contrib/flatpages/models.py
+.. _django/contrib/flatpages/models.py: 
https://github.com/django/django/tree/master/django/django/contrib/flatpages/models.py
 
 .. currentmodule:: django.contrib.flatpages
 
diff --git a/docs/ref/contrib/gis/db-api.txt b/docs/ref/contrib/gis/db-api.txt
index 4cf65e5..eb364de 100644
--- a/docs/ref/contrib/gis/db-api.txt
+++ b/docs/ref/contrib/gis/db-api.txt
@@ -215,7 +215,7 @@ Then distance queries may be performed as follows::
 >>> qs = SouthTexasCity.objects.filter(point__distance_gte=(pnt, D(mi=20)))
 >>> qs = SouthTexasCity.objects.filter(point__distance_gte=(pnt, 
D(chain=100)))
 
-__ 
https://code.djangoproject.com/browser/django/trunk/django/contrib/gis/tests/distapp/models.py
+__ 
https://github.com/django/django/tree/master/django/django/contrib/gis/tests/distapp/models.py
 
 .. _compatibility-table:
 
diff --git a/docs/ref/contrib/gis/geoquerysets.txt 
b/docs/ref/contrib/gis/geoquerysets.txt
index 5bc9ab1..7bd7fc8 100644
--- a/docs/ref/contrib/gis/geoquerysets.txt
+++ b/docs/ref/contrib/gis/geoquerysets.txt
@@ -736,7 +736,7 @@ the distance from the `Tasmanian`__ city of Hobart to every 
other
 in kilometers.  See the :ref:`ref-measure` for usage details and the list 
of
 :ref:`supported_units`.
 
-__ 
https://code.djangoproject.com/browser/django/trunk/django/contrib/gis/tests/distapp/models.py
+__ 
https://github.com/django/django/tree/master/django/django/contrib/gis/tests/distapp/models.py
 __ http://en.wikipedia.org/wiki/Tasmania
 
 ``length``
diff --git a/docs/ref/contrib/redirects.txt b/docs/ref/contrib/redirects.txt
index 71c3b4f..f527873 100644
--- a/docs/ref/contrib/redirects.txt
+++ b/docs/ref/contrib/redirects.txt
@@ -67,4 +67,4 @@ Via the Python API
 which lives in `django/contrib/redirects/models.py`_. You can access 
redirect
 objects via the :doc:`Django database API `.
 
-.. _django/contrib/redirects/models.py: 
https://code.djangoproject.com/browser/django/trunk/django/contrib/redirects/models.py
+.. _django/contrib/redirects/models.py: 
https://github.com/django/django/tree/master/django/django/contrib/redirects/models.py
diff --git a/docs/ref/contrib/syndication.txt b/docs/ref/contrib/syndication.txt
index 76c176e..5b2b0db 100644
--- a/docs/ref/contrib/syndication.txt
+++ b/docs/ref/contrib/syndication.txt
@@ -897,7 +897,7 @@ For example, to create an Atom 1.0 feed and print it to 
standard output::
 ...
 
 
-.. _django/utils/feedgenerator.py: 
https://code.djangoproject.com/browser/django/trunk/django/utils/feedgenerator.py
+.. _django/utils/feedgenerator.py: 

Re: [Django] #17049: The test suite should be deprecation-warning clean

[Django]

#17049: The test suite should be deprecation-warning clean
--+
 Reporter:  carljm|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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 claudep):

 After commit b52672d77822e88752cb178c8a359adde83ff0ba, the test suite with
 python2.6 + SQLite and PostgreSQL seems to be warnings-free. Needs
 confirmation for other combinations.

 
https://github.com/django/django/commit/b52672d77822e88752cb178c8a359adde83ff0ba

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

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

[django/django] b52672: Replaced deprecated TestCase methods. Refs #17049.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b52672d77822e88752cb178c8a359adde83ff0ba
  
https://github.com/django/django/commit/b52672d77822e88752cb178c8a359adde83ff0ba
  Author: Claude Paroz 
  Date:   2012-05-03 (Thu, 03 May 2012)

  Changed paths:
M django/contrib/auth/tests/management.py
M django/contrib/auth/tests/models.py
M django/contrib/formtools/tests/wizard/wizardtests/tests.py
M django/contrib/gis/geoip/tests.py
M django/contrib/gis/tests/test_measure.py
M tests/modeltests/prefetch_related/tests.py
M tests/modeltests/select_for_update/tests.py
M tests/modeltests/test_client/models.py
M tests/regressiontests/admin_filters/tests.py
M tests/regressiontests/admin_inlines/tests.py
M tests/regressiontests/admin_views/tests.py
M tests/regressiontests/backends/tests.py
M tests/regressiontests/createsuperuser/tests.py
M tests/regressiontests/file_uploads/tests.py
M tests/regressiontests/servers/tests.py
M tests/regressiontests/settings_tests/tests.py
M tests/regressiontests/test_client_regress/models.py
M tests/regressiontests/test_runner/tests.py
M tests/regressiontests/utils/feedgenerator.py

  Log Message:
  ---
  Replaced deprecated TestCase methods. Refs #17049.


diff --git a/django/contrib/auth/tests/management.py 
b/django/contrib/auth/tests/management.py
index 3708cc8..5d31bd7 100644
--- a/django/contrib/auth/tests/management.py
+++ b/django/contrib/auth/tests/management.py
@@ -50,7 +50,7 @@ def 
test_that_changepassword_command_changes_joes_password(self):
 command.execute("joe", stdout=self.stdout)
 command_output = self.stdout.getvalue().strip()
 
-self.assertEquals(command_output, "Changing password for user 
'joe'\nPassword changed successfully for user 'joe'")
+self.assertEqual(command_output, "Changing password for user 
'joe'\nPassword changed successfully for user 'joe'")
 
self.assertTrue(models.User.objects.get(username="joe").check_password("not 
qwerty"))
 
 def test_that_max_tries_exits_1(self):
diff --git a/django/contrib/auth/tests/models.py 
b/django/contrib/auth/tests/models.py
index 324f433..b956592 100644
--- a/django/contrib/auth/tests/models.py
+++ b/django/contrib/auth/tests/models.py
@@ -46,12 +46,12 @@ class NaturalKeysTestCase(TestCase):
 
 def test_user_natural_key(self):
 staff_user = User.objects.get(username='staff')
-self.assertEquals(User.objects.get_by_natural_key('staff'), staff_user)
-self.assertEquals(staff_user.natural_key(), ('staff',))
+self.assertEqual(User.objects.get_by_natural_key('staff'), staff_user)
+self.assertEqual(staff_user.natural_key(), ('staff',))
 
 def test_group_natural_key(self):
 users_group = Group.objects.create(name='users')
-self.assertEquals(Group.objects.get_by_natural_key('users'), 
users_group)
+self.assertEqual(Group.objects.get_by_natural_key('users'), 
users_group)
 
 
 @override_settings(USE_TZ=False)
@@ -61,7 +61,7 @@ class LoadDataWithoutNaturalKeysTestCase(TestCase):
 def test_user_is_created_and_added_to_group(self):
 user = User.objects.get(username='my_username')
 group = Group.objects.get(name='my_group')
-self.assertEquals(group, user.groups.get())
+self.assertEqual(group, user.groups.get())
 
 
 @override_settings(USE_TZ=False)
@@ -71,7 +71,7 @@ class LoadDataWithNaturalKeysTestCase(TestCase):
 def test_user_is_created_and_added_to_group(self):
 user = User.objects.get(username='my_username')
 group = Group.objects.get(name='my_group')
-self.assertEquals(group, user.groups.get())
+self.assertEqual(group, user.groups.get())
 
 
 class UserManagerTestCase(TestCase):
@@ -79,23 +79,23 @@ class UserManagerTestCase(TestCase):
 def test_create_user(self):
 email_lowercase = 'nor...@normal.com'
 user = User.objects.create_user('user', email_lowercase)
-self.assertEquals(user.email, email_lowercase)
-self.assertEquals(user.username, 'user')
-self.assertEquals(user.password, '!')
+self.assertEqual(user.email, email_lowercase)
+self.assertEqual(user.username, 'user')
+self.assertEqual(user.password, '!')
 
 def test_create_user_email_domain_normalize_rfc3696(self):
 # According to  http://tools.ietf.org/html/rfc3696#section-3
 # the "@" symbol can be part of the local part of an email address
 returned = UserManager.normalize_email(r'Abc\@d...@example.com')
-self.assertEquals(returned, r'Abc\@d...@example.com')
+self.assertEqual(returned, r'Abc\@d...@example.com')
 
 def test_create_user_email_domain_normalize(self):
 returned = UserManager.normalize_email('nor...@domain.com')
-self.assertEquals(returned, 'nor...@domain.com')
+self.assertEqual(returned, 

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:  nobody
 Type:  New feature|   Status:  reopened
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 aaugustin):

 The admin displays the number of matching objects and the total number of
 objects.

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

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

Re: [Django] #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:  nobody
 Type:  New feature|   Status:  reopened
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 akaariai):

 Can you track down where the unrestricted qs.count() is issued, and if
 there is a reason for it?

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

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

Re: [Django] #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:  nobody
 Type:  New feature|   Status:  reopened
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 nova77):

 Apparently count(*) is called on the whole table even if you filter your
 view. For instance if you add "?id__in=555,666", you'll have two select
 count(*): one with the "where" clause and a plain one which runs on the
 whole table.

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

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

Re: [Django] #11663: Delete orphaned replaced files

[Django]

#11663: Delete orphaned replaced files
-+-
 Reporter:  SmileyChris  |Owner:
 Type:  Uncategorized|  SmileyChris
Component:  File |   Status:  closed
  uploads/storage|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anonymous):

 There is a package for this.

 http://pypi.python.org/pypi/django-orphaned

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

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

Re: [Django] #18263: admin/edit_inline/tabular.html only handles hidden fields correctly in the header

[Django]

#18263: admin/edit_inline/tabular.html only handles hidden fields correctly in 
the
header
---+--
 Reporter:  hvdklauw   |Owner:  hvdklauw
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by hvdklauw):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * easy:  0 => 1
 * needs_docs:   => 0
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18263: admin/edit_inline/tabular.html only handles hidden fields correctly in the header

[Django]

#18263: admin/edit_inline/tabular.html only handles hidden fields correctly in 
the
header
---+--
 Reporter:  hvdklauw   |  Owner:  hvdklauw
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 So, hidden fields arent suppost to get their own column in the tabular
 inlines (makes sense)
 However the only thing here that get's handled properly is the header
 part, the actual form column part (the td's) don't add the hidden field to
 the first column but add their own column.

 I'll be adding a patch shortly to correct this problem

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

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

Re: [Django] #18261: Clarify the term "project root directory"

[Django]

#18261: Clarify the term "project root directory"
-+-
 Reporter:  schnippi |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  project root, root   | Triage Stage:  Accepted
  directory, translation,|  Needs documentation:  0
  makemessages, compilemessages  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by ramiro):

 * needs_better_patch:   => 0
 * needs_docs:   => 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] e84f79: Fixed #18042 -- Advanced deprecation warnings.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e84f79f05113f546810c1908c7baef99fb1e874a
  
https://github.com/django/django/commit/e84f79f05113f546810c1908c7baef99fb1e874a
  Author: Aymeric Augustin 
  Date:   2012-05-03 (Thu, 03 May 2012)

  Changed paths:
M django/conf/__init__.py
M django/conf/urls/defaults.py
M django/contrib/admin/templatetags/adminmedia.py
M django/contrib/databrowse/__init__.py
M django/contrib/formtools/tests/__init__.py
M django/contrib/formtools/wizard/legacy.py
M django/contrib/gis/utils/geoip.py
M django/contrib/localflavor/uk/forms.py
M django/contrib/localflavor/uk/uk_regions.py
M django/core/cache/backends/memcached.py
M django/core/management/__init__.py
M django/http/__init__.py
M django/middleware/common.py
M django/template/defaultfilters.py
M django/utils/copycompat.py
M django/utils/hashcompat.py
M django/utils/itercompat.py
M django/utils/text.py
M django/views/decorators/cache.py
M django/views/decorators/csrf.py
M tests/regressiontests/cache/tests.py
M tests/regressiontests/decorators/tests.py
M tests/regressiontests/logging_tests/tests.py
M tests/regressiontests/requests/tests.py
M tests/regressiontests/settings_tests/tests.py
M tests/regressiontests/utils/text.py
M tests/runtests.py

  Log Message:
  ---
  Fixed #18042 -- Advanced deprecation warnings.

Thanks Ramiro for the patch.


diff --git a/django/conf/__init__.py b/django/conf/__init__.py
index 6a2485b..531eed8 100644
--- a/django/conf/__init__.py
+++ b/django/conf/__init__.py
@@ -181,7 +181,7 @@ def compat_patch_logging_config(logging_config):
 "handler: adding implicit debug-false-only filter. "
 "See http://docs.djangoproject.com/en/dev/releases/1.4/;
 "#request-exceptions-are-now-always-logged",
-PendingDeprecationWarning)
+DeprecationWarning)
 
 filter_name = "require_debug_false"
 
diff --git a/django/conf/urls/defaults.py b/django/conf/urls/defaults.py
index 326f05f..7d5c738 100644
--- a/django/conf/urls/defaults.py
+++ b/django/conf/urls/defaults.py
@@ -1,6 +1,6 @@
 import warnings
 warnings.warn("django.conf.urls.defaults is deprecated; use django.conf.urls 
instead",
-  PendingDeprecationWarning)
+  DeprecationWarning)
 
 from django.conf.urls import (handler403, handler404, handler500,
 include, patterns, url)
diff --git a/django/contrib/admin/templatetags/adminmedia.py 
b/django/contrib/admin/templatetags/adminmedia.py
index 753c180..b08d13c 100644
--- a/django/contrib/admin/templatetags/adminmedia.py
+++ b/django/contrib/admin/templatetags/adminmedia.py
@@ -11,5 +11,5 @@ def admin_media_prefix():
 """
 warnings.warn(
 "The admin_media_prefix template tag is deprecated. "
-"Use the static template tag instead.", PendingDeprecationWarning)
+"Use the static template tag instead.", DeprecationWarning)
 return PrefixNode.handle_simple("ADMIN_MEDIA_PREFIX")
diff --git a/django/contrib/databrowse/__init__.py 
b/django/contrib/databrowse/__init__.py
index 24098b0..acb7626 100644
--- a/django/contrib/databrowse/__init__.py
+++ b/django/contrib/databrowse/__init__.py
@@ -2,5 +2,4 @@
 from django.contrib.databrowse.sites import DatabrowsePlugin, ModelDatabrowse, 
DatabrowseSite, site
 
 
-warnings.warn("The Databrowse contrib app is deprecated",
-PendingDeprecationWarning)
+warnings.warn("The Databrowse contrib app is deprecated", DeprecationWarning)
diff --git a/django/contrib/formtools/tests/__init__.py 
b/django/contrib/formtools/tests/__init__.py
index e628690..96d1dda 100644
--- a/django/contrib/formtools/tests/__init__.py
+++ b/django/contrib/formtools/tests/__init__.py
@@ -7,6 +7,7 @@
 from django.contrib.formtools import preview, utils
 from django.contrib.formtools.wizard import FormWizard
 from django.test import TestCase
+from django.test.utils import get_warnings_state, restore_warnings_state
 from django.test.utils import override_settings
 from django.utils import unittest
 
@@ -40,12 +41,20 @@ class PreviewTests(TestCase):
 
 def setUp(self):
 super(PreviewTests, self).setUp()
+self.save_warnings_state()
+warnings.filterwarnings('ignore', category=DeprecationWarning,
+
module='django.contrib.formtools.wizard.legacy')
+
 # Create a FormPreview instance to share between tests
 self.preview = preview.FormPreview(TestForm)
 input_template = ''
 self.input = input_template % (self.preview.unused_name('stage'), "%d")
 self.test_data = {'field1':u'foo', 'field1_':u'asdf'}
 
+def tearDown(self):
+super(PreviewTests, self).tearDown()
+self.restore_warnings_state()
+
 def test_unused_name(self):
 """
 Verifies name mangling to get uniue 

Re: [Django] #18042: Advance the deprecation warnings for the features that will be removed in 1.6

[Django]

#18042: Advance the deprecation warnings for the features that will be removed 
in
1.6
-+-
 Reporter:  aaugustin|Owner:  ramiro
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Uncategorized|   Resolution:  fixed
 Severity:  Release blocker  | 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 aaugustin):

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


Comment:

 Fixed in e84f79f05113f546810c1908c7baef99fb1e874a.

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

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

Re: [Django] #18262: {% url %} in sample template not working because of quotes

[Django]

#18262: {% url %} in sample template not working because of quotes
-+-
 Reporter:  schnippi |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  url, template,   | Triage Stage:  Accepted
  quotes |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * stage:  Unreviewed => Accepted


Comment:

 It seems the 1.4 docs are built from SVN trunk head, not from
 
[https://code.djangoproject.com/svn/django/branches/releases/1.4.X/docs/ref/templates/builtins.txt
 1.4 branch]. The 1.4 branch seems to have the correct documentation.

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

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

Re: [Django] #18262: {% url %} in sample template not working because of quotes

[Django]

#18262: {% url %} in sample template not working because of quotes
-+-
 Reporter:  schnippi |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  url, template,   | Triage Stage:
  quotes |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by schnippi):

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


Comment:

 Adding to the ticket:

 In this regard, the documentation at
 [https://docs.djangoproject.com/en/1.4/ref/templates/builtins/#url] seems
 wrong, too.

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

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

[Django] #18262: {% url %} in sample template not working because of quotes

[Django]

#18262: {% url %} in sample template not working because of quotes
---+---
 Reporter:  schnippi   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:  url, template, quotes
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 The sample template at [https://docs.djangoproject.com/en/1.4/topics/auth
 /#the-login-required-decorator] does not work because of the quotes around
 the view.

 Changing it to
 {{{
 {% url django.contrib.auth.views.login %}
 }}}
 will work.

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

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

[django/django] 227cec: Fixed #18214 -- Clarified the docs about serializa...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 227cec686e512412f613c3d14743b85445765d92
  
https://github.com/django/django/commit/227cec686e512412f613c3d14743b85445765d92
  Author: Alex Ogier 
  Date:   2012-05-02 (Wed, 02 May 2012)

  Changed paths:
M AUTHORS
M docs/topics/serialization.txt

  Log Message:
  ---
  Fixed #18214 -- Clarified the docs about serializable objects.


diff --git a/AUTHORS b/AUTHORS
index ded2ff6..7e771c2 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -395,6 +395,7 @@ answer newbie questions, and generally made Django that 
much better:
 Afonso Fernández Nogueira 
 Neal Norwitz 
 Todd O'Bryan 
+Alex Ogier 
 Selwin Ong 
 Gerardo Orozco 
 Christian Oudard 
diff --git a/docs/topics/serialization.txt b/docs/topics/serialization.txt
index d5a5282..6bda32d 100644
--- a/docs/topics/serialization.txt
+++ b/docs/topics/serialization.txt
@@ -3,8 +3,8 @@ Serializing Django objects
 ==
 
 Django's serialization framework provides a mechanism for "translating" Django
-objects into other formats. Usually these other formats will be text-based and
-used for sending Django objects over a wire, but it's possible for a
+models into other formats. Usually these other formats will be text-based and
+used for sending Django data over a wire, but it's possible for a
 serializer to handle any format (text-based or not).
 
 .. seealso::
@@ -23,8 +23,8 @@ At the highest level, serializing data is a very simple 
operation::
 The arguments to the ``serialize`` function are the format to serialize the 
data
 to (see `Serialization formats`_) and a
 :class:`~django.db.models.query.QuerySet` to serialize. (Actually, the second
-argument can be any iterator that yields Django objects, but it'll almost
-always be a QuerySet).
+argument can be any iterator that yields Django model instances, but it'll
+almost always be a QuerySet).
 
 You can also use a serializer object directly::
 




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

Re: [Django] #18260: Cache tag doesn't handle filter expresssions

[Django]

#18260: Cache tag doesn't handle filter expresssions
-+
 Reporter:  FunkyBob |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  cache| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by charettes):

 * cc: charette.s@… (added)
 * needs_tests:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 IMHO this should be tested.

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

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

[Django] #18261: Clarify the term "project root directory"

[Django]

#18261: Clarify the term "project root directory"
-+-
 Reporter:   |  Owner:  nobody
  schnippi   | Status:  new
 Type:   |Version:  1.4
  Uncategorized  |   Keywords:  project root, root directory,
Component:   |  translation, makemessages, compilemessages
  Documentation  |  Has patch:  0
 Severity:  Normal   |  UI/UX:  0
 Triage Stage:   |
  Unreviewed |
Easy pickings:  0|
-+-
 The documentation at
 {{{
 https://docs.djangoproject.com/en/dev/topics/i18n/translation/#message-
 files
 }}}
 states that
 {{{
 django-admin.py makemessages
 }}}
 should be run from "the root directory of your Django project" or "the
 root directory of your Django app".

 As the Django 1.4 directory structure creates mysite/ and mysite/mysite/,
 it is unclear, what the project's root directory is. Running django-admin
 makemessages/compilemessages within mysite/ makes the the Django
 translation system ignore my translation file. Running the commands in
 mysite/mysite/ instead does work as expected.

 It should be explicitly stated in the tutorial, that mysite/mysite/ is the
 project's root directory.

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

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

Re: [Django] #18260: Cache tag doesn't handle filter expresssions

[Django]

#18260: Cache tag doesn't handle filter expresssions
-+-
 Reporter:  FunkyBob |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  cache| Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by thepointer):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Ready for checkin


Comment:

 Looks good to me. Nice job FunkyBob

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

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

Re: [Django] #17776: DoesNotExist is not picklable

[Django]

#17776: DoesNotExist is not picklable
-+-
 Reporter:  ambv |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  1.3
  (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 anonymous):

 As I wrote in my WONTFIX explanation, this has to be fixed at the pickling
 level, specifically by introducing a new pickle protocol that can pickle
 inner classes. Good luck! ;)

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

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

Re: [Django] #2594: Template system should handle whitespace better

[Django]

#2594: Template system should handle whitespace better
-+-
 Reporter:  Gary Wilson  |Owner:  jshedd
  |   Status:  new
 Type:  Bug  |  Version:  master
Component:  Template system  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Semmel):

 * cc: Florian.Sening@… (added)


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

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

[Django] #18260: Cache tag doesn't handle filter expresssions

[Django]

#18260: Cache tag doesn't handle filter expresssions
-+
 Reporter:  FunkyBob |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  master
 Severity:  Normal   |   Keywords:  cache
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  1|  UI/UX:  0
-+
 I found the cache tag didn't well handle when I passed, for instance:

 {% cache .   request.GET.foo %}

 As it would raise an exception if GET['foo'] wasn't set... so I tried
 passing a default:

 {% cache . request.GET.foo|default:"bar" %}

 Only to see it not only didn't fix the issue, but didn't appear to be
 parsing filter expressions,  either.

 I've updated the cache tag to use parser.compile_filter for all its
 arguments.

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

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

Re: [Django] #17474: Problem when the request doesn't have Content-Type.

[Django]

#17474: Problem when the request doesn't have Content-Type.
-+-
 Reporter:  Marcelo Salhab   |Owner:  nobody
  Brogliato  |   Status:  reopened
 Type:  Bug  |  Version:  1.3
Component:  HTTP handling|   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  content-type |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ivan_virabyan):

 * cc: ivan_virabyan (added)


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

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

Re: [Django] #11305: Support for "Conditional Aggregates"

[Django]

#11305: Support for "Conditional Aggregates"
-+-
 Reporter:  bendavis78   |Owner:  akaariai
 Type:  New feature  |   Status:  new
Component:  ORM aggregation  |  Version:  1.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by LighteR):

 * cc: unknownlighter@… (added)


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

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

Re: [Django] #18214: Serializers do not serialize iterators

[Django]

#18214: Serializers do not serialize iterators
-+-
 Reporter:  moritzs  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  serialization json   |  checkin
  xml|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 Fixed in 227cec686e512412f613c3d14743b85445765d92

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

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

Re: [Django] #16884: Add message level argument to ModelAdmin's message_user

[Django]

#16884: Add message level argument to ModelAdmin's message_user
---+
 Reporter:  shelldweller   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+
Changes (by claudep):

 * needs_docs:  0 => 1


Comment:

 message_user is documented:
 
https://docs.djangoproject.com/en/dev/ref/contrib/admin/#django.contrib.admin.ModelAdmin.message_user

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

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