Re: [Django] #3371: Filter to get dict's value by key name (for the purpose of enabling variable lookups in the template) (was: Filter to get dict's value by key name)

[Django]

#3371: Filter to get dict's value by key name (for the purpose of enabling
variable lookups in the template)
-+-
 Reporter:  Alex Dedul   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  template filter  | Triage Stage:
  dict key   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by anonymous):

 * status:  closed => new
 * severity:   => Normal
 * resolution:  wontfix =>
 * easy:   => 1
 * ui_ux:   => 0
 * type:   => New feature
 * stage:  Design decision needed => Unreviewed


Comment:

 Dear "Django's lead developers":

 Being unable to perform variable lookups in the template is the bane of
 Django.
 Please be aware that after reviewing #12486, #1495, #959, and #577; I have
 determined that #3371 most appropriately addresses this source of Django's
 impotence. The individuals responsible for closing this ticket (@jacob,
 @ubernostrum) have provided nothing but non sequitur as motivation for its
 closing.  I find it necessary to reopen #3371, and I will continue to
 reopen it until Django is capable of performing variable lookups in the
 template, or until a SOUND reason is given for insisting that Django
 inflict such an undue handicap on perfectionists with deadlines.

 For the purpose of exemplifying the need for variable lookups in the
 template, consider a list of students ["Bob", ..., "Alice"] who enrol in
 courses ["Course1", ..., "CourseN"] and earn final marks of {"Bob" :
 {"Course1" : bobs_mark_for_course1, ..., "CourseN" :
 bobs_mark_for_courseN}, ..., "Alice" : {"Course1" :
 alices_mark_for_course1, ..., "CourseN" : alices_mark_for_courseN}}

 Displaying this table of information is a template level concern, and
 should be performed trivially as follows:

 Step 1 - In the views.py:
   c[!''students!''] = ["Bob", ..., "Alice"] # NOTE student names are
 unique in this example!
   c[!''courses!''] = ["Course1", ..., "CourseN"] # ditto the above comment
 for student names
   c[!''marks!''] = {"Bob" : {"Course1" : bobs_mark_for_course1, ...,
 "CourseN" : bobs_mark_for_courseN}, ..., "Alice" : {"Course1" :
 alices_mark_for_course1, ..., "CourseN" : alices_mark_for_courseN}}

   return render(request, c, "display.html")

 Step 2 - In the template display.html:
   
 
   Student Name
   {% for course in courses %}
 {{course}} Grade
   {% endfor %}
 

 {% for student in students %}
   
 {{student}}
 {% for course in courses %}
   {{marks.student.course}} {# ALERT Variable lookup! #}
 {% endfor %}
   
 {% endfor %}
   
 


 Sadly, it appears that this trivial exercise in templating is "out of
 scope" (@jacob) or even "impolite" (@ubernostrum). While not providing any
 alternatives to (or even any sound reasons for rejecting) @nullie's fix,
 one might speculate that the cited "Django's lead developers" would rather
 we perform such templating in the views.py:

 Step 1 - In the views.py:
 students = ["Bob", ..., "Alice"] # NOTE student names are unique in this
 example!
 courses = ["Course1", ..., "CourseN"] # ditto the above comment for
 student names
 marks = {"Bob" : {"Course1" : bobs_mark_for_course1, ..., "CourseN" :
 bobs_mark_for_courseN}, ..., "Alice" : {"Course1" :
 alices_mark_for_course1, ..., "CourseN" : alices_mark_for_courseN}}

 table_to_display = []
 html = table_to_display.append
 html("Student Name")
 for course in courses:
   html("")
   html(course)
   html(" Grade"
 html("")
 for student in students:
   html("")
   html(student)
   html("")
   for course in courses:
 html("")
 html(marks[student][course])
 html("")
   html("")
 html("")

 c[!''marks_table!''] = "".join(table_to_display)
 return render(request, c, "display.html")

 Step 2 - In the template display.html:
 {{marks_table|safe}}

 I'm sure that any person involved in a web-development project would agree
 that styling/upgrading/extending or otherwise maintaining under this
 paradigm is a doomed and futile effort.

 Using @nullie's fix, our task is accomplished with the following:
 Step 1 - In the views.py
   c[!''students!''] = ["Bob", ..., "Alice"] # NOTE student names are
 unique in this example!
   c[!''courses!''] = ["Course1", ..., "CourseN"] # ditto the above comment
 for student names
   c[!''mark

Re: [Django] #20392: Rearrange transactional behavior in django.test.TestCase: savepoints around tests

[Django]

#20392: Rearrange transactional behavior in django.test.TestCase: savepoints 
around
tests
-+-
 Reporter:  xelnor   |Owner:  smeatonj
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  test atomic  | Triage Stage:  Accepted
  savepoint  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by magopian):

 * cc: mathieu.agopian@… (added)


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

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

Re: [Django] #22577: The makemigrations management command has a problem with migrations dir

[Django]

#22577: The makemigrations management command has a problem with migrations dir
-+-
 Reporter:  japrogramer@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  makemigrations,  | Triage Stage:
  fail, init, file   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 I got this problem too. Could it because I'm on Python 3.

 Delete the migrations folder, solve the problem.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.a6874f715095b251b9290da49b3dd3a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22792: Check rule for list_display_links is incorrect

[Django]

#22792: Check rule for list_display_links is incorrect
---+
 Reporter:  bendavis78 |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.7-beta-2
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 This use case should be allowed according to the documentation:

 {{{
 #!python
 @admin.register(products.Product)
 class ModelAdmin(admin.ModelAdmin):
 list_display = ['brand', 'product', 'category']
 list_editable = list_display
 list_display_links = None
 }}}

 However, checks will fail saying:

 : (admin.E124) The value of
 'list_editable[0]' refers to the first field in 'list_display' ('brand'),
 which cannot be used unless 'list_display_links' is set.

 I think this check is a mistake. What it should be checking for is this:
 If the first values of `list_editable` and `list_display` are the same,
 list_display_links must be either set to None, or must be set to a field
 other than the first field in `list_display`.

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

Re: [Django] #13528: db_table truncation is applied based on the properties of the default database

[Django]

#13528: db_table truncation is applied based on the properties of the default
database
-+-
 Reporter:  russellm |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by loic84):

 * cc: loic84 (added)


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

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

Re: [Django] #20392: Rearrange transactional behavior in django.test.TestCase: savepoints around tests

[Django]

#20392: Rearrange transactional behavior in django.test.TestCase: savepoints 
around
tests
-+-
 Reporter:  xelnor   |Owner:  smeatonj
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  test atomic  | Triage Stage:  Accepted
  savepoint  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by smeatonj):

 xelnor, I'm looking into bringing this ticket up-to-date and testing the
 run time of the test suite with loaddata in the setUpClass. Is there any
 other information that you could offer up, or if you're already
 maintaining an up-to-date patch, providing the details of 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/064.049f6e3c00c915d36d2b5b2ed6be01f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #7837: Hierarchy in forms metaclasses can miss declarated fields in forms

[Django]

#7837: Hierarchy in forms metaclasses can miss declarated fields in forms
---+-
 Reporter:  msaelices  |Owner:  msaelices
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by loic84):

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


