Re: [Django] #7377: "extends" and "block" tags are not available when constructing template from scratch

[Django]

#7377: "extends" and "block" tags are not available when constructing template
from scratch
-+--
 Reporter:  mgeorge@…|Owner:  melinath
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by anubhav9042):

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


Comment:

 I don't think that this exists anymore in master.

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

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

Re: [Django] #23102: Document change in manage.py sql* --database behavior in 1.7

[Django]

#23102: Document change in manage.py sql* --database behavior in 1.7
--+
 Reporter:  manuel.gysin@…|Owner:  gmunumel
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.7-rc-1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by gmunumel):

 I made the change in release notes for 1.7 version but I cannot get the
 commit working. I followed the
 [https://docs.djangoproject.com/en/1.6/internals/contributing/writing-code
 /working-with-git/ documentation], but on commit I got an error: {{{fatal:
 unable to access 'https://github.com/django/django.git/': The requested
 URL returned error: 403}}}. I'm new on 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/088.2f06eb6dde4db0acd08bf80649e53eae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23110: TransactionManagementError when exception is thrown in django/contrib/sessions/backends/cached_db.py

[Django]

#23110: TransactionManagementError when exception is thrown in
django/contrib/sessions/backends/cached_db.py
-+-
 Reporter:  karthikr |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by karthikr12):

 * cc: karthikr12 (added)
 * needs_better_patch:   => 0
 * 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/066.9d7790714ee8da4b4c38edb3087b109e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23110: TransactionManagementError when exception is thrown in django/contrib/sessions/backends/cached_db.py

[Django]

#23110: TransactionManagementError when exception is thrown in
django/contrib/sessions/backends/cached_db.py
-+
 Reporter:  karthikr |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Cache system)  |Version:  1.6
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I was in the process of upgrading from django 1.5.1 to 1.6.5, and found
 this wierd issue. When I try to access any block of code which accesses
 the request.user object, the transaction.commit() fails because of the
 session. (Session matching query does not exist)


 {{{
 Environment:


 Request Method: GET
 Request URL: http://dev.wnyc.net:9876/in_iframe/accounts/login/

 Django Version: 1.6.5
 Python Version: 2.7.3


 Traceback:
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/django/core/handlers/base.py" in get_response
   137. response = response.render()
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/django/template/response.py" in render
   105. self.content = self.rendered_content
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/django/template/response.py" in rendered_content
   82. content = template.render(context)
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/django/db/transaction.py" in inner
   371. return func(*args, **kwargs)
 File "/home/kravindra/workspace/puppysite/puppy/settings/monkeypatch.py"
 in render
   67. return
 self.template_obj.render_unicode(**context_to_dict(context))
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/mako/template.py" in render_unicode
   198. as_unicode=True)
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/mako/runtime.py" in _render
   403. _render_context(template, callable_, context, *args,
 **_kwargs_for_callable(callable_, data))
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/mako/runtime.py" in _render_context
   434. _exec_template(inherit, lclcontext, args=args,
 kwargs=kwargs)
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/mako/runtime.py" in _exec_template
   457. callable_(context, *args, **kwargs)
 File "/tmp/kravindra/makopuppy/puppysite/base/really_stripped.html.py" in
 render_body
   88. __M_writer(unicode(self.body()))
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/mako/runtime.py" in 
   278. return lambda *args, **kwargs:callable_(self.context,
 *args, **kwargs)
 File "/tmp/kravindra/makopuppy/puppysite/registration/login.html.py" in
 render_body
   72. runtime._include_file(context,
 u'/registration/socialregistration.html', _template_uri)
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/mako/runtime.py" in _include_file
   341. callable_(ctx, **_kwargs_for_include(callable_, context._orig,
 **kwargs))
 File
 "/tmp/kravindra/makopuppy/puppysite/registration/socialregistration.html.py"
 in render_body
   66. __M_writer(unicode(django_template_tag(request,
 template_tag_function, template_path)))
 File "/home/kravindra/workspace/puppysite/puppy/util/templateutils.py" in
 django_template_tag
   30. tag_context =
 Context(dict_=template_tag_function(context_getting_context))
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/socialregistration/templatetags/facebook_tags.py" in
 facebook_button
   15. logged_in = context['request'].user.is_authenticated()
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/django/utils/functional.py" in inner
   213. self._setup()
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/django/utils/functional.py" in _setup
   298. self._wrapped = self._setupfunc()
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/django/contrib/auth/middleware.py" in 
   18. request.user = SimpleLazyObject(lambda: get_user(request))
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/django/contrib/auth/middleware.py" in get_user
   10. request._cached_user = auth.get_user(request)
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/django/contrib/auth/__init__.py" in get_user
   140. user_id = request.session[SESSION_KEY]
 File "/usr/local/virtualenvs/karthik-django165/local/lib/python2.7/site-
 packages/django/contrib/

Re: [Django] #23102: Document change in manage.py sql* --database behavior in 1.7

[Django]

#23102: Document change in manage.py sql* --database behavior in 1.7
--+
 Reporter:  manuel.gysin@…|Owner:  gmunumel
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.7-rc-1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by gmunumel):

 * owner:  nobody => gmunumel
 * 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/088.e6e03947be92a720483ab5cd739ce638%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22979: Move bug* tests

[Django]

#22979: Move bug* tests
--+
 Reporter:  timo  |Owner:  tushar
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Uncategorized |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"df0d5ea7bc9821923c70e7bf06d3646598cf019d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="df0d5ea7bc9821923c70e7bf06d3646598cf019d"
 [1.7.x] Fixed #22979 -- Moved bug* tests

 Backport of 11181a64f 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.5b2339d2d0822d240e2efba33965d195%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] df0d5e: [1.7.x] Fixed #22979 -- Moved bug* tests

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: df0d5ea7bc9821923c70e7bf06d3646598cf019d
  
https://github.com/django/django/commit/df0d5ea7bc9821923c70e7bf06d3646598cf019d
  Author: Tushar Bhatia 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
A tests/admin_autodiscover/__init__.py
A tests/admin_autodiscover/admin.py
A tests/admin_autodiscover/models.py
A tests/admin_autodiscover/tests.py
R tests/bug639/__init__.py
R tests/bug639/models.py
R tests/bug639/test.jpg
R tests/bug639/tests.py
R tests/bug8245/__init__.py
R tests/bug8245/admin.py
R tests/bug8245/models.py
R tests/bug8245/tests.py
M tests/model_forms/models.py
M tests/model_forms/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22979 -- Moved bug* tests

Backport of 11181a64f 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/53d454b120e98_2e521383d34102597%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22979: Move bug* tests

[Django]

