[Django] #22486: urlresolvers.reverse() security fix (1.5.6) breaks when a view is a partial

[Django]

#22486: urlresolvers.reverse() security fix (1.5.6) breaks when a view is a 
partial
-+
 Reporter:  rcoup|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (URLs)  |Version:  1.5
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 The changes in the recent security fix for `reverse()`
 
[https://github.com/django/django/commit/8b93b31487d6d3b0fcbbd0498991ea0db9088054
 Fixed a remote code execution vulnerabilty in URL reversing]
 ([https://www.djangoproject.com/weblog/2014/apr/21/security/
 CVE-2014-0472]) break when any view in the urlpatterns is a functools
 partial.

 Django 1.5.6 / Py2.6.5 / Linux.

 pseudo-code:


 {{{
 # myapp/views.py
 def my_view(request, **kwargs):
  return HttpResponse(str(kwargs))

 my_view2 = functools.partial(my_view, some_arg=123)

 # myapp/urls.py
 urlpatterns = patterns('my_app.views',
('^some_view/$', 'normal_view'),  # a normal function/class view
('^breaks/$', 'my_view2'),# partial-wrapped view
 )

 }}}

 Then

 {{{
 >>> from django.core.urlresolvers import reverse
 >>> reverse('my_app.some_view')
 django/core/urlresolvers.pyc in reverse(viewname, urlconf, args, kwargs,
 prefix, current_app)
 514 resolver = get_ns_resolver(ns_pattern, resolver)
 515
 --> 516 return iri_to_uri(resolver._reverse_with_prefix(view, prefix,
 *args, **kwargs))
 517
 518 reverse_lazy = lazy(reverse, str)

 django/core/urlresolvers.pyc in _reverse_with_prefix(self, lookup_view,
 _prefix, *args, **kwargs)
 393
 394 if not self._populated:
 --> 395 self._populate()
 396
 397 try:

 django/core/urlresolvers.pyc in _populate(self)
 285 else:
 286 parent = normalize(pattern.regex.pattern)
 --> 287 for name in pattern.reverse_dict:
 288 for matches, pat, defaults in
 pattern.reverse_dict.getlist(name):
 289 new_matches = []

 django/core/urlresolvers.pyc in reverse_dict(self)
 310 language_code = get_language()
 311 if language_code not in self._reverse_dict:
 --> 312 self._populate()
 313 return self._reverse_dict[language_code]
 314

 django/core/urlresolvers.pyc in _populate(self)
 271 callback = pattern._callback
 272 if not hasattr(callback, '__name__'):
 --> 273 lookup_str = callback.__module__ + "." +
 callback.__class__.__name__
 274 else:
 275 lookup_str = callback.__module__ + "." +
 callback.__name__

 AttributeError: 'functools.partial' object has no attribute '__module__'
 }}}

 Changing the view to use `functools.update_wrapper()` (as it probably
 should) and it works okay:

 {{{
 my_view2 = functools.partial(my_view, some_arg=123)
 functools.update_wrapper(my_view2, my_view)
 }}}

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

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

Re: [Django] #22479: Support byte range requests in django.views.static.serve

[Django]

#22479: Support byte range requests in django.views.static.serve
---+
 Reporter:  slurms |Owner:  slurms
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

 * cc: timo (added)


Comment:

 I don't know, but if we are adding runserver support for something that's
 not even supported by what I think is a fairly common web server, that
 seems like it will only encourage more people to use runserver in
 production.

 I'd echo Russ's sentiments from the django-developers thread: "rather than
 add a bunch of features to  a view in Django and then try to describe when
 you shouldn't use it, I'd prefer to use that effort to replace the
 devserver with something equally easy to use, but based off a base that is
 an actual real live web server. That way, we'd end up with a "devserver",
 but it would be an actual server, not a hack with a bunch of "please don't
 actually use this" warnings, we don't end up spending a bunch of time
 developing a feature that is already implemented better elsewhere, and it
 would be one step closer to having production mirror development."

 Would be great to at least do some investigation to see if this might be
 feasible even if gunicorn isn't the ultimate answer.

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

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

Re: [Django] #22051: Running `makemigrations` twice in a row fails

[Django]

#22051: Running `makemigrations` twice in a row fails
-+
 Reporter:  bmispelon|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by drackett@…):

 I'm running into the same thing as well. my initial `makemigration` is
 fine, but if I try and run it again (even with no changes) I get the same

 `django.db.migrations.state.InvalidBasesError: Cannot resolve bases for
 []`

 as everyone else.

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

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

[django/django] 7bb9be: [1.6.x] Add missing disclosure information to secu...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 7bb9bebe4764625e64b2a5725e47b45501f0537d
  
https://github.com/django/django/commit/7bb9bebe4764625e64b2a5725e47b45501f0537d
  Author: James Bennett 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M docs/releases/security.txt

  Log Message:
  ---
  [1.6.x] Add missing disclosure information to security archive.


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

[django/django] a0f609: [1.5.x] Add missing disclosure information to secu...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: a0f60958cf67d7ed1128e362cb1d6abee49169ed
  
https://github.com/django/django/commit/a0f60958cf67d7ed1128e362cb1d6abee49169ed
  Author: James Bennett 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M docs/releases/security.txt

  Log Message:
  ---
  [1.5.x] Add missing disclosure information to security archive.


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

[django/django] df8162: [1.7.x] Update for 1.7b2 security release.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: df81625da64473c43c7d0a948704d9efca84edbf
  
https://github.com/django/django/commit/df81625da64473c43c7d0a948704d9efca84edbf
  Author: James Bennett 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/__init__.py
M docs/releases/security.txt

  Log Message:
  ---
  [1.7.x] Update for 1.7b2 security release.


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

[django/django] 3f1abb: [1.6.x] Update for 1.6.3 security release.

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 3f1abbfc4097e1b9bace016258d8870f14ba8557
  
https://github.com/django/django/commit/3f1abbfc4097e1b9bace016258d8870f14ba8557
  Author: James Bennett 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/__init__.py
M docs/releases/security.txt

  Log Message:
  ---
  [1.6.x] Update for 1.6.3 security release.


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

[django/django] 486b6f: [1.5.x] Update for 1.5.6 security release.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 486b6f398bba109ba68b2f29c604e2cf13099aab
  
https://github.com/django/django/commit/486b6f398bba109ba68b2f29c604e2cf13099aab
  Author: James Bennett 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/__init__.py
M docs/conf.py
M docs/releases/security.txt
M setup.py

  Log Message:
  ---
  [1.5.x] Update for 1.5.6 security release.


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

[django/django] 194159: [1.4.x] Bump version numbers for 1.4.11 security r...

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 194159ba443645947e1a86bfd12e28dc78022521
  
https://github.com/django/django/commit/194159ba443645947e1a86bfd12e28dc78022521
  Author: James Bennett 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/__init__.py
M docs/conf.py
M setup.py

  Log Message:
  ---
  [1.4.x] Bump version numbers for 1.4.11 security release.


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

[django/django] c1a8c4: [1.4.x] Fixed a remote code execution vulnerabilty...

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: c1a8c420fe4b27fb2caf5e46d23b5712fc0ac535
  