Comment:

 Fixed in #19617.

 Note that as documented the `ModelForm` subclass should appear first in
 the MRO:

 {{{
 class FooForm(forms.ModelForm, GenericForm):
pass
 }}}

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

[Django] #22791: makemigrations interactive questioner ignores app labels

[Django]

#22791: makemigrations interactive questioner ignores app labels
---+
 Reporter:  bendavis78 |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Migrations |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 When running `makemigrations `, the interactive questioner will
 still ask questions regarding apps you didn't pass to the command, even
 though the migrations aren't created for those apps.

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

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

Re: [Django] #27: Single form field for multiple database fields

[Django]

#27: Single form field for multiple database fields
-+-
 Reporter:  adrian   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by loic84):

 I think this can be trivially implemented with a custom field and with the
 current public APIs.

 Any objection to closing 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/064.102bf3878bb93a5c718c36e2be614772%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #3111: newforms: Add as_tr(), as_li() methods to BoundField

[Django]

#3111: newforms: Add as_tr(), as_li() methods to BoundField
-+-
 Reporter:  brantley |Owner:  aashu_dwivedi
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:
 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 loic84):

 I agree with @kmike, HTML in python is technical debt that we should fix,
 adding more `as_method()` feels counterproductive.

 This is an 8 years old ticket, I propose we close it, any objections?

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

Re: [Django] #22775: Management command sqlall should support unmanaged models

[Django]

#22775: Management command sqlall should support unmanaged models
-+-
 Reporter:  smeatonj |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  sqlall   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by loic84):

 * cc: timo (added)
 * status:  closed => new
 * resolution:  wontfix =>


Comment:

 @mardini, these commands going away doesn't change the fact that we don't
 have an answer to the problem of generating SQL for unmanaged models.

 I think the feature request still stands even if it'll have to go through
 a different path than `sqlall`.

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

[django/django] d8f6b5: Optimize is_protected_type slightly (used by force...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d8f6b55aa8f05a479eb0018b470932805f2c95d1
  
https://github.com/django/django/commit/d8f6b55aa8f05a479eb0018b470932805f2c95d1
  Author: Alex Gaynor 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/utils/encoding.py

  Log Message:
  ---
  Optimize is_protected_type slightly (used by force_text, which is used 
basically everywhere)


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

Re: [Django] #22777: Foreignkey does (sometimes) not get added to migration of M2M with a through model

[Django]

#22777: Foreignkey does (sometimes) not get added to migration of M2M with a
through model
-+
 Reporter:  valberg  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by andrewgodwin):

 Looks like there's not enough dependency stuff set in the autodetector to
 force the operation ordering. Hopefully an easy-ish fix.

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

Re: [Django] #22248: Model renaming doesn't work backwards

[Django]

#22248: Model renaming doesn't work backwards
--+
 Reporter:  andrewgodwin  |Owner:  andrewgodwin
 Type:  Bug   |   Status:  closed
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"4ce7a6bc84c68406e39f48550434faeef3277eba"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4ce7a6bc84c68406e39f48550434faeef3277eba"
 Fixed #22750, #22248: Model renaming now also alters field FKs
 }}}

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

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

Re: [Django] #22248: Model renaming doesn't work backwards

[Django]

#22248: Model renaming doesn't work backwards
--+
 Reporter:  andrewgodwin  |Owner:  andrewgodwin
 Type:  Bug   |   Status:  closed
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Andrew Godwin ):

 In [changeset:"b568bdf8da30fe5940a31add9f3a2b8029ecb04d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b568bdf8da30fe5940a31add9f3a2b8029ecb04d"
 [1.7.x] Fixed #22750, #22248: Model renaming now also alters field FKs
 }}}

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

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

Re: [Django] #22750: Renaming model fails

[Django]

#22750: Renaming model fails
-+
 Reporter:  valberg  |Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Andrew Godwin ):

 In [changeset:"b568bdf8da30fe5940a31add9f3a2b8029ecb04d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b568bdf8da30fe5940a31add9f3a2b8029ecb04d"
 [1.7.x] Fixed #22750, #22248: Model renaming now also alters field FKs
 }}}

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

Re: [Django] #22750: Renaming model fails

[Django]

#22750: Renaming model fails
-+
 Reporter:  valberg  |Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"4ce7a6bc84c68406e39f48550434faeef3277eba"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4ce7a6bc84c68406e39f48550434faeef3277eba"
 Fixed #22750, #22248: Model renaming now also alters field FKs
 }}}

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

[django/django] b568bd: [1.7.x] Fixed #22750, #22248: Model renaming now a...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: b568bdf8da30fe5940a31add9f3a2b8029ecb04d
  
https://github.com/django/django/commit/b568bdf8da30fe5940a31add9f3a2b8029ecb04d
  Author: Andrew Godwin 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M django/db/migrations/operations/models.py
M django/db/migrations/state.py
M tests/migrations/test_autodetector.py
M tests/migrations/test_base.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  [1.7.x] Fixed #22750, #22248: Model renaming now also alters field FKs


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

[django/django] 4ce7a6: Fixed #22750, #22248: Model renaming now also alte...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4ce7a6bc84c68406e39f48550434faeef3277eba
  
https://github.com/django/django/commit/4ce7a6bc84c68406e39f48550434faeef3277eba
  Author: Andrew Godwin 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M django/db/migrations/operations/models.py
M django/db/migrations/state.py
M tests/migrations/test_autodetector.py
M tests/migrations/test_base.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  Fixed #22750, #22248: Model renaming now also alters field FKs


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

Re: [Django] #22782: Add i18n to sitemap

[Django]

#22782: Add i18n to sitemap
--+
 Reporter:  luanpab   |Owner:  luanpab
 Type:  New feature   |   Status:  new
Component:  contrib.sitemaps  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  sitemap, i18n | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 I left comments for improvement on PR. Please uncheck "Patch needs
 improvement" when you update it, 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/065.a2991699b15ec1b75fce93603bf1f620%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 83fe38: [1.7.x] Removed usage of deprecated django.utils.i...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 83fe38ae30fe6053f378c4adfc4387f2e8bd030c
  
https://github.com/django/django/commit/83fe38ae30fe6053f378c4adfc4387f2e8bd030c
  Author: Tim Graham 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/db/migrations/writer.py

  Log Message:
  ---
  [1.7.x] Removed usage of deprecated django.utils.importlib.

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

[django/django] 1e84d2: Removed usage of deprecated django.utils.importlib...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1e84d261d618c11c939028ba37db09bae81b1eef
  
https://github.com/django/django/commit/1e84d261d618c11c939028ba37db09bae81b1eef
  Author: Tim Graham 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/db/migrations/writer.py

  Log Message:
  ---
  Removed usage of deprecated django.utils.importlib.


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

[django/django] 6c27ff: Fixed flake8 error.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6c27ff957a6162870b91138ccddda8530a0450b0
  
https://github.com/django/django/commit/6c27ff957a6162870b91138ccddda8530a0450b0
  Author: Tim Graham 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M tests/backends/tests.py

  Log Message:
  ---
  Fixed flake8 error.


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

Re: [Django] #22749: Making SQL management commands migration aware.