#22979: Move bug* tests
--+
 Reporter:  timo  |Owner:  tushar
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Uncategorized |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"11181a64f947236402903deb6fa8c4df7b8bff75"]:
 {{{
 #!CommitTicketReference repository=""
 revision="11181a64f947236402903deb6fa8c4df7b8bff75"
 Fixed #22979 -- Moved bug* 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/062.eeb53446c8b25aaeb140be971641fb2e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 11181a: Fixed #22979 -- Moved bug* tests

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 11181a64f947236402903deb6fa8c4df7b8bff75
  
https://github.com/django/django/commit/11181a64f947236402903deb6fa8c4df7b8bff75
  Author: Tushar Bhatia 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
A tests/admin_autodiscover/__init__.py
A tests/admin_autodiscover/admin.py
A tests/admin_autodiscover/models.py
A tests/admin_autodiscover/tests.py
R tests/bug639/__init__.py
R tests/bug639/models.py
R tests/bug639/test.jpg
R tests/bug639/tests.py
R tests/bug8245/__init__.py
R tests/bug8245/admin.py
R tests/bug8245/models.py
R tests/bug8245/tests.py
M tests/model_forms/models.py
M tests/model_forms/tests.py

  Log Message:
  ---
  Fixed #22979 -- Moved bug* 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/53d4513143bff_331510add4486999%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22887: unique_for_date error message in Field has untranslated param lookup_type

[Django]

#22887: unique_for_date error message in Field has untranslated param 
lookup_type
--+
 Reporter:  Tuttle|Owner:  synasius
 Type:  Bug   |   Status:  closed
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  1
--+

Comment (by gmunumel):

 Hahaha. I finished my patch just to realized that @tuttle already made one
 :S. But at the end it's almost the same as mine.

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

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

[django/django] 30ccb3: [1.7.x] Fixed #23106 -- Updated class-based view r...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 30ccb36cb9c1bc9bd30edb2b67f26ef2a1e4fb53
  
https://github.com/django/django/commit/30ccb36cb9c1bc9bd30edb2b67f26ef2a1e4fb53
  Author: David Hoffman 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M docs/ref/class-based-views/index.txt

  Log Message:
  ---
  [1.7.x] Fixed #23106 -- Updated class-based view reference title.

Backport of f14898a453 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/53d44c1ada529_3194b99d4433052%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23106: Rename API reference page "Class-based views" to "Class-based views API reference"

[Django]

#23106: Rename API reference page "Class-based views" to "Class-based views API
reference"
--+
 Reporter:  jarus |Owner:  dhoffman
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  1
--+

Comment (by Tim Graham ):

 In [changeset:"30ccb36cb9c1bc9bd30edb2b67f26ef2a1e4fb53"]:
 {{{
 #!CommitTicketReference repository=""
 revision="30ccb36cb9c1bc9bd30edb2b67f26ef2a1e4fb53"
 [1.7.x] Fixed #23106 -- Updated class-based view reference title.

 Backport of f14898a453 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/063.2f16ad9d1b385cf5c3abb9abc0e6604b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] a7fe87: [1.6.x] Fixed #23106 -- Updated class-based view r...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: a7fe87bd286fad4b4e6f3a294bda248bb980e900
  
https://github.com/django/django/commit/a7fe87bd286fad4b4e6f3a294bda248bb980e900
  Author: David Hoffman 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M docs/ref/class-based-views/index.txt

  Log Message:
  ---
  [1.6.x] Fixed #23106 -- Updated class-based view reference title.

Backport of f14898a453 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/53d44c197e85d_2a7dbbdd34261b7%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] f14898: Fixed #23106 -- Updated class-based view reference...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f14898a45308c3a46e9a742f7f7ee7869364e95b
  
https://github.com/django/django/commit/f14898a45308c3a46e9a742f7f7ee7869364e95b
  Author: David Hoffman 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M docs/ref/class-based-views/index.txt

  Log Message:
  ---
  Fixed #23106 -- Updated class-based view reference title.


-- 
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/53d44c01978f1_36924a9d407295a%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22718: django.core.files.File doesn't handle certain file-like objects (e.g. zipfile.ZipExtFile)

[Django]

#22718: django.core.files.File doesn't handle certain file-like objects (e.g.
zipfile.ZipExtFile)
--+
 Reporter:  linkjuggler@… |Owner:  mshafiq9
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by anonymous):

 For me (the issue reporter) the only issue was size() failing.  So I
 solved it by wrapping the ZipFile in another class that copied the
 file_size attribute of ZipFile to the _size attribute of the wrapping
 class, and passed through the other file-like interface methods.

 You could simply check for a "file_size" attribute in _get_size(), but I
 agree it's probably not worth it if ZipFile is the only class that causes
 the issue.

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

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

Re: [Django] #23109: Spam on the Community Page

[Django]

#23109: Spam on the Community Page
-+-
 Reporter:  george_edison|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  *.djangoproject.com  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 This is the only spam question on http://djangoforum.com/.

 For now I've just deleted it through the admin.

 I don't know if it's going to come back next time the feed is fetched.

 Let wait and see if it was an isolated incident or if we should remove
 djangoforum.com from the aggregator.

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

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

[Django] #23109: Spam on the Community Page

[Django]

#23109: Spam on the Community Page
-+
 Reporter:  george_edison|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  *.djangoproject.com  |Version:
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Some spam is starting to show up on the "Community" page on the Django
 website:
 https://www.djangoproject.com/community/

 [[Image(http://i.stack.imgur.com/IM4sM.png)]]

-- 
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/056.00b50a50790d462010af7b7c06ba31e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23108: Drop support for PostgreSQL 8.4/PostGIS 1.3, 1.4

[Django]

#23108: Drop support for PostgreSQL 8.4/PostGIS 1.3, 1.4
-+-
   Reporter:  timo   |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component:  Database   |   Keywords:
  layer (models, ORM)|  Has patch:  1
   Severity:  Normal |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 The end of upstream support periods was reached in July 2014 for
 PostgreSQL 8.4. As a consequence, Django 1.8 may set 9.0 as the minimum
 PostgreSQL version it officially supports.

 This also includes dropping support for PostGIS 1.3 and 1.4 as these
 versions are not supported on versions of PostgreSQL later than 8.4.

-- 
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.15349f76d9a8272d76ae06d1985b1f09%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22887: unique_for_date error message in Field has untranslated param lookup_type

[Django]

#22887: unique_for_date error message in Field has untranslated param 
lookup_type
--+
 Reporter:  Tuttle|Owner:  synasius
 Type:  Bug   |   Status:  closed
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  1
--+

Comment (by Tuttle):

 Replying to [comment:9 claudep]:
 > I don't completely exclude having different messages, but I fear
 potential code complexity. Maybe having a patch would help evaluate the
 feasibility.

 Thank you. I think it could be quite terse, offering the patch.
 makemessages not done.

-- 
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.1c17afdb0a197a0933ca487faff08442%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23106: Rename API reference page "Class-based views" to "Class-based views API reference"

[Django]

#23106: Rename API reference page "Class-based views" to "Class-based views API
reference"
--+
 Reporter:  jarus |Owner:  dhoffman
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  1
--+
Changes (by dhoffman):

 * has_patch:  0 => 1


Comment:

 Fixed: https://github.com/django/django/pull/2980

-- 
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.f978aef56544e5315774d96ae057720c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16383: More specific errors when resolving template Variables

[Django]

#16383: More specific errors when resolving template Variables
-+-
 Reporter:  maraujop |Owner:
 Type:  New feature  |  anubhav9042
Component:  Template system  |   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  _resolve_lookup, |   Resolution:
  resolve, template, variable,   | Triage Stage:  Accepted
  exception  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by anubhav9042):

 * needs_tests:  1 => 0


Comment:

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

-- 
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.a108910a7f35e5a558a37b80d3a08da7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23098: ugettext_lazy gets translated too early in modelForm field choices

[Django]

#23098: ugettext_lazy gets translated too early in modelForm field choices
-+-
 Reporter:  magopian |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by magopian):

 Aymeric, I'm sorry that I confused things by talking about the pytest
 usage in the STR, while it actually has nothing to do with the issue. It's
 just that I discovered this issue in this particular case, while it was
 just "failing" (translating to early) silently otherwise.

 As you said, the issue is that the translation is resolved at import time,
 and that's the point of this ticket (hence the title), sorry if I made it
 harder to understand by providing to much (or confusing) details.

-- 
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.b356ca25294071da6f08a4cd28c95455%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23099: Remove usage of deprecated initial data in Django's test suite

[Django]

#23099: Remove usage of deprecated initial data in Django's test suite
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  GIS   |  Version:  master
 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 timo):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/2978 PR]

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

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

Re: [Django] #21792: Form.has_changed is not documented

[Django]

#21792: Form.has_changed is not documented
-+-
 Reporter:  bjb@…|Owner:  navi7
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  has_changed api  | Triage Stage:  Accepted
  ModelForm  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timo):

 I'm not sure we should document `Field._has_changed()`. Methods that start
 with an underscore are generally considered private and not documented.
 Was there any discussion about it besides comment 3 in this ticket?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.4ed43e4d799b90773855104a9fdf2f6e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22404: Make front-end getext catalog available as JSON