https://github.com/django/django/commit/c1a8c420fe4b27fb2caf5e46d23b5712fc0ac535
  Author: Tim Graham 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/core/urlresolvers.py
A tests/regressiontests/urlpatterns_reverse/nonimported_module.py
M tests/regressiontests/urlpatterns_reverse/tests.py
M tests/regressiontests/urlpatterns_reverse/urls.py
M tests/regressiontests/urlpatterns_reverse/views.py

  Log Message:
  ---
  [1.4.x] Fixed a remote code execution vulnerabilty in URL reversing.

Thanks Benjamin Bach for the report and initial patch.

This is a security fix; disclosure to follow shortly.

Backport of 8b93b31487d6d3b0fcbbd0498991ea0db9088054 from master


  Commit: 1170f285ddd6a94a65f911a27788ba49ca08c0b0
  
https://github.com/django/django/commit/1170f285ddd6a94a65f911a27788ba49ca08c0b0
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/middleware/cache.py
M tests/regressiontests/cache/tests.py

  Log Message:
  ---
  [1.4.x] Prevented leaking the CSRF token through caching.

This is a security fix. Disclosure will follow shortly.

Backport of c083e3815aec23b99833da710eea574e6f2e8566 from master


  Commit: aa80f498de6d687e613860933ac58433ab71ea4b
  
https://github.com/django/django/commit/aa80f498de6d687e613860933ac58433ab71ea4b
  Author: Erik Romijn 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/db/models/fields/__init__.py
M docs/howto/custom-model-fields.txt
M docs/ref/databases.txt
M docs/ref/models/querysets.txt
M docs/topics/db/sql.txt
M tests/regressiontests/model_fields/tests.py

  Log Message:
  ---
  [1.4.x] Fixed queries that may return unexpected results on MySQL due to 
typecasting.

This is a security fix. Disclosure will follow shortly.

Backport of 75c0d4ea3ae48970f788c482ee0bd6b29a7f1307 from master


  Commit: 80109083136d7d633810d765b74e4c3018434010
  
https://github.com/django/django/commit/80109083136d7d633810d765b74e4c3018434010
  Author: Erik Romijn 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M docs/releases/1.4.11.txt

  Log Message:
  ---
  [1.4.x] Added information on resolved security issues to release notes.

Backport of c07f3e60c2d455e36ba4ac339d4283d32bbc3814 from master


Compare: https://github.com/django/django/compare/ca3927dfb946...80109083136d

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

[django/django] 546740: [1.7.x] Fixed a remote code execution vulnerabilty...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 546740544d7f69254a67b06a3fc7fa0c43512958
  
https://github.com/django/django/commit/546740544d7f69254a67b06a3fc7fa0c43512958
  Author: Tim Graham 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/core/urlresolvers.py
A tests/urlpatterns_reverse/nonimported_module.py
M tests/urlpatterns_reverse/tests.py
M tests/urlpatterns_reverse/urls.py
M tests/urlpatterns_reverse/views.py

  Log Message:
  ---
  [1.7.x] Fixed a remote code execution vulnerabilty in URL reversing.

Thanks Benjamin Bach for the report and initial patch.

This is a security fix; disclosure to follow shortly.

Backport of 8b93b31487d6d3b0fcbbd0498991ea0db9088054 from master


  Commit: 380545bf85cbf17fc698d136815b7691f8d023ca
  
https://github.com/django/django/commit/380545bf85cbf17fc698d136815b7691f8d023ca
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/middleware/cache.py
M tests/cache/tests.py

  Log Message:
  ---
  [1.7.x] Prevented leaking the CSRF token through caching.

This is a security fix. Disclosure will follow shortly.

Backport of c083e3815aec23b99833da710eea574e6f2e8566 from master


  Commit: 34526c2f56b863c2103655a0893ac801667e86ea
  
https://github.com/django/django/commit/34526c2f56b863c2103655a0893ac801667e86ea
  Author: Erik Romijn 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/db/models/fields/__init__.py
M docs/howto/custom-model-fields.txt
M docs/ref/databases.txt
M docs/ref/models/querysets.txt
M docs/topics/db/sql.txt
M tests/model_fields/tests.py

  Log Message:
  ---
  [1.7.x] Fixed queries that may return unexpected results on MySQL due to 
typecasting.

This is a security fix. Disclosure will follow shortly.

Backport of 75c0d4ea3ae48970f788c482ee0bd6b29a7f1307 from master


  Commit: 5577fd673e071fbfb0d140ea66b31983956ab174
  
https://github.com/django/django/commit/5577fd673e071fbfb0d140ea66b31983956ab174
  Author: Erik Romijn 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M docs/releases/1.4.11.txt
M docs/releases/1.5.6.txt
M docs/releases/1.6.3.txt

  Log Message:
  ---
  [1.7.x] Added information on resolved security issues to release notes.

Backport of c07f3e60c2d455e36ba4ac339d4283d32bbc3814 from master


Compare: https://github.com/django/django/compare/0bd913a19cf0...5577fd673e07

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

[django/django] 2a5bcb: [1.5.x] Fixed a remote code execution vulnerabilty...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 2a5bcb69f42b84464b24b5c835dca6467b6aa7f1
  
https://github.com/django/django/commit/2a5bcb69f42b84464b24b5c835dca6467b6aa7f1
  Author: Tim Graham 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/core/urlresolvers.py
A tests/regressiontests/urlpatterns_reverse/nonimported_module.py
M tests/regressiontests/urlpatterns_reverse/tests.py
M tests/regressiontests/urlpatterns_reverse/urls.py
M tests/regressiontests/urlpatterns_reverse/views.py

  Log Message:
  ---
  [1.5.x] Fixed a remote code execution vulnerabilty in URL reversing.

Thanks Benjamin Bach for the report and initial patch.

This is a security fix; disclosure to follow shortly.

Backport of 8b93b31487d6d3b0fcbbd0498991ea0db9088054 from master


  Commit: 6872f42757d7ef6a97e0b6ec5db4d2615d8a2bd8
  
https://github.com/django/django/commit/6872f42757d7ef6a97e0b6ec5db4d2615d8a2bd8
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/middleware/cache.py
M tests/regressiontests/cache/tests.py

  Log Message:
  ---
  [1.5.x] Prevented leaking the CSRF token through caching.

This is a security fix. Disclosure will follow shortly.

Backport of c083e3815aec23b99833da710eea574e6f2e8566 from master


  Commit: 985434fb1d6bf2335bf96c6ebf91c3674f1f399f
  
https://github.com/django/django/commit/985434fb1d6bf2335bf96c6ebf91c3674f1f399f
  Author: Erik Romijn 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/db/models/fields/__init__.py
M docs/howto/custom-model-fields.txt
M docs/ref/databases.txt
M docs/ref/models/querysets.txt
M docs/topics/db/sql.txt
M tests/regressiontests/model_fields/tests.py

  Log Message:
  ---
  [1.5.x] Fixed queries that may return unexpected results on MySQL due to 
typecasting.

This is a security fix. Disclosure will follow shortly.