[Django]

#22749: Making SQL management commands migration aware.
-+-
 Reporter:  valberg  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:  fixed
  commands)  | Triage Stage:  Accepted
 Severity:  Release blocker  |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Andrew Godwin ):

 In [changeset:"3fc4f03895ae356a5861d0385de71e7a590811b6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3fc4f03895ae356a5861d0385de71e7a590811b6"
 [1.7.x] Fixed #22749: Making SQL management commands migration aware.
 }}}

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

Re: [Django] #22749: Making SQL management commands migration aware.

[Django]

#22749: Making SQL management commands migration aware.
-+-
 Reporter:  valberg  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:  fixed
  commands)  | Triage Stage:  Accepted
 Severity:  Release blocker  |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"f70f669941775ceef8433f4c66b189f82d53074f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f70f669941775ceef8433f4c66b189f82d53074f"
 Fixed #22749: Making SQL management commands migration aware.
 }}}

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

[django/django] 3fc4f0: [1.7.x] Fixed #22749: Making SQL management comman...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 3fc4f03895ae356a5861d0385de71e7a590811b6
  
https://github.com/django/django/commit/3fc4f03895ae356a5861d0385de71e7a590811b6
  Author: Víðir Valberg Guðmundsson 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/core/management/commands/sqlsequencereset.py
M django/core/management/sql.py
A tests/commands_sql_migrations/__init__.py
A tests/commands_sql_migrations/migrations/0001_initial.py
A tests/commands_sql_migrations/migrations/__init__.py
A tests/commands_sql_migrations/models.py
M tests/commands_sql_migrations/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22749: Making SQL management commands migration aware.


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

[django/django] f70f66: Fixed #22749: Making SQL management commands migra...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f70f669941775ceef8433f4c66b189f82d53074f
  
https://github.com/django/django/commit/f70f669941775ceef8433f4c66b189f82d53074f
  Author: Víðir Valberg Guðmundsson 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/core/management/commands/sqlsequencereset.py
M django/core/management/sql.py
A tests/commands_sql_migrations/__init__.py
A tests/commands_sql_migrations/migrations/0001_initial.py
A tests/commands_sql_migrations/migrations/__init__.py
A tests/commands_sql_migrations/models.py
M tests/commands_sql_migrations/tests.py

  Log Message:
  ---
  Fixed #22749: Making SQL management commands migration aware.


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

Re: [Django] #22436: migrations fail on custom upload_to on ImageField

[Django]

#22436: migrations fail on custom upload_to on ImageField
-+-
 Reporter:  David Binetti|Owner:
 |  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-2
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  1|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Andrew Godwin ):

 In [changeset:"98949e3b108100a40cb6ad59be78f33580439fef"]:
 {{{
 #!CommitTicketReference repository=""
 revision="98949e3b108100a40cb6ad59be78f33580439fef"
 [1.7.x] Fixed #22436: More careful checking on method ref'ce serialization
 }}}

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

[django/django] 98949e: [1.7.x] Fixed #22436: More careful checking on met...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 98949e3b108100a40cb6ad59be78f33580439fef
  
https://github.com/django/django/commit/98949e3b108100a40cb6ad59be78f33580439fef
  Author: Andrew Godwin 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/db/migrations/writer.py
M docs/topics/migrations.txt
M tests/migrations/test_writer.py

  Log Message:
  ---
  [1.7.x] Fixed #22436: More careful checking on method ref'ce serialization


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

Re: [Django] #22436: migrations fail on custom upload_to on ImageField

[Django]

#22436: migrations fail on custom upload_to on ImageField
-+-
 Reporter:  David Binetti|Owner:
 |  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-2
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  1|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"6fd455adfcc85f6bd390bce784a1b5dfe5d610ea"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6fd455adfcc85f6bd390bce784a1b5dfe5d610ea"
 Fixed #22436: More careful checking on method ref'ce serialization
 }}}

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

[django/django] 6fd455: Fixed #22436: More careful checking on method ref'...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6fd455adfcc85f6bd390bce784a1b5dfe5d610ea
  
https://github.com/django/django/commit/6fd455adfcc85f6bd390bce784a1b5dfe5d610ea
  Author: Andrew Godwin 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/db/migrations/writer.py
M docs/topics/migrations.txt
M tests/migrations/test_writer.py

  Log Message:
  ---
  Fixed #22436: More careful checking on method ref'ce serialization


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

Re: [Django] #22772: django.contrib.formtools test failures on Windows due to failure to delete file that is being used by another process

[Django]

#22772: django.contrib.formtools test failures on Windows due to failure to 
delete
file that is being used by another process
---+--
 Reporter:  manfre |Owner:  charettes
 Type:  Bug|   Status:  closed
Component:  contrib.formtools  |  Version:  1.7-beta-2
 Severity:  Release blocker|   Resolution:  fixed
 Keywords:  Windows| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by charettes):

 Backported to 1.7.x following
 
[https://github.com/django/django/commit/e2112edd9ac6a5f1877a62dd1c88d2d1726350de#commitcomment-6592575
 @timgraham's review].

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

[django/django] 2b1357: [1.7.x] Fixed #22772 -- Defer wizard temporary fil...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 2b13576c8f48bde808f58621ff26e5b1ab3ed4c1
  
https://github.com/django/django/commit/2b13576c8f48bde808f58621ff26e5b1ab3ed4c1
  Author: Simon Charette 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/contrib/formtools/tests/wizard/storage.py
M django/contrib/formtools/wizard/storage/base.py

  Log Message:
  ---
  [1.7.x] Fixed #22772 -- Defer wizard temporary files deletion.

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

Re: [Django] #22772: django.contrib.formtools test failures on Windows due to failure to delete file that is being used by another process

[Django]

#22772: django.contrib.formtools test failures on Windows due to failure to 
delete
file that is being used by another process
---+--
 Reporter:  manfre |Owner:  charettes
 Type:  Bug|   Status:  closed
Component:  contrib.formtools  |  Version:  1.7-beta-2
 Severity:  Release blocker|   Resolution:  fixed
 Keywords:  Windows| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Simon Charette ):

 In [changeset:"2b13576c8f48bde808f58621ff26e5b1ab3ed4c1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2b13576c8f48bde808f58621ff26e5b1ab3ed4c1"
 [1.7.x] Fixed #22772 -- Defer wizard temporary files deletion.

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

[django/django] 250e2b: Silenced some GIS deprecation warnings; refs #2238...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 250e2b422b4da93f38cd61319b9b3c9f422e6ede
  
https://github.com/django/django/commit/250e2b422b4da93f38cd61319b9b3c9f422e6ede
  Author: Tim Graham 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/contrib/gis/tests/geoapp/test_sitemaps.py
M django/contrib/gis/tests/geoapp/urls.py
M docs/releases/1.8.txt

  Log Message:
  ---
  Silenced some GIS deprecation warnings; refs #22384.


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

Re: [Django] #22384: Deprecate the ability to reverse by dotted path

[Django]

#22384: Deprecate the ability to reverse by dotted path
-+-
 Reporter:  timo |Owner:  timo
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (URLs)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"250e2b422b4da93f38cd61319b9b3c9f422e6ede"]:
 {{{
 #!CommitTicketReference repository=""
 revision="250e2b422b4da93f38cd61319b9b3c9f422e6ede"
 Silenced some GIS deprecation warnings; refs #22384.
 }}}

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