[Django]

#22404: Make front-end getext catalog available as JSON
--+-
 Reporter:  ian.morrison.a@…  |Owner:  manologab
 Type:  New feature   |   Status:  assigned
Component:  Translations  |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by manologab):

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


Comment:

 Hi, I've been working with Django for the last few months and I will like
 to contribute with this feature.

 What I propose is a javascript view json_catalog that returns the language
 settings as a json object like this:
 {{{
 {catalog:{
 'translate this':'traduce esto',
 'one plural sample': [
 'un ejemplo de plural',
 'muchos ejemplos de plural'
 ]
 },
 plural: null,
 formats: {
 "DATETIME_FORMAT": "N j, Y, P",
 "DATE_FORMAT": "N j, Y",
 "DECIMAL_SEPARATOR": ".",
 ...
 }
 }}}
 Here is the code:
 [https://github.com/manologab/django/tree/ticket_22404]

 Please let me know if you agree with this approach before going any
 further.

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

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

Re: [Django] #23101: Changing name of M2MField while db_table keeps table name unchanged leads to spurious migration that changes table name

[Django]

#23101: Changing name of M2MField while db_table keeps table name unchanged 
leads
to spurious migration that changes table name
-+-
 Reporter:  maney@…  |Owner:
 Type:  Bug  |  abraham.martin
Component:  Migrations   |   Status:  closed
 Severity:  Release blocker  |  Version:  1.7-rc-1
 Keywords:   |   Resolution:  fixed
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Andrew Godwin ):

 In [changeset:"e1347e9253821a31f9896de9eb993e2376e7398f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e1347e9253821a31f9896de9eb993e2376e7398f"
 Fixed #23101 db_table wasn't copied in deconstruct

 Forward port of 999758fc7a2d6fcb01eb40de937d4420f884788d from
 stable/1.7.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/073.0544f19df15329206731999a4d4584d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] e1347e: Fixed #23101 db_table wasn't copied in deconstruct

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e1347e9253821a31f9896de9eb993e2376e7398f
  
https://github.com/django/django/commit/e1347e9253821a31f9896de9eb993e2376e7398f
  Author: Abraham Martin 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

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

  Log Message:
  ---
  Fixed #23101 db_table wasn't copied in deconstruct

Forward port of 999758fc7a2d6fcb01eb40de937d4420f884788d from
stable/1.7.x


-- 
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/53d3deb1cf74e_347b1365d3433739%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23101: Changing name of M2MField while db_table keeps table name unchanged leads to spurious migration that changes table name

[Django]

#23101: Changing name of M2MField while db_table keeps table name unchanged 
leads
to spurious migration that changes table name
-+-
 Reporter:  maney@…  |Owner:
 Type:  Bug  |  abraham.martin
Component:  Migrations   |   Status:  closed
 Severity:  Release blocker  |  Version:  1.7-rc-1
 Keywords:   |   Resolution:  fixed
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Abraham Martin ):

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


Comment:

 In [changeset:"999758fc7a2d6fcb01eb40de937d4420f884788d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="999758fc7a2d6fcb01eb40de937d4420f884788d"
 Fixed #23101 db_table wasn't copied in deconstruct
 }}}

-- 
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/073.81c9181b46545d9c3cdc5d70cc235c66%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23101: Changing name of M2MField while db_table keeps table name unchanged leads to spurious migration that changes table name

[Django]

#23101: Changing name of M2MField while db_table keeps table name unchanged 
leads
to spurious migration that changes table name
-+-
 Reporter:  maney@…  |Owner:
 Type:  Bug  |  abraham.martin
Component:  Migrations   |   Status:  closed
 Severity:  Release blocker  |  Version:  1.7-rc-1
 Keywords:   |   Resolution:  fixed
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Andrew Godwin ):

 In [changeset:"37f8a83ad050a1040712876002edcbfc0b057603"]:
 {{{
 #!CommitTicketReference repository=""
 revision="37f8a83ad050a1040712876002edcbfc0b057603"
 Merge pull request #2977 from abrahammartin/stable/1.7.x

 Fixed #23101 db_table wasn't copied in deconstruct
 }}}

-- 
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/073.910e0b3c78d0ec340950e5789ab8b2b7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 999758: Fixed #23101 db_table wasn't copied in deconstruct

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 999758fc7a2d6fcb01eb40de937d4420f884788d
  
https://github.com/django/django/commit/999758fc7a2d6fcb01eb40de937d4420f884788d
  Author: Abraham Martin 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

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

  Log Message:
  ---
  Fixed #23101 db_table wasn't copied in deconstruct


  Commit: 37f8a83ad050a1040712876002edcbfc0b057603
  
https://github.com/django/django/commit/37f8a83ad050a1040712876002edcbfc0b057603
  Author: Andrew Godwin 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

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

  Log Message:
  ---
  Merge pull request #2977 from abrahammartin/stable/1.7.x

Fixed #23101 db_table wasn't copied in deconstruct


Compare: https://github.com/django/django/compare/7e708a2536d4...37f8a83ad050

-- 
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/53d3de5394313_3b31f8bd44156e8%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23051: QuerySet.only() fail to work with reverse o2o relationships

[Django]

#23051: QuerySet.only() fail to work with reverse o2o relationships
-+-
 Reporter:  vvd  |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  orm only reverse |  Needs documentation:  0
  relationship OneToOneField |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by nip3o):

 * status:  assigned => new
 * owner:  nip3o =>
 * version:  1.6 => master


Comment:

 I looked in to this, and it seems that at least
 `SQLCompiler.deferred_to_columns` (and all related methods called before
 then) works as intended in this case. However, I will not be able to solve
 this, even if I believe that it should not be unsolvable.

-- 
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.990ad61af105bba1b5dffe48a08fc0b7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23099: Remove usage of deprecated initial data in Django's test suite

[Django]

#23099: Remove usage of deprecated initial data in Django's test suite
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  GIS   |  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):

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


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

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