Backport of 75c0d4ea3ae48970f788c482ee0bd6b29a7f1307 from master


  Commit: cebfbcdb862c7800e84d7413afc80de992486c4a
  
https://github.com/django/django/commit/cebfbcdb862c7800e84d7413afc80de992486c4a
  Author: Erik Romijn 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M docs/releases/1.4.11.txt
M docs/releases/1.5.6.txt

  Log Message:
  ---
  [1.5.x] Added information on resolved security issues to release notes.

Backport of c07f3e60c2d455e36ba4ac339d4283d32bbc3814 from master


Compare: https://github.com/django/django/compare/d6c685cc78d6...cebfbcdb862c

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

[django/django] 4352a5: [1.6.x] Fixed a remote code execution vulnerabilty...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 4352a50871e239ebcdf64eee6f0b88e714015c1b
  
https://github.com/django/django/commit/4352a50871e239ebcdf64eee6f0b88e714015c1b
  Author: Tim Graham 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/core/urlresolvers.py
A tests/urlpatterns_reverse/nonimported_module.py
M tests/urlpatterns_reverse/tests.py
M tests/urlpatterns_reverse/urls.py
M tests/urlpatterns_reverse/views.py

  Log Message:
  ---
  [1.6.x] Fixed a remote code execution vulnerabilty in URL reversing.

Thanks Benjamin Bach for the report and initial patch.

This is a security fix; disclosure to follow shortly.

Backport of 8b93b31487d6d3b0fcbbd0498991ea0db9088054 from master


  Commit: d63e20942f3024f24cb8cd85a49461ba8a9b6736
  
https://github.com/django/django/commit/d63e20942f3024f24cb8cd85a49461ba8a9b6736
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/middleware/cache.py
M tests/cache/tests.py

  Log Message:
  ---
  [1.6.x] Prevented leaking the CSRF token through caching.

This is a security fix. Disclosure will follow shortly.

Backport of c083e3815aec23b99833da710eea574e6f2e8566 from master


  Commit: 5f0829a27e85d89ad8c433f5c6a7a7d17c9e9292
  
https://github.com/django/django/commit/5f0829a27e85d89ad8c433f5c6a7a7d17c9e9292
  Author: Erik Romijn 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/db/models/fields/__init__.py
M docs/howto/custom-model-fields.txt
M docs/ref/databases.txt
M docs/ref/models/querysets.txt
M docs/topics/db/sql.txt
M tests/model_fields/tests.py

  Log Message:
  ---
  [1.6.x] Fixed queries that may return unexpected results on MySQL due to 
typecasting.

This is a security fix. Disclosure will follow shortly.

Backport of 75c0d4ea3ae48970f788c482ee0bd6b29a7f1307 from master


  Commit: d63bfb14dd1a35672fff18cd41f386330e109f8e
  
https://github.com/django/django/commit/d63bfb14dd1a35672fff18cd41f386330e109f8e
  Author: Erik Romijn 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M docs/releases/1.4.11.txt
M docs/releases/1.5.6.txt
M docs/releases/1.6.3.txt

  Log Message:
  ---
  [1.6.x] Added information on resolved security issues to release notes.

Backport of c07f3e60c2d455e36ba4ac339d4283d32bbc3814 from master


Compare: https://github.com/django/django/compare/25adac9b42e6...d63bfb14dd1a

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

[django/django] 8b93b3: Fixed a remote code execution vulnerabilty in URL ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8b93b31487d6d3b0fcbbd0498991ea0db9088054
  
https://github.com/django/django/commit/8b93b31487d6d3b0fcbbd0498991ea0db9088054
  Author: Tim Graham 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/core/urlresolvers.py
A tests/urlpatterns_reverse/nonimported_module.py
M tests/urlpatterns_reverse/tests.py
M tests/urlpatterns_reverse/urls.py
M tests/urlpatterns_reverse/views.py

  Log Message:
  ---
  Fixed a remote code execution vulnerabilty in URL reversing.

Thanks Benjamin Bach for the report and initial patch.

This is a security fix; disclosure to follow shortly.


  Commit: c083e3815aec23b99833da710eea574e6f2e8566
  
https://github.com/django/django/commit/c083e3815aec23b99833da710eea574e6f2e8566
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/middleware/cache.py
M tests/cache/tests.py

  Log Message:
  ---
  Prevented leaking the CSRF token through caching.

This is a security fix. Disclosure will follow shortly.


  Commit: 75c0d4ea3ae48970f788c482ee0bd6b29a7f1307
  
https://github.com/django/django/commit/75c0d4ea3ae48970f788c482ee0bd6b29a7f1307
  Author: Erik Romijn 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/db/models/fields/__init__.py
M docs/howto/custom-model-fields.txt
M docs/ref/databases.txt
M docs/ref/models/querysets.txt
M docs/topics/db/sql.txt
M tests/model_fields/tests.py

  Log Message:
  ---
  Fixed queries that may return unexpected results on MySQL due to typecasting.

This is a security fix; disclosure to follow shortly.


  Commit: c07f3e60c2d455e36ba4ac339d4283d32bbc3814
  
https://github.com/django/django/commit/c07f3e60c2d455e36ba4ac339d4283d32bbc3814
  Author: Erik Romijn 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M docs/releases/1.4.11.txt
M docs/releases/1.5.6.txt
M docs/releases/1.6.3.txt

  Log Message:
  ---
  Added information on resolved security issues to release notes.


Compare: https://github.com/django/django/compare/ab90c4707bc8...c07f3e60c2d4

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

Re: [Django] #22482: Sites documentation suggest using initial data fixtures which are deprecated in 1.7

[Django]

#22482: Sites documentation suggest using initial data fixtures which are
deprecated in 1.7
---+--
 Reporter:  scibi  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  sites, migrations  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by rtnpro):

 I believe that "initial data fixture" does not map directly to
 automatically loading of 'initial_data.' fixtures. You can load
 the fixtures with {{{ python manage.py loaddata  }}} as well
 as by a custom migration (which does not need any fixture AFAIK).

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

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

[django/django] 1667e7: Fixed PostGIS remove_field implementation

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1667e736a7da634bbda0df171bb60a980cbab7a3
  
https://github.com/django/django/commit/1667e736a7da634bbda0df171bb60a980cbab7a3
  Author: Claude Paroz 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/contrib/gis/db/backends/postgis/schema.py

  Log Message:
  ---
  Fixed PostGIS remove_field implementation

Fixed bad code introduced in 2f9d1576e8.


  Commit: ab90c4707bc8c813962658350b2e6c13ea0b4711
  
https://github.com/django/django/commit/ab90c4707bc8c813962658350b2e6c13ea0b4711
  Author: Claude Paroz 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/contrib/gis/tests/gis_migrations/test_operations.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  Fixed table cleanup in GIS migration tests


Compare: https://github.com/django/django/compare/2f9d1576e839...ab90c4707bc8

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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:
 Severity:  Normal   |  1.7-beta-1
 Keywords:  tests, test suite|   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  1
 |UI/UX:  0
-+-

Comment (by yakky):

 Good, thanks for support!

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

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

[Django]

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by charettes):

 Related to #21968 and #22397.

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

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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:
 Severity:  Normal   |  1.7-beta-1
 Keywords:  tests, test suite|   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  1
 |UI/UX:  0