[Django] #22790: spatialite/Oracle GIS app_label deprecation warnings

[Django]

#22790: spatialite/Oracle GIS app_label deprecation warnings
+-
   Reporter:  timo  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  GIS   |Version:  1.7-beta-2
   Severity:  Normal|   Keywords:  app-loading
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+-
 {{{
 /home/tim/code/django/django/contrib/gis/db/backends/spatialite/models.py:10:
 RemovedInDjango19Warning: Model class
 django.contrib.gis.db.backends.spatialite.models.GeometryColumns
 doesn't declare an explicit app_label and either isn't in an application
 in INSTALLED_APPS or else was
 imported before its application was loaded. This will no longer be
 supported in Django 1.9.
   class GeometryColumns(models.Model):

 /home/tim/code/django/django/contrib/gis/db/backends/spatialite/models.py:47:
 RemovedInDjango19Warning: Model class
 django.contrib.gis.db.backends.spatialite.models.SpatialRefSys
 doesn't declare an explicit app_label and either isn't in an application
 in INSTALLED_APPS or else was
 imported before its application was loaded. This will no longer be
 supported in Django 1.9.
 }}}

 Tried adding `app_label = 'gis'` to the models, but ran into another
 problem:
 {{{
 ==
 ERROR: django.contrib.gis.tests.tests
 (unittest.loader.ModuleImportFailure)
 --
 ImportError: Failed to import test module: django.contrib.gis.tests.tests
 Traceback (most recent call last):
   File "/usr/lib/python2.7/unittest/loader.py", line 252, in _find_tests
 module = self._get_module_from_name(name)
   File "/usr/lib/python2.7/unittest/loader.py", line 230, in
 _get_module_from_name
 __import__(name)
   File "/home/tim/code/django/django/contrib/gis/tests/tests.py", line 9,
 in 
 from django.contrib.gis.db.backends.postgis.operations import
 PostGISOperations
   File
 "/home/tim/code/django/django/contrib/gis/db/backends/postgis/operations.py",
 line 16, in 
 from .models import GeometryColumns, SpatialRefSys
   File
 "/home/tim/code/django/django/contrib/gis/db/backends/postgis/models.py",
 line 10, in 
 class GeometryColumns(models.Model):
   File "/home/tim/code/django/django/db/models/base.py", line 287, in
 __new__
 new_class._meta.apps.register_model(new_class._meta.app_label,
 new_class)
   File "/home/tim/code/django/django/apps/registry.py", line 201, in
 register_model
 (model_name, app_label, app_models[model_name], model))
 RuntimeError: Conflicting 'geometrycolumns' models in application 'gis':
 
 and .
 }}}

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

Re: [Django] #13711: Very long field names on models cause problems

[Django]

#13711: Very long field names on models cause problems
-+-
 Reporter:  russellm |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 We are going to revisit this after working on #13528. I think we might be
 able to same a similar approach here.

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

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

Re: [Django] #19905: ResourceWarning in formtools tests

[Django]

#19905: ResourceWarning in formtools tests
---+
 Reporter:  apollo13   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.formtools  |  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):

 * has_patch:  1 => 0
 * severity:  Normal => Release blocker


Comment:

 Yes, CI does `git clean -fqdx` before each run.

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

Re: [Django] #22789: Consider deprecating contrib.webdesign

[Django]

#22789: Consider deprecating contrib.webdesign
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.webdesign |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timo):

 I've never used it myself.

 from [https://groups.google.com/d/topic/django-
 developers/P_WMxmOCJFY/discussion 2011 mailing list thread]:

 Carl: +1

 Paul M: +0 on webdesign, since it's functionality that's probably in
 transient use by the more invisible members of our community.

 Markus G: I'd miss it even though it's just a tiny piece of code and
 trivial, it's quite useful when you mock up a site and thus need some text
 to get a feeling for its layout when there's lots of text involved. I am
 sure, as you say, there are quite a few people out there who would miss it
 too.

 Gabriel: As for webdesign, why not roll the one piece in it (the
 marginally-useful lorem tag) into the main library and deprecate the hook
 in contrib?

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

Re: [Django] #22068: Trailing slash after some test suites leads to test failure

[Django]

#22068: Trailing slash after some test suites leads to test failure
-+-
 Reporter:  MattBlack|Owner:
 Type:  Bug  |  akshay1994.leo
Component:  Testing framework|   Status:  new
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by timo):

 I don't know if `runtests.py` should have the same behavior. For example,
 `./runtests.py ../django/contrib/admin/` doesn't discover any tests.  The
 slash method isn't documented in
 [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /unit-tests/#running-only-some-of-the-tests running some of Django's
 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/067.173f83d3858c1e97bcae3ba03c94a7fa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 1a01e2: Tested pluralization of decimals.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1a01e24331194a8580d9f16b02e02f8403680942
  
https://github.com/django/django/commit/1a01e24331194a8580d9f16b02e02f8403680942
  Author: Aymeric Augustin 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M tests/defaultfilters/tests.py

  Log Message:
  ---
  Tested pluralization of decimals.

Refs #16723.


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

Re: [Django] #16723: Pluralize filter shouldn't pluralize decimal/float values between 1 and 2

[Django]

#16723: Pluralize filter shouldn't pluralize decimal/float values between 1 and 
2
-+
 Reporter:  rfugger  |Owner:
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  invalid
 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 Aymeric Augustin ):

 In [changeset:"1a01e24331194a8580d9f16b02e02f8403680942"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1a01e24331194a8580d9f16b02e02f8403680942"
 Tested pluralization of decimals.

 Refs #16723.
 }}}

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

Re: [Django] #16723: Pluralize filter shouldn't pluralize decimal/float values between 1 and 2

[Django]

#16723: Pluralize filter shouldn't pluralize decimal/float values between 1 and 
2
-+
 Reporter:  rfugger  |Owner:
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  invalid
 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 aaugustin):

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


Comment:

 I don't understand the last comment, `Decimal('1.0')` is handled by the
 `|pluralize` filter as a singular value and is displayed as `1` in the
 template. So everything is correct. I'm going to add a test.

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

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

Re: [Django] #9974: Add a template filter similar to pluralize but i18n-aware regarding plural form rules

[Django]

#9974: Add a template filter similar to pluralize but i18n-aware regarding 
plural
form rules
-+
 Reporter:  david|Owner:  david
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  1.0
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by aaugustin):

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


Comment:

 This is very difficult to get right in English -- as the Rails people
 learnt the hard way -- and I cannot imagine maintaining this for French.

 There's no fundamental reason for such a template tag to live in Django.
 It's better to leave this feature to a third-party library.

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

Re: [Django] #21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout passed

[Django]

#21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout 
passed
-+-
 Reporter:  ekeydar@…|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  mysql|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Description changed by aaugustin:

Old description:

> '''EDIT -- THE SOLUTION TO THIS PROBLEM IS EXPLAINED IN
> [https://code.djangoproject.com/ticket/21597#comment:29 COMMENT 29]. JUST
> DO WHAT IT SAYS. THANK YOU!'''
>
> 
>
> In django 1.6, when the wait_timeout passed (of mysql), then DB access
> cause the (2006, 'MySQL server has gone away') error.
> This was not the case in django 1.5.1
>
> I've noticed this error when using workers that run the django code
> (using gearman).
>
> To reproduce:
>
> Set the timeout to low value by editing /etc/mysql/my.cnf
> add the following under [mysqld]
>
> wait_timeout= 10
> interactive_timeout = 10
>
> Then
>
> {{{
> % python manage.py shell
>
> >>> # access DB
> >>> import django.contrib.auth.models
> >>> print list(django.contrib.auth.models.User.objects.all())
> >>> import time
> >>> time.sleep(15)
> >>> print list(django.contrib.auth.models.User.objects.all())
> }}}
>
> Now you get the error.
>
> Simple solution I found on the web is to call
> django.db.close_connection() before the access
>
> {{{
> >>> import django.db
> >>> django.db.close_connection()
> >>> print list(django.contrib.auth.models.User.objects.all())
> }}}
> works ok.

New description:

 '''EDIT -- THE SOLUTION TO THIS PROBLEM IS EXPLAINED IN
 [https://code.djangoproject.com/ticket/21597#comment:29 COMMENT 29]. JUST
 DO WHAT IT SAYS. THANK YOU! '''

 

 In django 1.6, when the wait_timeout passed (of mysql), then DB access
 cause the (2006, 'MySQL server has gone away') error.
 This was not the case in django 1.5.1

 I've noticed this error when using workers that run the django code (using
 gearman).

 To reproduce:

 Set the timeout to low value by editing /etc/mysql/my.cnf
 add the following under [mysqld]

 wait_timeout= 10
 interactive_timeout = 10

 Then

 {{{
 % python manage.py shell

 >>> # access DB
 >>> import django.contrib.auth.models
 >>> print list(django.contrib.auth.models.User.objects.all())
 >>> import time
 >>> time.sleep(15)
 >>> print list(django.contrib.auth.models.User.objects.all())
 }}}

 Now you get the error.

 Simple solution I found on the web is to call django.db.close_connection()
 before the access

 {{{
 >>> import django.db
 >>> django.db.close_connection()
 >>> print list(django.contrib.auth.models.User.objects.all())
 }}}
 works ok.

--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.44281cefcc243a45709dfe728bb29669%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout passed

[Django]

#21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout 
passed
-+-
 Reporter:  ekeydar@…|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  mysql|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Description changed by aaugustin:

Old description:

> In django 1.6, when the wait_timeout passed (of mysql), then DB access
> cause the (2006, 'MySQL server has gone away') error.
> This was not the case in django 1.5.1
>
> I've noticed this error when using workers that run the django code
> (using gearman).
>
> To reproduce:
>
> Set the timeout to low value by editing /etc/mysql/my.cnf
> add the following under [mysqld]
>
> wait_timeout= 10
> interactive_timeout = 10
>
> Then
>
> {{{
> % python manage.py shell
>
> >>> # access DB
> >>> import django.contrib.auth.models
> >>> print list(django.contrib.auth.models.User.objects.all())
> >>> import time
> >>> time.sleep(15)
> >>> print list(django.contrib.auth.models.User.objects.all())
> }}}
>
> Now you get the error.
>
> Simple solution I found on the web is to call
> django.db.close_connection() before the access
>
> {{{
> >>> import django.db
> >>> django.db.close_connection()
> >>> print list(django.contrib.auth.models.User.objects.all())
> }}}
> works ok.

New description:

 '''EDIT -- THE SOLUTION TO THIS PROBLEM IS EXPLAINED IN
 [https://code.djangoproject.com/ticket/21597#comment:29 COMMENT 29]. JUST
 DO WHAT IT SAYS. THANK YOU!'''

 

 In django 1.6, when the wait_timeout passed (of mysql), then DB access
 cause the (2006, 'MySQL server has gone away') error.
 This was not the case in django 1.5.1

 I've noticed this error when using workers that run the django code (using
 gearman).

 To reproduce:

 Set the timeout to low value by editing /etc/mysql/my.cnf
 add the following under [mysqld]

 wait_timeout= 10
 interactive_timeout = 10

 Then

 {{{
 % python manage.py shell

 >>> # access DB
 >>> import django.contrib.auth.models
 >>> print list(django.contrib.auth.models.User.objects.all())
 >>> import time
 >>> time.sleep(15)
 >>> print list(django.contrib.auth.models.User.objects.all())
 }}}

 Now you get the error.

 Simple solution I found on the web is to call django.db.close_connection()
 before the access

 {{{
 >>> import django.db
 >>> django.db.close_connection()
 >>> print list(django.contrib.auth.models.User.objects.all())
 }}}
 works ok.

--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.36712e9903bf59563c604dfe621bf281%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout passed

[Django]

#21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout 
passed
-+-
 Reporter:  ekeydar@…|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  mysql|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 I already answered in comment 29.

 If people read answers instead of asking the same question again and
 again, it would remain more visible.

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

Re: [Django] #21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout passed

[Django]

#21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout 
passed
-+-
 Reporter:  ekeydar@…|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  mysql|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by pembo13):

 What is the correct solution for management commands that may take longer
 than the regular web queries? This issue was closed with more questions
 than answers.

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

Re: [Django] #20752: Error signals are not reliable, especially when dealing with database errors

[Django]

#20752: Error signals are not reliable, especially when dealing with database
errors
-+-
 Reporter:  tal@…|Owner:  schacki
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  signals errors   | Triage Stage:  Accepted
  databaseError  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 The PR doesn't apply any more.

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

Re: [Django] #17552: The GZip Middleware's browser checking is too broad and misses versions of Netscape which have similar bugs

[Django]

#17552: The GZip Middleware's browser checking is too broad and misses versions 
of
Netscape which have similar bugs
-+
 Reporter:  cannona  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  gzip middleware  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by aaugustin):

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


Comment:

 I think usage of IE 6 and Netscape 4 has fallen sufficiently to make this
 unnecessary. Sorry.

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

Re: [Django] #22111: Signal can throw ValueError in debug mode

[Django]

#22111: Signal can throw ValueError in debug mode
--+
 Reporter:  ilya_pirogov  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Python 3  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 Yes, we avoid maintaining patched versions of stdlib features at all
 costs.

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

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

Re: [Django] #20815: daemonize.py: unbuffered text IO error (python3)

[Django]