Re: [Django] #16116: Compress cache data

[Django]

#16116: Compress cache data
-+-
 Reporter:  bjourne  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Cache system)  |  Version:  1.3
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by timo):

 If you disagree with a "won't fix" decision, please open a thread on the
 DevelopersMailingList. Are those requesting this using a 3rd party
 implementation that has gained widespread use as Russ asked? I think the
 idea is fine and note #20892 which is another ticket asking for a way to
 pass options to the memcache backend.

-- 
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.ebf95ec750243f42ca35936b9320a631%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23102: Document change in manage.py sql* --database behavior in 1.7 (was: SQL-Management does not work with DATABASE_ROUTERS set)

[Django]

#23102: Document change in manage.py sql* --database behavior in 1.7
--+
 Reporter:  manuel.gysin@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7-rc-1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted
 * component:  Core (Management commands) => Documentation


Comment:

 The new behavior makes sense to me. I think we should clarify the
 documentation and add a note about it in the 1.7 release notes.

-- 
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/088.f4d236105030445e7e6dedb1abf13869%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17638: Link up topic guides with API reference

[Django]

#17638: Link up topic guides with API reference
--+
 Reporter:  oinopion  |Owner:  jarus
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 The idea was to do this for all pages that have both topic and ref docs,
 not just for class based views.

-- 
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.c49c65fdb13f11b1459a016854bbad84%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22944: Migrate doesn't like ForeignKey being reassigned to a different app's model

[Django]

#22944: Migrate doesn't like ForeignKey being reassigned to a different app's 
model
-+
 Reporter:  mozumder@…   |Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Andrew Godwin ):

 In [changeset:"7e708a2536d4828d06f7aa4002fbd5cfc20bef16"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7e708a2536d4828d06f7aa4002fbd5cfc20bef16"
 [1.7.x] Fixed #22944: Bad dependency on FK alteration in autodetector
 }}}

-- 
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/081.cd8d2565002efc20ee754fe470f29a22%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 805774: Fixed #22944: Bad dependency on FK alteration in a...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 805774df1f2ec9552f1d9c826f5ca9276684da11
  
https://github.com/django/django/commit/805774df1f2ec9552f1d9c826f5ca9276684da11
  Author: Andrew Godwin 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M tests/migrations/test_autodetector.py

  Log Message:
  ---
  Fixed #22944: Bad dependency on FK alteration in autodetector


-- 
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/53d3d5c0461d0_2948b2dd38648d8%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22944: Migrate doesn't like ForeignKey being reassigned to a different app's model

[Django]

#22944: Migrate doesn't like ForeignKey being reassigned to a different app's 
model
-+
 Reporter:  mozumder@…   |Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"805774df1f2ec9552f1d9c826f5ca9276684da11"]:
 {{{
 #!CommitTicketReference repository=""
 revision="805774df1f2ec9552f1d9c826f5ca9276684da11"
 Fixed #22944: Bad dependency on FK alteration in autodetector
 }}}

-- 
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/081.215997b6b9ce59c1aea6747c677ee123%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 7e708a: [1.7.x] Fixed #22944: Bad dependency on FK alterat...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 7e708a2536d4828d06f7aa4002fbd5cfc20bef16
  
https://github.com/django/django/commit/7e708a2536d4828d06f7aa4002fbd5cfc20bef16
  Author: Andrew Godwin 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M tests/migrations/test_autodetector.py

  Log Message:
  ---
  [1.7.x] Fixed #22944: Bad dependency on FK alteration in autodetector


-- 
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/53d3d5cc1e6c8_36924a9d4070352%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23102: SQL-Management does not work with DATABASE_ROUTERS set

[Django]

#23102: SQL-Management does not work with DATABASE_ROUTERS set
-+-
 Reporter:  manuel.gysin@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.7-rc-1
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by areski):

 It's definitely a change of behaviour in Django 1.7.

 In 1.7 we read the models from router.get_migratable_models:
 https://github.com/django/django/blob/master/django/core/management/sql.py#L45
 in 1.6 we read the models from models.get_models:
 https://github.com/django/django/blob/1.6.5/django/core/management/sql.py

 I'm not sure what's the desired implementation for 1.7

-- 
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/088.4f26e31d0299ae8398b9f6cb73cd6203%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13749: Link from admin-site to site

[Django]

#13749: Link from admin-site to site
-+-
 Reporter:  romankrv |Owner:  joelklabo
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin url dceu2011   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  1
-+-

Comment (by claudep):

 No need for a ticket, if the string is marked for translation (with
 `trans`), the traditional translation workflow will take care of it.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.ce41b5c996e4bda7c3d195300a8140d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23107: --no-color option won't work for output of runserver command

[Django]

#23107: --no-color option won't work for output of runserver command
-+-
 Reporter:  hirokiky |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.7-rc-1
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by hirokiky):

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


Comment:

 Attached a patch to fix the behaviour.
 I'll try to write tests and send PR (after Accepted).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.30bb542fe6e34f36066a1393c697772d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23107: --no-color option won't work for output of runserver command

[Django]

#23107: --no-color option won't work for output of runserver command
-+-
 Reporter:  hirokiky |Owner:  hirokiky
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.7-rc-1
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by hirokiky):

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


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

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

Re: [Django] #23060: UnicodeDecodeError in debug templatetag

[Django]

#23060: UnicodeDecodeError in debug templatetag
-+
 Reporter:  anonymous|Owner:  qingfeng
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+

Comment (by Claude Paroz ):

 In [changeset:"3a2badcbb73c2aed6451d2451da1c4fc8d934ab2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3a2badcbb73c2aed6451d2451da1c4fc8d934ab2"
 [1.7.x] Fixed #23060 -- Prevented UnicodeDecodeError in debug templatetag

 Backport of 08451f17d0 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/067.fdbc69a590b76306a919441b53528be6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 3a2bad: [1.7.x] Fixed #23060 -- Prevented UnicodeDecodeErr...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 3a2badcbb73c2aed6451d2451da1c4fc8d934ab2
  
https://github.com/django/django/commit/3a2badcbb73c2aed6451d2451da1c4fc8d934ab2
  Author: qingfeng 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M django/template/defaulttags.py
M tests/template_tests/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #23060 -- Prevented UnicodeDecodeError in debug templatetag

Backport of 08451f17d0 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/53d3d18e74766_303b4d1d401005df%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 08451f: Fixed #23060 -- Prevented UnicodeDecodeError in de...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 08451f17d08486055542daecdcc3be1779f0815b
  
https://github.com/django/django/commit/08451f17d08486055542daecdcc3be1779f0815b
  Author: qingfeng 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M django/template/defaulttags.py
M tests/template_tests/tests.py

  Log Message:
  ---
  Fixed #23060 -- Prevented UnicodeDecodeError in debug templatetag


-- 
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/53d3d1528c3ad_37371421d40161d%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23060: UnicodeDecodeError in debug templatetag

[Django]

#23060: UnicodeDecodeError in debug templatetag
-+
 Reporter:  anonymous|Owner:  qingfeng
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"08451f17d08486055542daecdcc3be1779f0815b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="08451f17d08486055542daecdcc3be1779f0815b"
 Fixed #23060 -- Prevented UnicodeDecodeError in debug templatetag
 }}}