-+-

Comment (by prestontimmons):

 Thanks, yakky. That illustrates the problem well.

 I added a pull request here: https://github.com/django/django/pull/2596

 I simplified your test case, since test_suite_override isn't really the
 right directory for this test, and there is a sample app already with an
 `__init__.py`.

 Thanks for preparing this.

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

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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:
 Severity:  Normal   |  1.7-beta-1
 Keywords:  tests, test suite|   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by rtnpro):

 * stage:  Accepted => Ready for checkin


Comment:

 https://code.djangoproject.com/attachment/ticket/22478/0001-Fixed-22478
 .-Use-correct-module-variable-in-build_te.2.patch looks good to me.

 +1.

 Marking it as "Ready for checkin".

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

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

[Django] #22485: makemigrations fails with dependencies to unmigrated apps

[Django]

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
   Reporter:  apollo13   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  master
  Migrations |   Keywords:  migrations,
   Severity:  Release|  unmigrated, makemigrations
  blocker|  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 Download the attached sample project and run ''manage.py makemigrations'':
 {{{
 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File
 "/home/florian/sources/django.git/django/core/management/__init__.py",
 line 427, in execute_from_command_line
 utility.execute()
   File
 "/home/florian/sources/django.git/django/core/management/__init__.py",
 line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/florian/sources/django.git/django/core/management/base.py",
 line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/florian/sources/django.git/django/core/management/base.py",
 line 337, in execute
 output = self.handle(*args, **options)
   File
 
"/home/florian/sources/django.git/django/core/management/commands/makemigrations.py",
 line 99, in handle
 changes = autodetector.changes(graph=loader.graph,
 trim_to_apps=app_labels or None)
   File
 "/home/florian/sources/django.git/django/db/migrations/autodetector.py",
 line 33, in changes
 changes = self._detect_changes()
   File
 "/home/florian/sources/django.git/django/db/migrations/autodetector.py",
 line 50, in _detect_changes
 old_apps = self.from_state.render()
   File "/home/florian/sources/django.git/django/db/migrations/state.py",
 line 63, in render
 model=dangling_lookup[0]))
 ValueError: Lookup failed for model referenced by field
 migrationtest.Test.user: auth.User

 }}}

 This is caused by
 
https://github.com/django/django/commit/956bd644249337b9467c017aac4eec228dde8c5d
 (see the comments there) -- not sure if this is the actual cause or rather
 
https://github.com/django/django/commit/2085f53f567f7619ecf3eab93fdacab7a5991a11
 due to missing tests.

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

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

Re: [Django] #22451: Migrations do not work with GeoDjango

[Django]

#22451: Migrations do not work with GeoDjango
-+--
 Reporter:  scibi|Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by claudep):

 * has_patch:  1 => 0


Comment:

 I'd like to also address this issue with Spatialite.

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

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

Re: [Django] #22481: Dropping geometry columns (PostGIS < 2.0) doesn't work

[Django]

#22481: Dropping geometry columns (PostGIS < 2.0) doesn't work
-+--
 Reporter:  claudep  |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by claudep):

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


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

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

Re: [Django] #22481: Dropping geometry columns (PostGIS < 2.0) doesn't work

[Django]

#22481: Dropping geometry columns (PostGIS < 2.0) doesn't work
-+--
 Reporter:  claudep  |Owner:  claudep
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Claude Paroz ):

 In [changeset:"2f9d1576e8395d401bd55d43046a6a65b575ab10"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2f9d1576e8395d401bd55d43046a6a65b575ab10"
 Fixed removal of GIS column in PostGIS 1.x migration

 Refs #22481.
 }}}

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

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

Re: [Django] #22451: Migrations do not work with GeoDjango

[Django]

#22451: Migrations do not work with GeoDjango
-+--
 Reporter:  scibi|Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Claude Paroz ):

 In [changeset:"fb09a489ca2c9c8940348e0cafafdbd7aff4740a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb09a489ca2c9c8940348e0cafafdbd7aff4740a"
 Fixed adding new GIS column in PostGIS 1.x migration

 Refs #22451.
 }}}

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

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

[django/django] fb09a4: Fixed adding new GIS column in PostGIS 1.x migrati...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fb09a489ca2c9c8940348e0cafafdbd7aff4740a
  
https://github.com/django/django/commit/fb09a489ca2c9c8940348e0cafafdbd7aff4740a
  Author: Claude Paroz 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/contrib/gis/db/backends/postgis/schema.py
A django/contrib/gis/tests/gis_migrations/test_operations.py

  Log Message:
  ---
  Fixed adding new GIS column in PostGIS 1.x migration

Refs #22451.


  Commit: 2f9d1576e8395d401bd55d43046a6a65b575ab10
  
https://github.com/django/django/commit/2f9d1576e8395d401bd55d43046a6a65b575ab10
  Author: Claude Paroz 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/contrib/gis/db/backends/postgis/schema.py
M django/contrib/gis/tests/gis_migrations/test_operations.py

  Log Message:
  ---
  Fixed removal of GIS column in PostGIS 1.x migration

Refs #22481.


Compare: https://github.com/django/django/compare/b2514c02e186...2f9d1576e839

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

Re: [Django] #20856: Error with admin popups: expected a character buffer object

[Django]

#20856: Error with admin popups: expected a character buffer object
-+-
 Reporter:  heppner.mark@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  admin, str,  | Triage Stage:
  character, inline, popup   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by apollo13):

 * resolution:  needsinfo => invalid


Comment:

 This was fixed as a sideeffect of #20812, people on 1.6 will have to live
 with it or write proper `__unicode__` methods :)

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

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

[django/django] d6c685: [1.5.x] Corrected the section identifier for MySQL...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: d6c685cc78d6bde96a60d82b9a065db3cd44ac66
  
https://github.com/django/django/commit/d6c685cc78d6bde96a60d82b9a065db3cd44ac66
  Author: Matt Lauber 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M docs/ref/unicode.txt

  Log Message:
  ---
  [1.5.x] Corrected the section identifier for MySQL unicode reference.

Backport of b2514c02e1 from master


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

[django/django] 25adac: [1.6.x] Corrected the section identifier for MySQL...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 25adac9b42e65caa5d2d42b6322e59ffb48df775
  
https://github.com/django/django/commit/25adac9b42e65caa5d2d42b6322e59ffb48df775
  Author: Matt Lauber 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M docs/ref/unicode.txt

  Log Message:
  ---
  [1.6.x] Corrected the section identifier for MySQL unicode reference.

Backport of b2514c02e1 from master


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

[django/django] 0bd913: [1.7.x] Corrected the section identifier for MySQL...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 0bd913a19cf0e7515834d6cb6d9e668840fecce5
  
https://github.com/django/django/commit/0bd913a19cf0e7515834d6cb6d9e668840fecce5
  Author: Matt Lauber 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M docs/ref/unicode.txt

  Log Message:
  ---
  [1.7.x] Corrected the section identifier for MySQL unicode reference.

Backport of b2514c02e1 from master


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