#20815: daemonize.py: unbuffered text IO error (python3)
--+
 Reporter:  alex01@…  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  python3 runfcgi open  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Aymeric Augustin ):

 In [changeset:"211ff288a03ba4623399e222d15a33075e958f0a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="211ff288a03ba4623399e222d15a33075e958f0a"
 [1.7.x] Fixed #20815 -- Don't enforce unbuffered I/O on Python 3.

 No test because this code is already deprecated (part of FastCGI support).

 Backport of 5836a577 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/074.47554da29e01ec84e5eb301478680ff7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 211ff2: [1.7.x] Fixed #20815 -- Don't enforce unbuffered I...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 211ff288a03ba4623399e222d15a33075e958f0a
  
https://github.com/django/django/commit/211ff288a03ba4623399e222d15a33075e958f0a
  Author: Aymeric Augustin 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/utils/daemonize.py

  Log Message:
  ---
  [1.7.x] Fixed #20815 -- Don't enforce unbuffered I/O on Python 3.

No test because this code is already deprecated (part of FastCGI support).

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

[django/django] 5836a5: Fixed #20815 -- Don't enforce unbuffered I/O on Py...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5836a5771f2aefca83349b111f4191d6485af1d5
  
https://github.com/django/django/commit/5836a5771f2aefca83349b111f4191d6485af1d5
  Author: Aymeric Augustin 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/utils/daemonize.py

  Log Message:
  ---
  Fixed #20815 -- Don't enforce unbuffered I/O on Python 3.

No test because this code is already deprecated (part of FastCGI support).


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

Re: [Django] #22563: Migration of admin.LogEntry.user fails.

[Django]

#22563: Migration of admin.LogEntry.user fails.
-+
 Reporter:  efrinut@…|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 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 bendavis78):

 I'm also still seeing the issue on 1.7.x. I have to switch to 1.7.b2 to do
 migrations.

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

Re: [Django] #20815: daemonize.py: unbuffered text IO error (python3)

[Django]

#20815: daemonize.py: unbuffered text IO error (python3)
--+
 Reporter:  alex01@…  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  python3 runfcgi open  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"5836a5771f2aefca83349b111f4191d6485af1d5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5836a5771f2aefca83349b111f4191d6485af1d5"
 Fixed #20815 -- Don't enforce unbuffered I/O on Python 3.

 No test because this code is already deprecated (part of FastCGI support).
 }}}

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

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

Re: [Django] #21628: Stop using the `imp` module

[Django]

#21628: Stop using the `imp` module
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 Removing usage in the tests is quite difficult. I tried to use the
 replacements from importlib but I keep hitting infinite recursions.

 In fact it's a bit difficult to figure out what matters in the test. They
 were introduced in #13464 but that ticket is short on details.

 If I understand Python's deprecation policy correctly, the `imp` module
 won't be removed before Python 4. We could simply silence the deprecation
 warning.

 The alternative would be to run these tests only under Python < 3.3. The
 implementation on Python >= 3.3 is drastically simpler and may not require
 as many 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/067.2001d6c4dbb08599c6335516ca45a005%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22462: Loading issue of models declared in tests.py due to a combination of AdminConfig, System checks, and Model._meta caching.

[Django]

#22462: Loading issue of models declared in tests.py due to a combination of
AdminConfig, System checks, and Model._meta caching.
--+-
 Reporter:  loic84|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  duplicate
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by aaugustin):

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


Comment:

 Closing as a duplicate of #7835.

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

Re: [Django] #21628: Stop using the `imp` module

[Django]

#21628: Stop using the `imp` module
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Aymeric Augustin ):

 In [changeset:"d7f1f316bcb21853597515a25e6e43639b9ed021"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d7f1f316bcb21853597515a25e6e43639b9ed021"
 Simplified module_has_submodule on Python >= 3.3.

 Stopped using the imp module on Python >= 3.3. Refs #21628.
 }}}

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

[django/django] d7f1f3: Simplified module_has_submodule on Python >= 3.3.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d7f1f316bcb21853597515a25e6e43639b9ed021
  
https://github.com/django/django/commit/d7f1f316bcb21853597515a25e6e43639b9ed021
  Author: Aymeric Augustin 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/utils/module_loading.py

  Log Message:
  ---
  Simplified module_has_submodule on Python >= 3.3.

Stopped using the imp module on Python >= 3.3. Refs #21628.


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

Re: [Django] #6992: Better error message if Middleware.process_response returns None

[Django]

#6992: Better error message if Middleware.process_response returns None
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"47a9347b9828ed0186d676ee0c5cadd9e6a93edb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="47a9347b9828ed0186d676ee0c5cadd9e6a93edb"
 Fixed #6992 -- Improved error when middleware omits HttpResponse.

 Thanks guettli for the report.
 }}}

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

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

[django/django] 47a934: Fixed #6992 -- Improved error when middleware omit...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 47a9347b9828ed0186d676ee0c5cadd9e6a93edb
  
https://github.com/django/django/commit/47a9347b9828ed0186d676ee0c5cadd9e6a93edb
  Author: Aymeric Augustin 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

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

  Log Message:
  ---
  Fixed #6992 -- Improved error when middleware omits HttpResponse.

Thanks guettli for the report.


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

Re: [Django] #22788: Custom migration operations are rewritten incorrectly

[Django]

#22788: Custom migration operations are rewritten incorrectly
+--
 Reporter:  schinckel   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by mardini):

 * has_patch:  0 => 1


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

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

Re: [Django] #16665: Make sql clui commands consistent with dumpdata by allowing manage.py sql appname.Model

[Django]

#16665: Make sql clui commands consistent with dumpdata by allowing manage.py 
sql
appname.Model
-+-
 Reporter:  wim@…|Owner:  marclurr
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:  wontfix
 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 mardini):

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


Comment:

 I'm closing this since sql commands will be deprecated according to
 Andrew, so working on new features won't be useful:
 https://code.djangoproject.com/ticket/22611#comment:6

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

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

Re: [Django] #22776: Management command sqlall should support applabel.model syntax

[Django]

#22776: Management command sqlall should support applabel.model syntax
-+-
 Reporter:  smeatonj |Owner:  mardini
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  sqlall   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mardini):

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


Comment:

 After a discussion on IRC, Tim suggested closing this ticket and not doing
 any new work on sql commands, since they will be deprecated according to
 Andrew: https://code.djangoproject.com/ticket/22611#comment:6

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

Re: [Django] #22775: Management command sqlall should support unmanaged models

[Django]

#22775: Management command sqlall should support unmanaged models
-+-
 Reporter:  smeatonj |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  sqlall   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mardini):

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


Comment:

 After a discussion on IRC, Tim suggested closing this ticket and not doing
 any new work on sql commands, since they will be deprecate according to
 Andrew: https://code.djangoproject.com/ticket/22611#comment:6

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

Re: [Django] #13528: db_table truncation is applied based on the properties of the default database

[Django]

#13528: db_table truncation is applied based on the properties of the default
database
-+-
 Reporter:  russellm |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 I don't think the approach of the latest PR is good. Let's try
 implementing what Andrew suggested in comment 5 of 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.ad8c06112982dbdc24504542550def9d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22776: Management command sqlall should support applabel.model syntax

[Django]

#22776: Management command sqlall should support applabel.model syntax
-+-
 Reporter:  smeatonj |Owner:  mardini
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  sqlall   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mardini):

 * component:  Database layer (models, ORM) => Core (Management commands)


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

Re: [Django] #21451: LiveServerTestCase returns a 404 on all URLs when MEDIA_URL = '' and DEBUG = True

[Django]

#21451: LiveServerTestCase returns a 404 on all URLs when MEDIA_URL = '' and 
DEBUG
= True
---+
 Reporter:  aaugustin  |Owner:  gchp
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  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:  0  |UI/UX:  0
---+
Changes (by timo):

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