-- 
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.f8aab2d3083eeb574009eac9948afb0d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23101: Changing name of M2MField while db_table keeps table name unchanged leads to spurious migration that changes table name

[Django]

#23101: Changing name of M2MField while db_table keeps table name unchanged 
leads
to spurious migration that changes table name
-+-
 Reporter:  maney@…  |Owner:
 Type:  Bug  |  abraham.martin
Component:  Migrations   |   Status:  assigned
 Severity:  Release blocker  |  Version:  1.7-rc-1
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by abraham.martin):

 * owner:  nobody => abraham.martin
 * 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/073.93230ffc5ab9761a685616120d5eb3c7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23055: Filters don't use ModelAdmin get_queryset()

[Django]

#23055: Filters don't use ModelAdmin get_queryset()
-+-
 Reporter:  ramiro   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin filters| Triage Stage:  Accepted
  list_filter multi-db get_queryset  |  Needs documentation:  0
  modeladmin |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by synasius):

 Hi ramiro,

 I'm trying to reproduce the issue but I can't. Can you help me?

 This is my current setup: I have a `foo` application with just one `Stuff`
 model

 {{{
 #!python
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
 },
 'other': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': os.path.join(BASE_DIR, 'other.sqlite3'),
 },
 }

 DATABASE_ROUTERS = ['help.routers.FooRouter']
 }}}

 and that's my ModelAdmin

 {{{
 #!python
 class MultiDBModelAdmin(admin.ModelAdmin):
 # A handy constant for the name of the alternate database.
 using = 'other'

 def get_queryset(self, request):
 # Tell Django to look for objects on the 'other' database.
 return super(MultiDBModelAdmin,
 self).get_queryset(request).using(self.using)

 # Register your models here.
 class StuffAdmin(MultiDBModelAdmin):
 list_filter = ("empty",)
 }}}

 The router is used to create the `foo_stuff` table only in the `other` db.

-- 
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.5303cedf9f2ccfe0b923c4313a221910%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23099: Remove usage of deprecated initial data in Django's test suite

[Django]

#23099: Remove usage of deprecated initial data in Django's test suite
--+
 Reporter:  timo  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  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 andrewgodwin):

 +1 on moving the initial data to normal test fixtures.

-- 
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.bf4f6b6977ca648835132044c2a2a2df%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23106: Rename API reference page "Class-based views" to "Class-based views API reference"

[Django]

#23106: Rename API reference page "Class-based views" to "Class-based views API
reference"
--+
 Reporter:  jarus |Owner:  dhoffman
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  1
--+
Changes (by dhoffman):

 * owner:  nobody => dhoffman
 * 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.87a2e76d6479dbec27f4bbc8f9b1de64%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23060: UnicodeDecodeError in debug templatetag

[Django]

#23060: UnicodeDecodeError in debug templatetag
-+
 Reporter:  anonymous|Owner:  qingfeng
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+

Comment (by qingfeng):

 @claudep send a new pr https://github.com/django/django/pull/2976 , pls,
 review, thanks

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

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

[Django] #23107: --no-color option won't work for output of runserver command

[Django]

#23107: --no-color option won't work for output of runserver command
+--
 Reporter:  hirokiky|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Core (Management commands)  |Version:  1.7-rc-1
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+--
 The `--no-color` option won't work for output of runserver command.

 {{{
 python manage.py runserver --no-color
 ...

 [26/Jul/2014 15:01:07] "GET / HTTP/1.1" 500 85001  # Colored
 }}}

 Ticket for `--no-color` feature did not include about WSGIServer
 https://code.djangoproject.com/ticket/19877
 And, output of the WSGIServer will be colorized.
 (actually output of the management command won't be colorized).

-- 
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.37bc8f11397cab465912f8cc3036d961%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18480: Inherited model fails to handle blank field properly

[Django]

#18480: Inherited model fails to handle blank field properly
-+-
 Reporter:  yuval_a  |Owner:  navi7
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by navi7):

 * owner:  nobody => navi7
 * 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/065.18009ffdad3cb83af66c7b9b2c14ba08%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23105: Cosmetic change on lru_cache backport

[Django]

#23105: Cosmetic change on lru_cache backport
-+-
 Reporter:  areski   |Owner:  areski
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  lru_cache|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bmispelon):

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


Comment:

 I don't think that change is worth it.

 We've already dropped support for Python 2.6 and eventually, we'll also
 drop support for 2.7, at which point we'll be able to delete that file
 altogether.

 Marking this as `wontfix` consequently.

-- 
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.581b228b035596ea35a0d028a8264576%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23051: QuerySet.only() fail to work with reverse o2o relationships

[Django]

#23051: QuerySet.only() fail to work with reverse o2o relationships
-+-
 Reporter:  vvd  |Owner:  nip3o
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  orm only reverse |  Needs documentation:  0
  relationship OneToOneField |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by nip3o):

 Failing test:

 {{{

diff --git a/tests/defer_regress/tests.py
 b/tests/defer_regress/tests.py
 index 63f9e97..5d70da2 100644
 --- a/tests/defer_regress/tests.py
 +++ b/tests/defer_regress/tests.py
 @@ -144,6 +144,18 @@ class DeferRegressionTest(TestCase):
 list(SimpleItem.objects.annotate(Count('feature')).only('name')),
  list)

 +def test_ticket_23051(self):
 +item = Item.objects.create(value=1, name='item')
 +OneToOneItem.objects.create(item=item, name='one_to_one_item')
 +
 +obj = Item.objects.only('name',
 'one_to_one_item__name').get(name='item')
 +
 +with self.assertNumQueries(0):
 +self.assertEqual(obj.name, 'item')
 +
 +with self.assertNumQueries(0):
 +self.assertEqual(obj.one_to_one_item.name, 'one_to_one_item')
 +
  def test_only_and_defer_usage_on_proxy_models(self):
  # Regression for #15790 - only() broken for proxy models
  proxy = Proxy.objects.create(name="proxy", value=42)

 }}}

-- 
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.85c4c017a95a7db3d27f318c0c99294b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17638: Link up topic guides with API reference

[Django]

#17638: Link up topic guides with API reference
--+
 Reporter:  oinopion  |Owner:  jarus
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by jarus):

 * has_patch:  0 => 1


Comment:

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

-- 
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.92a8eadea7e7b958ea472bef492de035%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17638: Link up topic guides with API reference

[Django]

#17638: Link up topic guides with API reference
--+
 Reporter:  oinopion  |Owner:  jarus
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by jarus):

 See also #23106

-- 
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.4ac160d179c18e77f276fe6aafab3cdb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23051: QuerySet.only() fail to work with reverse o2o relationships

[Django]

#23051: QuerySet.only() fail to work with reverse o2o relationships
-+-
 Reporter:  vvd  |Owner:  nip3o
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  orm only reverse |  Needs documentation:  0
  relationship OneToOneField |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by nip3o):

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


Comment:

 Will try to at least make a test for this during EP14.

-- 
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.f69523eb5cd9201cd775ef9905518acd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22718: django.core.files.File doesn't handle certain file-like objects (e.g. zipfile.ZipExtFile)

[Django]