[django/django] ca3927: [1.4.x] Corrected the section identifier for MySQL...

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: ca3927dfb946cf7de2fbd1d85ce9433f02069eba
  
https://github.com/django/django/commit/ca3927dfb946cf7de2fbd1d85ce9433f02069eba
  Author: Matt Lauber 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M docs/ref/unicode.txt

  Log Message:
  ---
  [1.4.x] Corrected the section identifier for MySQL unicode reference.

Backport of b2514c02e1 from master


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

[django/django] b2514c: Corrected the section identifier for MySQL unicode...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b2514c02e186662ab82b77106a1a85abecf94039
  
https://github.com/django/django/commit/b2514c02e186662ab82b77106a1a85abecf94039
  Author: Matt Lauber 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M docs/ref/unicode.txt

  Log Message:
  ---
  Corrected the section identifier for MySQL unicode reference.


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

Re: [Django] #22340: Legacy Table Creation Methods Not Properly Deprecated

[Django]

#22340: Legacy Table Creation Methods Not Properly Deprecated
-+
 Reporter:  mlavin   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by timo):

 * version:  1.7-beta-1 => master


Comment:

 I'm going to change the version of this to master so we don't consider it
 a release blocker for 1.7. from Andrew in the
 [https://groups.google.com/d/msg/django-
 developers/wR6hTy9Nu2k/nQmuQ_5jXoMJ django-dev thread]:

 "Yes, the test suite is basically the biggest obstacle to full usage of
 migrations - I've tried to make it see sense, but given my limited time at
 the moment and the fact that it's a tortuous mess of hacks in places it
 means that I can't see that happening before the RC.

 I'd like to have started the Creation deprecation cycle this release, but
 it's probably fine if we let that slip a release (it's going to be harder
 to remove than many other features). Migrations will hopefully drive the
 adoption of SchemaEditor by developers and third-party backends anyway."

 We'll need to update the deprecation timeline and 1.7 release at some
 point once this punt is confirmed for sure.

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

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

Re: [Django] #22484: Remove old test runner cases

[Django]

#22484: Remove old test runner cases
-+-
 Reporter:  prestontimmons   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Merged in c54e7ec9ca1417bee0409489ed12f3e0f942a784. If you can update the
 PR with "Fixed #X -- " after filing a ticket so it's closed
 automatically, that's ideal.

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

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

[django/django] 251e83: Removed old test runner test cases.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 251e833c75b761c673d69e5f2a8e0cbd07586009
  
https://github.com/django/django/commit/251e833c75b761c673d69e5f2a8e0cbd07586009
  Author: Preston Timmons 
  Date:   2014-04-20 (Sun, 20 Apr 2014)

  Changed paths:
M tests/runtests.py
R tests/test_runner/valid_app/__init__.py
R tests/test_runner/valid_app/models/__init__.py
R tests/test_runner/valid_app/tests/__init__.py
R tests/test_runner_invalid_app/__init__.py
R tests/test_runner_invalid_app/models/__init__.py
R tests/test_runner_invalid_app/tests/__init__.py

  Log Message:
  ---
  Removed old test runner test cases.

These files were added as part of #12658, which pertained to the old 
django.test.simple test runner. No tests call them anymore.


  Commit: c54e7ec9ca1417bee0409489ed12f3e0f942a784
  
https://github.com/django/django/commit/c54e7ec9ca1417bee0409489ed12f3e0f942a784
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M tests/runtests.py
R tests/test_runner/valid_app/__init__.py
R tests/test_runner/valid_app/models/__init__.py
R tests/test_runner/valid_app/tests/__init__.py
R tests/test_runner_invalid_app/__init__.py
R tests/test_runner_invalid_app/models/__init__.py
R tests/test_runner_invalid_app/tests/__init__.py

  Log Message:
  ---
  Merge pull request #2592 from prestontimmons/remove-test-runner-cases

Removed old test runner test cases.


Compare: https://github.com/django/django/compare/405b13fe83e3...c54e7ec9ca14

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

[Django] #22484: Remove old test runner cases

[Django]

#22484: Remove old test runner cases
--+
 Reporter:  prestontimmons|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Testing framework |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+
 These files are left over from the django.test.simple tests.

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

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

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

Re: [Django] #22482: Sites documentation suggest using initial data fixtures which are deprecated in 1.7

[Django]

#22482: Sites documentation suggest using initial data fixtures which are
deprecated in 1.7
---+--
 Reporter:  scibi  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  sites, migrations  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

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

Re: [Django] #17802: Pass the request down to the Sitemap callable

[Django]

#17802: Pass the request down to the Sitemap callable
--+--
 Reporter:  rm_   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.sitemaps  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by rm_):

 Replying to [comment:6 aaugustin]:
 > I can't say what the proper solution is, but I'm afraid hardcoding a
 sitemap-specific solution will only make proper multi-tenancy harder. I
 think this requires a discussion on the DevelopersMailingList. See also
 #22231.

 So tried to open a discussion on mailing list few weeks ago without much
 success. The side effect though is that i'm very much interested in the
 patch [2] attached to #15089 [3] which make this #17802 ticket obsolete.
 Aymeric, any chance you can review the patch?

 [1] https://groups.google.com/forum/#!topic/django-developers/ORo_28B_VIA
 [2] https://code.djangoproject.com/attachment/ticket/15089/0001-Make-
 settings.SITE_ID-optional-for-django.contrib.si.patch
 [3] https://code.djangoproject.com/ticket/15089

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

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

[Django] #22483: Oracle test failures due to InterfaceError

[Django]

#22483: Oracle test failures due to InterfaceError
-+-
   Reporter:  timo   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.7-beta-1
  layer (models, ORM)|   Keywords:
   Severity:  Release|  Has patch:  0
  blocker|Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 Bisected to 2e42c859da42a871244aca36162a0aad2b63c02b (#21239)

 Example:
 {{{
 $ ./runtests.py --settings=test_oracle migrations
 ==
 ERROR: test_migrate (migrations.test_commands.MigrateTests)
 --
 Traceback (most recent call last):
   File "/home/tim/code/django/django/test/utils.py", line 316, in inner
 return test_func(*args, **kwargs)
   File "/home/tim/code/django/django/test/utils.py", line 216, in inner
 return test_func(*args, **kwargs)
   File "/home/tim/code/django/tests/migrations/test_commands.py", line 44,
 in test_migrate
 call_command("migrate", verbosity=0)
   File "/home/tim/code/django/django/core/management/__init__.py", line
 167, in call_command
 return klass.execute(*args, **defaults)
   File "/home/tim/code/django/django/core/management/base.py", line 337,
 in execute
 output = self.handle(*args, **options)
   File "/home/tim/code/django/django/core/management/commands/migrate.py",
 line 145, in handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File "/home/tim/code/django/django/db/migrations/executor.py", line 60,
 in migrate
 self.apply_migration(migration, fake=fake)
   File "/home/tim/code/django/django/db/migrations/executor.py", line 94,
 in apply_migration
 migration.apply(project_state, schema_editor)
   File "/home/tim/code/django/django/db/migrations/migration.py", line 97,
 in apply
 operation.database_forwards(self.app_label, schema_editor,
 project_state, new_state)
   File "/home/tim/code/django/django/db/migrations/operations/fields.py",
 line 36, in database_forwards
 field,
   File "/home/tim/code/django/django/db/backends/schema.py", line 392, in
 add_field
 self.execute(sql, params)
   File "/home/tim/code/django/django/db/backends/schema.py", line 95, in
 execute
 cursor.execute(sql, params)
   File "/home/tim/code/django/django/db/backends/utils.py", line 40, in
 __exit__
 self.close()
 InterfaceError: not connected
 }}}

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

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

Re: [Django] #22051: Running `makemigrations` twice in a row fails

[Django]

#22051: Running `makemigrations` twice in a row fails
-+
 Reporter:  bmispelon|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by david.fischer.ch@…):

 I am facing the same bug.

 That is a serious issue for my project.

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

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