Comment:

 On the PR, Greg noted that this was fixed in 1.7 as part of the removal
 the static files dependencies in `LiveServerTestCase` [e909ceae].

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

Re: [Django] #6992: Better error message if Middleware.process_response returns None

[Django]

#6992: Better error message if Middleware.process_response returns None
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

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

 It's quite simple but I'll wait for the CI to run the test suite.

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

Re: [Django] #22789: Consider deprecating contrib.webdesign

[Django]

#22789: Consider deprecating contrib.webdesign
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.webdesign |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by loic84):

 * stage:  Unreviewed => Accepted


Comment:

 Couldn't agree more, especially since it's trivial to vendor it for
 whomever needs 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/067.0d71e84feb6098a83f9c0a0d3ed4eae2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #8713: Django core depends on django.contrib

[Django]

#8713: Django core depends on django.contrib
-+-
 Reporter:  Piotr Lewandowski|Owner:  nobody
   |   Status:  closed
 Type:  New feature  |  Version:  master
Component:  Core (Other) |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 Since all changes identified in comment 13 have been done, except the one
 that's still tracked in #20915, I believe we can close 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/098.d70b0ea3b2ae275290e48193ceeb34d7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5685: [patch] Add ability to perform pre-runtime setup before executing code

[Django]

#5685: [patch] Add ability to perform pre-runtime setup before executing code
--+
 Reporter:  __hawkeye__   |Owner:
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

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


Comment:

 The app-loading refactor clarified Django's start-up sequence and a
 solution for [https://docs.djangoproject.com/en/dev/ref/signals/#class-
 prepared registering class_prepared receivers] was documented.

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

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

Re: [Django] #14094: Cannot define CharField with unlimited length

[Django]

#14094: Cannot define CharField with unlimited length
-+-
 Reporter:  millerdev|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.2
  (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 aaugustin):

 * component:  Core (Other) => Database layer (models, ORM)


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

Re: [Django] #17916: humanize naturaltime for large delta

[Django]

#17916: humanize naturaltime for large delta
---+
 Reporter:  anonymous  |Owner:
 Type:  New feature|   Status:  closed
Component:  contrib.humanize   |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  sprints-django-ar  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by aaugustin):

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


Comment:

 I don't think we want to change the behavior, because it isn't obviously
 wrong and we don't have sufficient reasons to introduce a backwards
 incompatibility. Indeed, you should implement a custom tag if you have
 specific requirements not met by Django's native tags.

 The documentation issue was previously reported in #16941 and fixed in
 [07e10fbe9f].

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

Re: [Django] #19447: Intword and intabr expansion and intword_internal api exposure

[Django]

#19447: Intword and intabr expansion and intword_internal api exposure
--+
 Reporter:  eire1130  |Owner:  eire1130
 Type:  New feature   |   Status:  closed
Component:  contrib.humanize  |  Version:  master
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

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


Comment:

 I agree with Luke, we already have many built-in filters and we're not
 particularly looking at adding more.

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

Re: [Django] #16507: Tests that alter ROOT_URLCONF should set DEBUG_PROPAGATE_EXCEPTION

[Django]

#16507: Tests that alter ROOT_URLCONF should set DEBUG_PROPAGATE_EXCEPTION
--+
 Reporter:  andymckay |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.messages  |  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 aaugustin):

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


Comment:

 With the new test runner introduced in Django 1.6, tests of contrib apps
 aren't run anymore when you run your projects' tests.

 So this issue shouldn't manifest itself anymore. It was just a
 particularly insidious example of the lack of isolation of contrib apps
 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/067.ba538113bde824b9bb676468eeaecee1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19323: Add django.contrib.redirects setting for turning redirect on/off.

[Django]

#19323: Add django.contrib.redirects setting for turning redirect on/off.
-+-
 Reporter:  Melevir  |Owner:  Melevir
 Type:  New feature  |   Status:  new
Component:  contrib.redirects|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  schemamigration, | Triage Stage:
  redirects, is_active   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 The current plan is to make changes to models in contrib apps in Django
 1.8.

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

Re: [Django] #22782: Add i18n to sitemap

[Django]

#22782: Add i18n to sitemap
--+--
 Reporter:  luanpab   |Owner:  luanpab
 Type:  New feature   |   Status:  new
Component:  contrib.sitemaps  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  sitemap, i18n | Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by aaugustin):

 I agree with the API proposed in the pull request. It just needs some
 polish.

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

Re: [Django] #11572: Very high memory usage by big sitemaps

[Django]

#11572: Very high memory usage by big sitemaps
-+-
 Reporter:  riklaunim|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.sitemaps |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Reading this ticket again, there's just some handwaving about magical
 "streaming" that's going to fix everything, but it isn't clear whether
 that's HTTP streaming or server-side database cursors...

 In the absence of a concrete proposal, I'm going to close this ticket as
 "needsinfo". Please reopen if you can suggest implementation changes or
 documentatation changes.

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

[Django] #22789: Consider deprecating contrib.webdesign

[Django]

#22789: Consider deprecating contrib.webdesign
+
   Reporter:  aaugustin |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.webdesign |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 This app looks like a joke in 2014.

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

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

Re: [Django] #10743: Support lookup separators in ModelAdmin.list_display

[Django]

#10743: Support lookup separators in ModelAdmin.list_display
-+-
 Reporter:  mrts |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  efficient-admin, | Triage Stage:  Accepted
  list_display   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 If I understand correctly, the goal of this ticket is to enable Django to
 automatically optimize the queryset for building the admin changelist by
 adding appropriate fields to select_related() and only().

 But that can't be done automatically as soon as someone puts a callable in
 `display_list`. So we're back to square 1, except Django pretended that it
 could handle the optimization automatically, and failed at that.

 In my opinion that would be worse that just telling the user to write an
 appropriate get_queryset. For this reason (and also considering limited
 demand for this feature over the last five years) I'm going to reject 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/062.ad54b1c2c951ef027819bc080a90024c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #10911: Date comparison lookup operators

[Django]

#10911: Date comparison lookup operators
-+-
 Reporter:  vbmendes |Owner:  clement
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.0
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  lookup, orm, date|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 I don't think we want to provide lookups for all the permutations of
 (DateField, DateTimeField, TimeField) x (year, month, day, dow, doy, hour,
 minute, second, microsecond) x (eq, ne, gt, lt, gte, lte). So the solution
 given by Anssi is the way to go.

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

Re: [Django] #9596: Comparing a DateTimeField to a date is too hard

[Django]

#9596: Comparing a DateTimeField to a date is too hard
-+-
 Reporter:  django@… |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  lookup_type date |  Needs documentation:  0
  datetimefield compare comparison   |  Patch needs improvement:  1
  query_term field lookup|UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Still, I would support adding proper support for this feature in Django,
 if only to make sure time zones are handled correctly when USE_TZ is True.
 It's very easy to mess them up!

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

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

Re: [Django] #12489: Need a Field Lookup for day of year: __dayofyear

[Django]