#22718: django.core.files.File doesn't handle certain file-like objects (e.g.
zipfile.ZipExtFile)
--+
 Reporter:  linkjuggler@… |Owner:  mshafiq9
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by mshafiq9):

 Digged down in this issue on EuroPython 2014 Django Sprint, and If I break
 the `zfile = File(zip.open("dir/file.txt")` as below

 {{{
 opened_zip_file = zip.open("dir/file.txt")
 zfile = File(opened_zip_file)
 }}}

 and inspect on the `opened_zip_file` its an instance of `class
 ZipExtFile(io.BufferedIOBase):`
 http://hg.python.org/cpython/file/2.7/Lib/zipfile.py#l501 which being
 `file-like object` do not support seek interface on this file instance
 (also return `False` if you check `opened_zip_file.seekable()`).

 1 - If we want to improve the `python zipfile library` to support this
 interface (if necessary?) the correct fix should be done by cpython.

 2 - I don't see a practical example of this happening (to send `file-like`
 objects directly to django `FileField`) without being involved a user's
 custom logic, so I think this is an individual user's problem (not
 Django's) to solve it by using some trick / extracting zip file in `/tmp`
 directory of server or something like this. ***I think some core django
 developer (if agreed?) please mark this ticket as invalid and close it.***

 3 - Another peer sitting around suggested to develop a `ZipFileField` but
 I think I don't see any usage of it currently! (if someone need it please
 define some standard usage, interfaces, and examples and ask for a new
 feature ticket and I will appreciate if you place the link of the new
 ticket here if you do so! I might pick that one later).

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

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

Re: [Django] #23067: Update docs to use django-admin instead of django-admin.py

[Django]

#23067: Update docs to use django-admin instead of django-admin.py
-+-
 Reporter:  timo |Owner:  jarus
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.7-rc-1
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by areski):

 Reviewed, looks good to me!

-- 
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.749b4e023e332b92afc9edba5a5dd21c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23067: Update docs to use django-admin instead of django-admin.py

[Django]

#23067: Update docs to use django-admin instead of django-admin.py
-+-
 Reporter:  timo |Owner:  jarus
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.7-rc-1
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by areski):

 * stage:  Unreviewed => 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/062.7d55e57ce2c55afa62ebb163f1f1964e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16116: Compress cache data

[Django]

#16116: Compress cache data
-+-
 Reporter:  bjourne  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Cache system)  |  Version:  1.3
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by the_drow):

 I also disagree.
 There is no reason not to support it.
 Both python-memcached and pylibmc do support it if zlib is available.
 Why shouldn't it be opt-in if required?

-- 
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.61a6e7ca27698376675d23adbb3ba035%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22873: Rename BaseDatabaseWrapper.use_debug_cursor to force_debug_cursor

[Django]

#22873: Rename BaseDatabaseWrapper.use_debug_cursor to force_debug_cursor
-+-
 Reporter:  john@…   |Owner:  anonymous
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"90faa196f67863370a4682ecfd053e189cd46705"]:
 {{{
 #!CommitTicketReference repository=""
 revision="90faa196f67863370a4682ecfd053e189cd46705"
 Fixed #22873 -- Renamed use_debug_cursor to force_debug_cursor to clarify
 the behavior.
 }}}

-- 
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.7b4aa66c88ee640cf0eabad93443fde5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 90faa1: Fixed #22873 -- Renamed use_debug_cursor to force_...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 90faa196f67863370a4682ecfd053e189cd46705
  
https://github.com/django/django/commit/90faa196f67863370a4682ecfd053e189cd46705
  Author: areski 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M django/db/backends/__init__.py
M django/test/utils.py

  Log Message:
  ---
  Fixed #22873 -- Renamed use_debug_cursor to force_debug_cursor to clarify the 
behavior.


-- 
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/53d3bd9647014_257e7c5d4428251%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23106: Rename API reference page "Class-based views" to "Class-based views API reference"

[Django]

#23106: Rename API reference page "Class-based views" to "Class-based views API
reference"
--+
 Reporter:  jarus |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  1
--+
Changes (by timo):

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


Comment:

 I would call it "Class-based views API" for consistency with others pages
 like "The Forms API" and since it's a bit shorter without losing clarity.

-- 
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.0198c4fcc9abdc95de89d4f9eddad0f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22873: Rename BaseDatabaseWrapper.use_debug_cursor to force_debug_cursor (was: Allow disabling debug cursor when DEBUG=True)

[Django]

#22873: Rename BaseDatabaseWrapper.use_debug_cursor to force_debug_cursor
-+-
 Reporter:  john@…   |Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by timo):

 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => 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/080.614cfd506752c2bdd00ec9d2fd35be86%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23105: Cosmetic change on lru_cache backport

[Django]

#23105: Cosmetic change on lru_cache backport
-+-
 Reporter:  areski   |Owner:  areski
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  lru_cache|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by areski):

 It actually fix compatibility with Python2.6:
 http://code.activestate.com/recipes/578078-py26-and-py30-backport-of-
 python-33s-lru-cache/#c3

 But as Python2.6 support is dropped in Django 1.7, this doesnt give any
 value

-- 
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.485ae3f71d12541252d6df018f09b92a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23106: Rename API reference page "Class-based views" to "Class-based views API reference"

[Django]

#23106: Rename API reference page "Class-based views" to "Class-based views API
reference"
--+
 Reporter:  jarus |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  1
--+
 Currently there are two pages called "Class-based views".

 [https://docs.djangoproject.com/en/1.7/topics/class-based-views/ Topic
 page]
 [https://docs.djangoproject.com/en/1.7/ref/class-based-views/ API
 reference]

 Also a google search for "django class-based views" is very confusing.
 
[[Image(https://files.thelabmill.de/shuttle/Screen%20Shot%202014-07-26%20at%2016.18.12-GLZOcWCUbs.png)]]

 I would propose to rename the API page into "Class-based views API
 reference". A possible problem is that the version choicer isn't able
 anymore to switch through the version in the API reference overview page.


 See also #17638.

-- 
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.b1156fb59303c993d84b75d89bdc8852%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22553: Add ability to refresh queryset

[Django]

#22553: Add ability to refresh queryset
-+-
 Reporter:  giggaflop@…  |Owner:  dhoffman
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6d5daa30cf29d0bada0586213ecb2959152566b4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6d5daa30cf29d0bada0586213ecb2959152566b4"
 Fixed #22553 -- Added refreshing queryset info to docs.
 }}}

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

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

[django/django] e3a993: [1.6.x] Fixed #22553 -- Added refreshing queryset ...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: e3a99357cba5085f5ae937920529292edafc5c7a
  
https://github.com/django/django/commit/e3a99357cba5085f5ae937920529292edafc5c7a
  Author: David Hoffman 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

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

  Log Message:
  ---
  [1.6.x] Fixed #22553 -- Added refreshing queryset info to docs.

Backport of 6d5daa30cf 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/53d3baec46d08_1d235c9d3880748%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22553: Add ability to refresh queryset

[Django]

#22553: Add ability to refresh queryset
-+-
 Reporter:  giggaflop@…  |Owner:  dhoffman
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"e3a99357cba5085f5ae937920529292edafc5c7a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e3a99357cba5085f5ae937920529292edafc5c7a"
 [1.6.x] Fixed #22553 -- Added refreshing queryset info to docs.

 Backport of 6d5daa30cf 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/077.46910ba40f3a6fb13737b080f68127a7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 1ef544: [1.7.x] Fixed #22553 -- Added refreshing queryset ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 1ef544f91f0d4be3f44ae7fd0498530e57a9b160
  