Re: [Django] #22479: Support byte range requests in django.views.static.serve

[Django]

#22479: Support byte range requests in django.views.static.serve
---+
 Reporter:  slurms |Owner:  slurms
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by slurms):

 Does gunicorn support it? I'm not sure it does (there are no mentions of
 "Range" in the source at all), in which case it's not avoidable unless we
 add support into gunicorn instead?

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

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

[Django] #22482: Sites documentation suggest using initial data fixtures which are deprecated in 1.7

[Django]

#22482: Sites documentation suggest using initial data fixtures which are
deprecated in 1.7
---+---
 Reporter:  scibi  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.7-beta-1
 Severity:  Normal |   Keywords:  sites, migrations
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 Hi,

 Currently django.contrib.sites documentation suggest to use initial data
 fixtures to setup correct name and domain for the project
 (https://docs.djangoproject.com/en/dev/ref/contrib/sites/):

   `django.contrib.sites` registers a `post_migrate` signal handler which
 creates a default site named `example.com` with the domain `example.com`.
 This site will also be created after Django creates the test database. To
 set the correct name and domain for your project, you can use an initial
 data fixture.

 However automatic loading of fixtures has been deprecated in Django 1.7:
 https://docs.djangoproject.com/en/dev/howto/initial-data/#automatically-
 loading-initial-data-fixtures

 It would be nice if there was a description in the documentation how to
 setup sites configuration with migrations. I tried achieving this but
 without success - referring to `Site` model from `sites` in migration of
 some app leads to: `LookupError: No installed app with label 'sites'`.

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

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

Re: [Django] #22479: Support byte range requests in django.views.static.serve

[Django]

#22479: Support byte range requests in django.views.static.serve
---+
 Reporter:  slurms |Owner:  slurms
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timo):

 Did you have any thoughts on adding gunicorn support for runserver
 (#21978) as a possible way to avoid this?

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

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

Re: [Django] #22479: Support byte range requests in django.views.static.serve

[Django]

#22479: Support byte range requests in django.views.static.serve
---+
 Reporter:  slurms |Owner:  slurms
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by slurms):

 * owner:  nobody => slurms
 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * status:  new => assigned


Comment:

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

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

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

Re: [Django] #22477: Incompatible Global Settings

[Django]

#22477: Incompatible Global Settings
--+
 Reporter:  mlavin|Owner:  mlavin
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Uncategorized |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  0 => 1
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 It's a bit late in the 1.7 release cycle to make this change, so I suggest
 we do it in 1.8. Note that PRs should always be against master anyway; we
 then backport from there.

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

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

[django/django] 405b13: Fixed migrate when called inside a transaction.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 405b13fe83e3d8c9079545429d40c434eb496893
  
https://github.com/django/django/commit/405b13fe83e3d8c9079545429d40c434eb496893
  Author: Florian Apolloner 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/core/management/commands/migrate.py

  Log Message:
  ---
  Fixed migrate when called inside a transaction.

This is useful for tests manually calling migrate inside a testcase,
for normal usage this should make no difference, since there is no
surrounding transaction after all. If there is one we still try to
leave the transaction in a useable state (for postgres at least).

If this commit turns out to be causing issues, settings savepoint=False
is probably the right fix :)


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

Re: [Django] #22451: Migrations do not work with GeoDjango

[Django]

#22451: Migrations do not work with GeoDjango
-+--
 Reporter:  scibi|Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by scibi):

 * cc: scibi (added)


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

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

[django/django] 50dddb: [1.7.x] Corrected many style guide violations that...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 50dddbdfc7489847d55465ad352fc3278b2a9a08
  
https://github.com/django/django/commit/50dddbdfc7489847d55465ad352fc3278b2a9a08
  Author: Alex Gaynor 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/contrib/admin/options.py
M django/contrib/admin/validation.py
M django/contrib/flatpages/templatetags/flatpages.py
M django/contrib/gis/db/backends/postgis/operations.py
M django/contrib/gis/db/models/fields.py
M django/contrib/gis/db/models/query.py
M django/contrib/gis/feeds.py
M django/contrib/gis/gdal/geometries.py
M django/contrib/gis/gdal/geomtype.py
M django/contrib/gis/gdal/layer.py
M django/contrib/gis/gdal/libgdal.py
M django/contrib/gis/geos/libgeos.py
M django/contrib/gis/geos/prototypes/io.py
M django/contrib/gis/geos/tests/test_geos.py
M django/contrib/gis/utils/layermapping.py
M django/contrib/staticfiles/management/commands/collectstatic.py
M django/core/management/commands/inspectdb.py
M django/core/signing.py
M django/core/validators.py
M django/db/backends/utils.py
M django/db/models/lookups.py
M django/db/models/manager.py
M django/forms/formsets.py
M django/forms/models.py
M django/middleware/cache.py
M django/template/defaultfilters.py
M django/template/defaulttags.py
M django/utils/html.py
M django/utils/log.py
M scripts/manage_translations.py
M tests/admin_views/tests.py
M tests/forms_tests/tests/test_fields.py
M tests/lookup/tests.py
M tests/mail/tests.py
M tests/save_delete_hooks/models.py
M tests/str/tests.py
M tests/template_tests/test_response.py

  Log Message:
  ---
  [1.7.x] Corrected many style guide violations that the newest version of 
flake8 catches

Backport of 778ce245dd466bce1b19f89e52cf9ed8f1b46513 from master


  Commit: 62eb79fc4cc956b798e5c3a3be96101037ae9cb0
  
https://github.com/django/django/commit/62eb79fc4cc956b798e5c3a3be96101037ae9cb0
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/contrib/auth/management/__init__.py
M django/contrib/gis/views.py
M django/contrib/staticfiles/management/commands/collectstatic.py
M django/core/management/commands/loaddata.py
M django/db/models/base.py
M django/db/models/expressions.py
M django/db/models/fields/__init__.py
M django/utils/ipv6.py
M setup.cfg
M tests/cache/tests.py
M tests/migrations/test_writer.py
M tests/model_inheritance/tests.py
M tests/staticfiles_tests/tests.py

  Log Message:
  ---
  [1.7.x] Appeased flake8 2.1.0.

Backport of 428c0bbe1bcd303560d7e96d7d2721ff3fdc0e3f from master


  Commit: d7de6ed07eda3968d50e9045ff585763845bb290
  