#12489: Need a Field Lookup for day of year: __dayofyear
-+-
 Reporter:  deanq|Owner:  v1v3kn
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  field lookup |  Needs documentation:  1
  datetime filter|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 The custom lookups introduced in Django 1.7 can be used to implement this
 feature.

 See https://docs.djangoproject.com/en/1.7/ref/models/custom-lookups/

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

Re: [Django] #12529: manage.py syncdb doesn't check tables by using mangled names with Oracle backend

[Django]

#12529: manage.py syncdb doesn't check tables by using mangled names with Oracle
backend
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  syncdb oracle|  Needs documentation:  0
  inspectdb  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 With the introduction of the new migrations framework in Django 1.7, this
 issue doesn't exist anymore.

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

Re: [Django] #12581: connection.queries should use a ring buffer to avoid large memory consumption under runserver

[Django]

#12581: connection.queries should use a ring buffer to avoid large memory
consumption under runserver
-+-
 Reporter:  robhudson|Owner:  nobody
 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:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"fc31319752945d4d39f70c8278ecd42af240bc64"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc31319752945d4d39f70c8278ecd42af240bc64"
 Fixed test again. Refs #12581.
 }}}

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

[django/django] fc3131: Fixed test again. Refs #12581.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fc31319752945d4d39f70c8278ecd42af240bc64
  
https://github.com/django/django/commit/fc31319752945d4d39f70c8278ecd42af240bc64
  Author: Aymeric Augustin 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M tests/backends/tests.py

  Log Message:
  ---
  Fixed test again. Refs #12581.


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

[django/django] 58de49: Fixed #17427 -- Removed dubious definition of conn...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 58de495c54c203dfa838538fb6ca46187120f4e6
  
https://github.com/django/django/commit/58de495c54c203dfa838538fb6ca46187120f4e6
  Author: Aymeric Augustin 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/db/backends/__init__.py
M docs/releases/1.8.txt
R tests/db_backends/__init__.py
R tests/db_backends/tests.py

  Log Message:
  ---
  Fixed #17427 -- Removed dubious definition of connections equality.


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

Re: [Django] #17427: DatabaseWrapper no longer hashable-> failure in test_connections_thread_local

[Django]

#17427: DatabaseWrapper no longer hashable-> failure in
test_connections_thread_local
-+-
 Reporter:  vsajip   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"58de495c54c203dfa838538fb6ca46187120f4e6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="58de495c54c203dfa838538fb6ca46187120f4e6"
 Fixed #17427 -- Removed dubious definition of connections equality.
 }}}

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

Re: [Django] #20392: Rearrange transactional behavior in django.test.TestCase: savepoints around tests

[Django]

#20392: Rearrange transactional behavior in django.test.TestCase: savepoints 
around
tests
-+-
 Reporter:  xelnor   |Owner:  smeatonj
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  test atomic  | Triage Stage:  Accepted
  savepoint  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by xelnor):

 Replying to [comment:7 aaugustin]:
 > Xelnor, when you say "create the database", you mean "create the
 database connection", don't you?

 Hmm, yes, I think that's what I thought. Anyway, that's what the patch
 does ;)

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

Re: [Django] #20392: Rearrange transactional behavior in django.test.TestCase: savepoints around tests

[Django]

#20392: Rearrange transactional behavior in django.test.TestCase: savepoints 
around
tests
-+-
 Reporter:  xelnor   |Owner:  smeatonj
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  test atomic  | Triage Stage:  Accepted
  savepoint  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by smeatonj):

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


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

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

Re: [Django] #12857: Doc: Media class usage

[Django]

#12857: Doc: Media class usage
---+
 Reporter:  Ciantic|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 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):

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


Comment:

 `Media` class is likely to be deprecated, or at least renamed (#22298).

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

Re: [Django] #21687: Document the abstract models testing

[Django]

#21687: Document the abstract models testing
-+-
 Reporter:  jocelyn@…|Owner:  JocelynD
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  documentation,   |  Needs documentation:  0
  testing|  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 Closing per Marc's concerns.

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

[django/django] d98cc4: Made a test compatible with Python 2 and 3.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d98cc41a845237edd62013e3156a0991dfb3d93e
  
https://github.com/django/django/commit/d98cc41a845237edd62013e3156a0991dfb3d93e
  Author: Aymeric Augustin 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/utils/six.py
M tests/backends/tests.py

  Log Message:
  ---
  Made a test compatible with Python 2 and 3.


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

Re: [Django] #18314: request.build_absolute_uri() functions incorrectly when the path starts with //

[Django]

#18314: request.build_absolute_uri() functions incorrectly when the path starts
with //
---+
 Reporter:  anonymous  |Owner:  unaizalakain
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"11284a63d48c84f1d60b5686d55cf8a9f8d64422"]:
 {{{
 #!CommitTicketReference repository=""
 revision="11284a63d48c84f1d60b5686d55cf8a9f8d64422"
 Fixed #18314 -- Corrected request.build_absolute_uri() handling of paths
 starting with //

 ``HttpRequest.build_absolute_uri()`` now correctly handles paths starting
 with ``//``.
 ``WSGIRequest`` now doesn't remove all the leading slashes either,
 because ``http://test/server`` and http://test//server`` aren't the same
 thing
 (RFC2396).

 Thanks to SmileyChris for the 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/067.b6c0baff20f61a9dc8f791076e3c5f74%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 11284a: Fixed #18314 -- Corrected request.build_absolute_u...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 11284a63d48c84f1d60b5686d55cf8a9f8d64422
  
https://github.com/django/django/commit/11284a63d48c84f1d60b5686d55cf8a9f8d64422
  Author: Unai Zalakain 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M django/core/handlers/wsgi.py
M django/http/request.py
M docs/releases/1.8.txt
M tests/requests/tests.py

  Log Message:
  ---
  Fixed #18314 -- Corrected request.build_absolute_uri() handling of paths 
starting with //

``HttpRequest.build_absolute_uri()`` now correctly handles paths starting with 
``//``.
``WSGIRequest`` now doesn't remove all the leading slashes either,
because ``http://test/server`` and http://test//server`` aren't the same thing
(RFC2396).

Thanks to SmileyChris for the 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/53930d6a52124_1aa46abd3c33ef%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17238: Link to source code in docs

[Django]

#17238: Link to source code in docs
-+
 Reporter:  santiagobasulto  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"9ed4a8c6b1a552a03fd27b77f1b742e3f9c66bde"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9ed4a8c6b1a552a03fd27b77f1b742e3f9c66bde"
 Fixed #17238 -- Added source code links to docs using sphinx.ext.viewcode.

 Thanks santiagobasulto for the suggestion.
 }}}

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

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

[django/django] 9ed4a8: Fixed #17238 -- Added source code links to docs us...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9ed4a8c6b1a552a03fd27b77f1b742e3f9c66bde
  
https://github.com/django/django/commit/9ed4a8c6b1a552a03fd27b77f1b742e3f9c66bde
  Author: Tim Graham 
  Date:   2014-06-07 (Sat, 07 Jun 2014)

  Changed paths:
M docs/conf.py

  Log Message:
  ---
  Fixed #17238 -- Added source code links to docs using sphinx.ext.viewcode.

Thanks santiagobasulto for the suggestion.


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