https://github.com/django/django/commit/1ef544f91f0d4be3f44ae7fd0498530e57a9b160
  Author: David Hoffman 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

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

  Log Message:
  ---
  [1.7.x] Fixed #22553 -- Added refreshing queryset info to docs.

Backport of 6d5daa30cf 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/53d3baec46e38_202da27d44563e7%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22553: Add ability to refresh queryset

[Django]

#22553: Add ability to refresh queryset
-+-
 Reporter:  giggaflop@…  |Owner:  dhoffman
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"1ef544f91f0d4be3f44ae7fd0498530e57a9b160"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1ef544f91f0d4be3f44ae7fd0498530e57a9b160"
 [1.7.x] Fixed #22553 -- Added refreshing queryset info to docs.

 Backport of 6d5daa30cf 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/077.2e1498156bdbdc5f30972953694f1427%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 6d5daa: Fixed #22553 -- Added refreshing queryset info to ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6d5daa30cf29d0bada0586213ecb2959152566b4
  
https://github.com/django/django/commit/6d5daa30cf29d0bada0586213ecb2959152566b4
  Author: David Hoffman 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

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

  Log Message:
  ---
  Fixed #22553 -- Added refreshing queryset info to docs.


-- 
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/53d3bad6e8342_26f8939d3877898%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23102: SQL-Management does not work with DATABASE_ROUTERS set

[Django]

#23102: SQL-Management does not work with DATABASE_ROUTERS set
-+-
 Reporter:  manuel.gysin@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.7-rc-1
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 Hello

 No it have nothing to do with the setting itself.
 There is a different behavior between Django 1.6 and 1.7.

 This gives no output, because SampleModel in the second_db.
 {{{
 [mgysin@localhost Demo]$ python manage.py sqlall SampleModel
 [mgysin@localhost Demo]$
 }}}

 Adjusting the command with --database argument, get things working again:

 {{{
 [mgysin@localhost Demo]$ python manage.py sqlall SampleModel
 --database=second_db
 BEGIN;
 CREATE TABLE "SampleModel_location" (
 "id" integer NOT NULL PRIMARY KEY AUTOINCREMENT,
 "name" varchar(50) NOT NULL
 )
 ;

 COMMIT;
 }}}

 I'm not sure if this is a design decision or just some side effect with
 Django 1.7.
 But it is very confusing if you are not aware of that. Maybe something
 like 'Only models in the default database are used, for other databases
 please provide --database argument' should be printed?

 I've added an demo sample with this behavior.

-- 
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/088.fbbd74be17bfffc881f809e55f413892%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22553: Add ability to refresh queryset

[Django]

#22553: Add ability to refresh queryset
-+-
 Reporter:  giggaflop@…  |Owner:  dhoffman
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Looks good. Don't forget to check "Has patch" so the ticket appears in the
 review queue. Thanks!

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

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

Re: [Django] #23105: Cosmetic change on lru_cache backport

[Django]

#23105: Cosmetic change on lru_cache backport
-+-
 Reporter:  areski   |Owner:  areski
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  lru_cache|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by areski):

 It's likely that Raymond Hettinger won't be supporting this code from the
 Activestate website.
 The code has been ported unchanged to bitbucket by a different user, this
 may change if someone come with some optimization or bugs fix, but it is
 not the case so far.

 Feel free to close the ticket if it's irrelevant or if it doesn't improve
 Django code readability.

-- 
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.b9720899a3b9b394471fdf766133c3cf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22718: django.core.files.File doesn't handle certain file-like objects (e.g. zipfile.ZipExtFile)

[Django]

#22718: django.core.files.File doesn't handle certain file-like objects (e.g.
zipfile.ZipExtFile)
--+
 Reporter:  linkjuggler@… |Owner:  mshafiq9
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by mshafiq9):

 * owner:  nobody => mshafiq9
 * 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/079.8437ea00406999371fe22a10a9f5451d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18586: Rewrite unit tests migrated from doctests

[Django]

#18586: Rewrite unit tests migrated from doctests
--+
 Reporter:  konk  |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  unit tests| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

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


-- 
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.0e2e279d5457e3e654a866e1c1a2b892%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22553: Add ability to refresh queryset

[Django]

#22553: Add ability to refresh queryset
---+
 Reporter:  giggaflop@…|Owner:  dhoffman
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by dhoffman):

 Completed: https://github.com/django/django/pull/2974

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

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

[django/django] 5cdb8f: Fixed #16617 -- Added 'value' to BaseValidator par...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5cdb8f8c1ea7161ca9e3b702ec7cdd7e3cd0999a
  
https://github.com/django/django/commit/5cdb8f8c1ea7161ca9e3b702ec7cdd7e3cd0999a
  Author: Anubhav Joshi 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M django/core/validators.py
M docs/ref/validators.txt
M tests/forms_tests/tests/test_error_messages.py
M tests/validators/tests.py

  Log Message:
  ---
  Fixed #16617 -- Added 'value' to BaseValidator params.

Also allowed overriding the default messages in subclasses of BaseValidator.

Thanks sperrygrove for initial patch.


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

Re: [Django] #16617: URLField with min_length or max_length reports wrong length in validation messages

[Django]

#16617: URLField with min_length or max_length reports wrong length in 
validation
messages
-+-
 Reporter:  frasern  |Owner:  anubhav9042
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5cdb8f8c1ea7161ca9e3b702ec7cdd7e3cd0999a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5cdb8f8c1ea7161ca9e3b702ec7cdd7e3cd0999a"
 Fixed #16617 -- Added 'value' to BaseValidator params.

 Also allowed overriding the default messages in subclasses of
 BaseValidator.

 Thanks sperrygrove for initial 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/065.30c05e9009ccd687992e37dc03cc36dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23105: Cosmetic change on lru_cache backport

[Django]

#23105: Cosmetic change on lru_cache backport
-+-
 Reporter:  areski   |Owner:  areski
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  lru_cache|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by bmispelon):

 What new features or bug fixes are we missing by using the "old" version?

 From what I can tell, the original version was authored by Raymond
 Hettinger (who wrote the original implementation) whereas this repository
 is maintained by another person. How are the two projects related?

-- 
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.e13a18df95a9299da77a6747ce63%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23103: Add Link To "Writing your first patch for Django" Into "Contributing to Django" Documentation Page

[Django]

#23103: Add Link To "Writing your first patch for Django" Into "Contributing to
Django" Documentation Page
-+-
 Reporter:  petraszd |Owner:  petraszd
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5a311d2ccc48cb3a89858c92e449ffbfd9cbfb00"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5a311d2ccc48cb3a89858c92e449ffbfd9cbfb00"
 Fixed #23103 -- Added contributing tutorial link to contributing index.
 }}}

-- 
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.dafeab96a15b5af06d7cd17ad329dad1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23105: Cosmetic change on lru_cache backport

[Django]

#23105: Cosmetic change on lru_cache backport
-+-
 Reporter:  areski   |Owner:  areski
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Utilities|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  lru_cache|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by areski):

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