https://github.com/django/django/commit/d7de6ed07eda3968d50e9045ff585763845bb290
  Author: Florian Apolloner 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M tests/staticfiles_tests/tests.py

  Log Message:
  ---
  [1.7.x] Fixed monkeypatching in a staticfiles test.

Backport of a4553e0510 from master


Compare: https://github.com/django/django/compare/0dad0ca55ec6...d7de6ed07eda

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

Re: [Django] #22374: Suggest to validate unique before running clean in models full_clean etc..

[Django]

#22374: Suggest to validate unique before running clean in models full_clean 
etc..
-+-
 Reporter:  dspjmt@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * resolution:  needsinfo => wontfix


Comment:

 I don't think it's a good idea. In particular, there is no guarantee that
 `validate_unique()` will be called. Note this comment in
 `django.forms.models`:
 {{{
 # self._validate_unique will be set to True by BaseModelForm.clean().
 # It is False by default so overriding self.clean() and failing to call
 # super will stop validate_unique from being called.
 }}}

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

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

Re: [Django] #22422: RegistryNotReadyException in django.apps.registry.Apps.check_ready()

[Django]

#22422: RegistryNotReadyException in django.apps.registry.Apps.check_ready()
-+-
 Reporter:  valberg  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.7-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * has_patch:  0 => 1


Comment:

 I think I would prefer linking the release notes to the text in the
 documentation so as we make additions and/or corrections we don't need to
 update two places. The PR should be against master, then we backport from
 there.

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

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

[django/django] a4553e: Fixed monkeypatching in a staticfiles test.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a4553e051087a026b7f52bfb56c0d880c39c9cc2
  
https://github.com/django/django/commit/a4553e051087a026b7f52bfb56c0d880c39c9cc2
  Author: Florian Apolloner 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M tests/staticfiles_tests/tests.py

  Log Message:
  ---
  Fixed monkeypatching in a staticfiles test.


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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  tests, test suite  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by yakky):

 Thanks.
 0001-Fixed-22478.-Use-correct-module-variable-in-build_te.2.patch is the
 complete patch (code -linted- and test)

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

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

Re: [Django] #22481: Dropping geometry columns (PostGIS < 2.0) doesn't work

[Django]

#22481: Dropping geometry columns (PostGIS < 2.0) doesn't work
-+--
 Reporter:  claudep  |Owner:  claudep
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 The patch has to be applied over the one for #22451, hence just attaching
 it for now.

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

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

[Django] #22481: Dropping geometry columns (PostGIS < 2.0) doesn't work

[Django]

#22481: Dropping geometry columns (PostGIS < 2.0) doesn't work
---+
   Reporter:  claudep  |  Owner:  claudep
   Type:  Bug  | Status:  new
  Component:  Migrations   |Version:  1.7-beta-1
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 While working on #22451, I also found that dropping geometry columns
 didn't work with PostGIS 1.x.

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

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

Re: [Django] #22451: Migrations do not work with GeoDjango

[Django]

#22451: Migrations do not work with GeoDjango
-+--
 Reporter:  scibi|Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  tests, test suite  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by rtnpro):

 Hey yakky,

 AFAIK, you can replace existing attachment with the same name, but not
 with a different name.

 Regards,
 rtnpro

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

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

Re: [Django] #22451: Migrations do not work with GeoDjango

[Django]

#22451: Migrations do not work with GeoDjango
-+--
 Reporter:  scibi|Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by claudep):

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


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

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

[Django] #22480: "django-admin.py dumpdata" - unable to serialize

[Django]

#22480: "django-admin.py dumpdata" - unable to serialize
---+
 Reporter:  yn |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I encountered an error in


 {{{
 django-admin.py dumpdata
 }}}


 https://docs.djangoproject.com/en/1.6/ref/django-admin/#django-admin-
 dumpdata

 This command should print the serialized dump to stdout. And it's work
 fine

 I need to redirect stdout to file

 But
 {{{
 django-admin.py dumpdata > data.json
 }}}

 generates the error "Command error - unable to serialize"

 Django 1.6.2

 Python 3.3

 Windows 7 home 64b

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

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

[django/django] 25b2ce: Consolidated get_or_create tests.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 25b2ce896b93982e5e89931625e20349fb815fda
  
https://github.com/django/django/commit/25b2ce896b93982e5e89931625e20349fb815fda
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M tests/get_or_create/models.py
M tests/get_or_create/tests.py
R tests/get_or_create_regress/__init__.py
R tests/get_or_create_regress/models.py
R tests/get_or_create_regress/tests.py

  Log Message:
  ---
  Consolidated get_or_create tests.


  Commit: df3b1a01c7d6326e966fbe13aa149265f4bf9c8f
  
https://github.com/django/django/commit/df3b1a01c7d6326e966fbe13aa149265f4bf9c8f
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M tests/expressions/models.py
M tests/expressions/tests.py
R tests/expressions_regress/__init__.py
R tests/expressions_regress/models.py
R tests/expressions_regress/tests.py

  Log Message:
  ---
  Consolidated expressions tests.


  Commit: 428c0bbe1bcd303560d7e96d7d2721ff3fdc0e3f
  
https://github.com/django/django/commit/428c0bbe1bcd303560d7e96d7d2721ff3fdc0e3f
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M django/contrib/auth/management/__init__.py
M django/contrib/gis/views.py
M django/contrib/staticfiles/management/commands/collectstatic.py
M django/core/management/commands/loaddata.py
M django/db/models/base.py
M django/db/models/expressions.py
M django/db/models/fields/__init__.py
M django/utils/ipv6.py
M setup.cfg
M tests/cache/tests.py
M tests/migrations/test_writer.py
M tests/model_inheritance/tests.py
M tests/staticfiles_tests/tests.py

  Log Message:
  ---
  Appeased flake8 2.1.0.


Compare: https://github.com/django/django/compare/3f01e82c591b...428c0bbe1bcd

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

Re: [Django] #22374: Suggest to validate unique before running clean in models full_clean etc..

[Django]

#22374: Suggest to validate unique before running clean in models full_clean 
etc..
-+-
 Reporter:  dspjmt@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  needsinfo
 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 Jimmy):

 Replying to [comment:3 Jimmy]:
 > Let's say, I have a module like:
 >
 > class A(Model):
 > b = IntegerField(max_length=3)

 Sorry, b = IntegerField()

 >
 > clean(self):
 > if b < 3:
 > raise ValidationError('Too large')
 >
 > When we use a form, if b is not filled, error will happen because b
 don't have a value. So we have to check if b has value, which was done in
 validate_unique(). So why not validate_unique first and then call clean?

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

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

Re: [Django] #22374: Suggest to validate unique before running clean in models full_clean etc..

[Django]

#22374: Suggest to validate unique before running clean in models full_clean 
etc..
-+-
 Reporter:  dspjmt@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  needsinfo
 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 Jimmy):

 Let's say, I have a module like:

 class A(Model):
 b = IntegerField(max_length=3)

 clean(self):
 if b < 3:
 raise ValidationError('Too large')

 When we use a form, if b is not filled, error will happen because b don't
 have a value. So we have to check if b has value, which was done in
 validate_unique(). So why not validate_unique first and then call clean?

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

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

Re: [Django] #22254: Testing documentation doesn't make it clear that django.setup() needs to be called with setup_test_environment

[Django]

#22254: Testing documentation doesn't make it clear that django.setup() needs 
to be
called with setup_test_environment
-+-
 Reporter:  peter.landry@…   |Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.7-alpha-2
 Severity:  Release blocker  |   Resolution:
 Keywords:  app-loading  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * status:  new => assigned
 * owner:  nobody => aaugustin
 * severity:  Normal => Release blocker


Comment:

 Indeed, django.setup() isn't correctly documented. Sorry about that.

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

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

[django/django] 3f01e8: Further consolidated the model_inheritance tests.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3f01e82c591b880faa5066ba28a3f11b2b82154c
  
https://github.com/django/django/commit/3f01e82c591b880faa5066ba28a3f11b2b82154c
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M tests/model_inheritance_regress/models.py
M tests/model_inheritance_regress/tests.py
R tests/model_inheritance_select_related/__init__.py
R tests/model_inheritance_select_related/models.py
R tests/model_inheritance_select_related/tests.py

  Log Message:
  ---
  Further consolidated the model_inheritance tests.


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

[django/django] 0dad0c: [1.7.x] Further consolidated the model_inheritance...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 0dad0ca55ec6081d3e92ac8340ed9f8d5c65a606
  
https://github.com/django/django/commit/0dad0ca55ec6081d3e92ac8340ed9f8d5c65a606
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
M tests/model_inheritance_regress/models.py
M tests/model_inheritance_regress/tests.py
R tests/model_inheritance_select_related/__init__.py
R tests/model_inheritance_select_related/models.py
R tests/model_inheritance_select_related/tests.py

  Log Message:
  ---
  [1.7.x] Further consolidated the model_inheritance tests.

Backport of 3f01e82 from master


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

[django/django] ab0afe: [1.7.x] Fixed #22402 -- Consolidated model_inherit...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: ab0afef9590730064d40ca074c3b2be3baebf9cb
  
https://github.com/django/django/commit/ab0afef9590730064d40ca074c3b2be3baebf9cb
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
A tests/model_inheritance/same_model_name/__init__.py
A tests/model_inheritance/same_model_name/models.py
M tests/model_inheritance/tests.py
R tests/model_inheritance_same_model_name/__init__.py
R tests/model_inheritance_same_model_name/models.py
R tests/model_inheritance_same_model_name/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22402 -- Consolidated model_inheritance tests.

The model_inheritance_same_model_name tests couldn't be run without the
model_inheritance tests. Make the problem go away by merging them.

Thanks timo for the report.

Backport of 0097d38 from master


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

Re: [Django] #22402: Deprecation warnings with model_inheritance

[Django]

#22402: Deprecation warnings with model_inheritance
-+-
 Reporter:  timo |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  app-loading  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"3f76339355c1fe550dedf676feddd42a5d48be58"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3f76339355c1fe550dedf676feddd42a5d48be58"
 Fixed #22402 -- Consolidated model_inheritance tests.

 The model_inheritance_same_model_name tests couldn't be run without the
 model_inheritance tests. Make the problem go away by merging them.

 Thanks timo for the report.
 }}}

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

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

Re: [Django] #22402: Deprecation warnings with model_inheritance

[Django]

#22402: Deprecation warnings with model_inheritance
-+-
 Reporter:  timo |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  app-loading  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"ab0afef9590730064d40ca074c3b2be3baebf9cb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ab0afef9590730064d40ca074c3b2be3baebf9cb"
 [1.7.x] Fixed #22402 -- Consolidated model_inheritance tests.

 The model_inheritance_same_model_name tests couldn't be run without the
 model_inheritance tests. Make the problem go away by merging them.

 Thanks timo for the report.

 Backport of 0097d38 from master
 }}}

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

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

[django/django] 3f7633: Fixed #22402 -- Consolidated model_inheritance tes...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3f76339355c1fe550dedf676feddd42a5d48be58
  
https://github.com/django/django/commit/3f76339355c1fe550dedf676feddd42a5d48be58
  Author: Aymeric Augustin 
  Date:   2014-04-21 (Mon, 21 Apr 2014)

  Changed paths:
A tests/model_inheritance/same_model_name/__init__.py
A tests/model_inheritance/same_model_name/models.py
M tests/model_inheritance/tests.py
R tests/model_inheritance_same_model_name/__init__.py
R tests/model_inheritance_same_model_name/models.py
R tests/model_inheritance_same_model_name/tests.py

  Log Message:
  ---
  Fixed #22402 -- Consolidated model_inheritance tests.

The model_inheritance_same_model_name tests couldn't be run without the
model_inheritance tests. Make the problem go away by merging them.

Thanks timo for the report.


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

Re: [Django] #22451: Migrations do not work with GeoDjango

[Django]

#22451: Migrations do not work with GeoDjango
-+--
 Reporter:  scibi|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by claudep):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Failing test for gis_migrations:
 
https://github.com/claudep/django/commit/d4a46fe075a3bd7e80ac3d7ce93c828d870f636d

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

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

Re: [Django] #22402: Deprecation warnings with model_inheritance

[Django]

#22402: Deprecation warnings with model_inheritance
-+-
 Reporter:  timo |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  app-loading  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 It's a bit of an edge case due to a peculiar test construct. I don't think
 any changes are required in Django.

 We want to test what happens if a model inherits from another model with
 the same name (I guessed that from the name of the test app).

 That requires two models with the same name: the parent and the child.

 But you can't have two models with the same name in the same app, given
 how the app registry works.

 So you need two different apps in INSTALLED_APPS. It doesn't make sense to
 run one without the other.

 The proper fix is to restructure the test:


 - by inheriting from a model found in an application that's in
 ALWAYS_INSTALLED_APPS, or
 - by adding `'model_inheritance'` to ALWAYS_INSTALLED_APPS (which seems
 wrong), or
 - by creating an ad-hoc application and inserting it in tho app registry
 only for the duration of the test.

  by having `'model_inheritance_same_model_name'` add a specific app to
 `INSTALLED_APPS`

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

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

Re: [Django] #22459: Creating model classes for test purposes breaks migrations

[Django]

#22459: Creating model classes for test purposes breaks migrations
--+
 Reporter:  pgcd  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  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
--+
Changes (by claudep):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Note that I was also confronted to this while trying to provide initial
 migrations for contrib.auth app (#22170). I workarounded it by also adding
 a migrations folder in the tests, and specifying `MIGRATION_MODULES` (see
 
https://github.com/claudep/django/commit/05af8e787e22e5fd5894fd1f3069df7a9fd40fc3).

 But It's definitely a realm where a better solution should be provided.

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

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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  tests, test suite  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by yakky):

 Sorry, quite new here: is it possible to remove obsolete attachments?

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

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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  tests, test suite  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by yakky):

 Replying to [comment:8 prestontimmons]:
 > Replying to [comment:2 yakky]:
 > > Test attached
 >
 > yakky, it would help if you submitted this as a single patch.

 Sure.
 Will make the code compliancy modifications and resubmit as single patch

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

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