Comment:

 PR: https://github.com/django/django/pull/2973

-- 
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.6367b4e19cab75954b87750460625637%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 5a311d: Fixed #23103 -- Added contributing tutorial link t...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5a311d2ccc48cb3a89858c92e449ffbfd9cbfb00
  
https://github.com/django/django/commit/5a311d2ccc48cb3a89858c92e449ffbfd9cbfb00
  Author: Petras Zdanavičius 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M docs/internals/contributing/index.txt
M docs/internals/contributing/writing-code/submitting-patches.txt

  Log Message:
  ---
  Fixed #23103 -- Added contributing tutorial link to contributing index.


-- 
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/53d3b21758573_2d2891fd3436530%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17638: Link up topic guides with API reference

[Django]

#17638: Link up topic guides with API reference
--+
 Reporter:  oinopion  |Owner:  jarus
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by jarus):

 * owner:  anonymous => jarus
 * type:  New feature => Cleanup/optimization


Comment:

 There was no action since 4 months, I hope it's okay that I adopt this
 ticket.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.127a11721a540fbf5e3ac72bf9e107c9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23105: Cosmetic change on lru_cache backport

[Django]

#23105: Cosmetic change on lru_cache backport
--+---
 Reporter:  areski|  Owner:  areski
 Type:  Cleanup/optimization  | Status:  new
Component:  Utilities |Version:  master
 Severity:  Normal|   Keywords:  lru_cache
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+---
 A backport for lru_cache has been imported to Django:
 https://github.com/django/django/blob/master/django/utils/lru_cache.py
 Unfortunately when importing it, we added an non-necessary extra indent.

 FYI, lru_cache last backport is now
 https://bitbucket.org/jaraco/backports.functools_lru_cache/

 To improve the code style, I moved the backport to a separate file, that
 way the code will be cleaner and it will be easier to keep in sync with
 the original code on bitbucket.

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

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

[django/django] ddf2b7: [1.7.x] Fixed #22305 -- Added note to docs about U...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: ddf2b7d96b1048b1210d2315d92275496352ccaf
  
https://github.com/django/django/commit/ddf2b7d96b1048b1210d2315d92275496352ccaf
  Author: Niclas Olofsson 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M docs/ref/databases.txt

  Log Message:
  ---
  [1.7.x] Fixed #22305 -- Added note to docs about UTF8 database requirement.

Backport of 08b85de9b7 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/53d3afd7a608c_36f4a8fd40810ea%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22305: MaxLengthValidator doesn't take database encoding into account

[Django]

#22305: MaxLengthValidator doesn't take database encoding into account
--+
 Reporter:  joeri |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"1c714c18d22a38ad2dca696ca8bc4201cc3da131"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1c714c18d22a38ad2dca696ca8bc4201cc3da131"
 [1.6.x] Fixed #22305 -- Added note to docs about UTF8 database
 requirement.

 Backport of 08b85de9b7 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/063.7095b5d419db3335fc55f2f00f1cd5a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22305: MaxLengthValidator doesn't take database encoding into account

[Django]

#22305: MaxLengthValidator doesn't take database encoding into account
--+
 Reporter:  joeri |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"08b85de9b7a8940702dba9348b642538da888c6c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="08b85de9b7a8940702dba9348b642538da888c6c"
 Fixed #22305 -- Added note to docs about UTF8 database requirement.
 }}}

-- 
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.6a45bdb0704117845037d55c9888e55f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 1c714c: [1.6.x] Fixed #22305 -- Added note to docs about U...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 1c714c18d22a38ad2dca696ca8bc4201cc3da131
  
https://github.com/django/django/commit/1c714c18d22a38ad2dca696ca8bc4201cc3da131
  Author: Niclas Olofsson 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M docs/ref/databases.txt

  Log Message:
  ---
  [1.6.x] Fixed #22305 -- Added note to docs about UTF8 database requirement.

Backport of 08b85de9b7 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/53d3afd7b0540_1e28b19d3846234%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22305: MaxLengthValidator doesn't take database encoding into account

[Django]

#22305: MaxLengthValidator doesn't take database encoding into account
--+
 Reporter:  joeri |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"ddf2b7d96b1048b1210d2315d92275496352ccaf"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ddf2b7d96b1048b1210d2315d92275496352ccaf"
 [1.7.x] Fixed #22305 -- Added note to docs about UTF8 database
 requirement.

 Backport of 08b85de9b7 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/063.883e5ce35df8bd576763a54308d2694e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 08b85d: Fixed #22305 -- Added note to docs about UTF8 data...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 08b85de9b7a8940702dba9348b642538da888c6c
  
https://github.com/django/django/commit/08b85de9b7a8940702dba9348b642538da888c6c
  Author: Niclas Olofsson 
  Date:   2014-07-26 (Sat, 26 Jul 2014)

  Changed paths:
M docs/ref/databases.txt

  Log Message:
  ---
  Fixed #22305 -- Added note to docs about UTF8 database requirement.


-- 
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/53d3afbd851d3_303dbebd3813782%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23098: ugettext_lazy gets translated too early in modelForm field choices

[Django]

#23098: ugettext_lazy gets translated too early in modelForm field choices
-+-
 Reporter:  magopian |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Mmm, regardless, if the translation is resolved at import time, that's
 bad. We should at least fix 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/066.64f0aa72aea539de8a01bc50e3beb700%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18682: Make the deletion of stale content types safer

[Django]

#18682: Make the deletion of stale content types safer
--+
 Reporter:  aaugustin |Owner:  speijnik
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.contenttypes  |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by speijnik):

 * has_patch:  0 => 1


Comment:

 Just attached the patch.

 Formatting is obviously up for discussion and probably not optimal.

 Example:

 {{{
 The following content types are stale and need to be deleted:

 app | a
   - auth | permission objects to be deleted: 3
   - app | genericrel objects to be deleted: 26
 }}}

-- 
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.cae116155e653e3a8ef6398d002d5aaa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #10935: forms.ImageField.clean should annotate the object returned by FileField.clean

[Django]

#10935: forms.ImageField.clean should annotate the object returned by
FileField.clean
--+
 Reporter:  jdunck|Owner:  petraszd
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by petraszd):

 * needs_docs:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.27bd9f39e2cda4daf754ffea7b7196eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22887: unique_for_date error message in Field has untranslated param lookup_type

[Django]

#22887: unique_for_date error message in Field has untranslated param 
lookup_type
--+
 Reporter:  Tuttle|Owner:  synasius
 Type:  Bug   |   Status:  closed
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  1
--+

Comment (by claudep):

 I don't completely exclude having different messages, but I fear potential
 code complexity. Maybe having a patch would help evaluate the feasibility.

-- 
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.35ddb3ffac019d4eb59e61730c3d0a5b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23098: ugettext_lazy gets translated too early in modelForm field choices

[Django]

#23098: ugettext_lazy gets translated too early in modelForm field choices
-+-
 Reporter:  magopian |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:  invalid
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 This report seems invalid to me. The reproduction instructions include:

 > import the ModelForm from an external script that has the settings
 configured, but not called django.setup() yet

 But the 1.7 release notes explain that you should call `django.setup()`
 before doing anything 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/066.4f0c63c58edf2203478590c380c1f81b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.