Re: [Django] #21454: Ignoring certain fields on INSERT and UPDATE queries

2013-12-27 Thread Django 
#21454: Ignoring certain fields on INSERT and UPDATE queries
-+-
 Reporter:  mpessas  |Owner:  mpessas
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mpessas):

 Replying to [comment:8 shai]:
 > @mpessas: With all things Oracle, you can always bug me. I only had time
 to glimpse at your patch now, but I will happily work with you to make
 sure that, by the time it is committed, Oracle is not broken.

 Great, thanks! Right now the Oracle backend uses a second query to read
 any updated values, even though it supports the `RETURNING INTO` clause.
 However, I am not that familiar with Oracle to be sure how to make this
 work (or test anything).

 As far as I can tell, Oracle needs to create "bind" variables with a given
 type. Would it work, if I used a list of `Field`s instead of names (right
 now the list of returning values is a list of field ''names'')? That way,
 I guess I should be (somehow, maybe via the `db_type` property) able to
 figure out the type of each field in the returning values list. How does
 this sound? I could work on this, but like I said I have no way to
 actually test any changes.

 By the way, you can email me directly, if we need to coordinate this; it
 is a gmail account with this username.

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

Re: [Django] #21454: Ignoring certain fields on INSERT and UPDATE queries

2013-12-27 Thread Django 
#21454: Ignoring certain fields on INSERT and UPDATE queries
-+-
 Reporter:  mpessas  |Owner:  mpessas
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mpessas):

 Replying to [comment:5 manfre]:
 > It's possible that a database backend is capable of returning the IDs
 from an insert without supporting the {{{RETURNING}}} clause. Those should
 be separate features. I previously injected a select statement to return
 the inserted ID without needing a second round trip to the MSSQL server.
 It's also possible that certain database drivers may return newly inserted
 IDs without SQL.
 >

 True, this has been implemented at
 
https://github.com/mpessas/django/commit/c7ca041347b9c8b24285cb0c94ba3eefeded707e.

 Replying to [comment:6 manfre]:
 >The use_on_insert and use_on_update arguments could get merged in to an
 edit_behavior argument (probably needs a better name) that expects one of
 the following constant values:
 >
 >DEFAULT - use_on_insert == True and use_on_update == True
 >CREATE_ONLY - use_on_insert == True and use_on_update == False
 >UPDATE_ONLY - use_on_insert == False and use_on_update == True
 >READ_ONLY - use_on_insert == False and use_on_update == False

 That is a good idea, see commit
 
https://github.com/mpessas/django/commit/a8a19b65774383bc47d3fb04ca6966ba4a4cba94
 (a better name is welcome).

 The `always_refresh` feature sounds interesting and I will take a look; it
 should not be that hard.

 Keep in mind, by the way, that as far as I can tell and at least in
 PostgreSQL the `RETURNING` clause does not "work" with an ''after''
 trigger; that is, if a field is changed by an `AFTER INSERT` or `AFTER
 UPDATE` trigger will not be returned with a `RETURNING` clause.

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

Re: [Django] #21693: detaultfilter wordcap converts a string into titlecase but respect the actual uppercase

2013-12-27 Thread Django 
#21693: detaultfilter wordcap converts a string into titlecase but respect the
actual uppercase
-+--
 Reporter:  areski   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  filter   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by areski):

 * cc: areski@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #21693: detaultfilter wordcap converts a string into titlecase but respect the actual uppercase

2013-12-27 Thread Django 
#21693: detaultfilter wordcap converts a string into titlecase but respect the
actual uppercase
-+
 Reporter:  areski   |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Template system  |Version:  1.6
 Severity:  Normal   |   Keywords:  filter
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  1|  UI/UX:  0
-+
 The defaultfilter title may in many cases be an issue to obtain a correct
 titlecase, for instance if the title contains acronyms or abbreviations.
 For instance, "SMS count"|title will display "Sms Count" which is not the
 desired result.

 The defaultfilter wordcap try to provide a filter for this.
 "SMS count"|wordcap -> "SMS Count"

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

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

Re: [Django] #16735: Queryset values should be aliasable

2013-12-27 Thread Django 
#16735: Queryset values should be aliasable
-+-
 Reporter:  alex.latchford@… |Owner:  nate_b
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  queryset, alias, |  Needs documentation:  0
  values |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by russellm):

 @Wraithan As far as I can make out, yes. I can't see any benefit to having
 API consistency between `values()` and `values_list()` - if only because
 `values_list()` already accepts a keyword argument, which introduces a
 whole world of pain in the API (what if you want an alias called `flat`?).

 The "`values()` is an optimisation" argument doesn't hold water for me.
 Yes, it's an optimisation. The source of the optimisation is passing less
 information on the wire during the database query (i.e., only returning
 two of 15 fields). An alias is already being used for this operation - it
 just isn't user specified. Making it user specified is a single dictionary
 lookup in a couple of key locations is a minor change in implementation
 with huge usability benefits.

 So - clean up the patch and we can get this into trunk.

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

[django/django] 3518e9: Amend test table name so it doesn't clash.

2013-12-27 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3518e9ec1f23f0278aefea6738f9d49eb7d4fe52
  
https://github.com/django/django/commit/3518e9ec1f23f0278aefea6738f9d49eb7d4fe52
  Author: Ramiro Morales 
  Date:   2013-12-27 (Fri, 27 Dec 2013)

  Changed paths:
M tests/schema/models.py

  Log Message:
  ---
  Amend test table name so it doesn't clash.

Refs #21692 and 3efd1b8b939.


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

Re: [Django] #21692: 'CREATE TABLE' of initial migration doesn't quote table name

2013-12-27 Thread Django 
#21692: 'CREATE TABLE' of initial migration doesn't quote table name
-+-
 Reporter:  ramiro   |Owner:  Ramiro
 Type:  Bug  |  Morales 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Ramiro Morales ):

 In [changeset:"3518e9ec1f23f0278aefea6738f9d49eb7d4fe52"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3518e9ec1f23f0278aefea6738f9d49eb7d4fe52"
 Amend test table name so it doesn't clash.

 Refs #21692 and 3efd1b8b939.
 }}}

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

[django/django] 3efd1b: Fixed #21692 -- Quote table name when creating it.

2013-12-27 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3efd1b8b939c0a600b2d63317d224ebaab766f01
  
https://github.com/django/django/commit/3efd1b8b939c0a600b2d63317d224ebaab766f01
  Author: Ramiro Morales 
  Date:   2013-12-27 (Fri, 27 Dec 2013)

  Changed paths:
M django/db/backends/schema.py
M tests/schema/models.py
M tests/schema/tests.py

  Log Message:
  ---
  Fixed #21692 -- Quote table name when creating it.


  Commit: 61cfcec5b7d47232a1d6facbde71d4cca35986eb
  
https://github.com/django/django/commit/61cfcec5b7d47232a1d6facbde71d4cca35986eb
  Author: Ramiro Morales 
  Date:   2013-12-27 (Fri, 27 Dec 2013)

  Changed paths:
M django/db/backends/schema.py
M tests/schema/models.py
M tests/schema/tests.py

  Log Message:
  ---
  Merge pull request #2120 from ramiro/schema-creation-quoting

Fixed #21692 -- Quote table name when creating it.


Compare: https://github.com/django/django/compare/14bcbd9937f5...61cfcec5b7d4

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

Re: [Django] #21692: 'CREATE TABLE' of initial migration doesn't quote table name

2013-12-27 Thread Django 
#21692: 'CREATE TABLE' of initial migration doesn't quote table name
-+-
 Reporter:  ramiro   |Owner:  Ramiro
 Type:  Bug  |  Morales 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Ramiro Morales ):

 In [changeset:"61cfcec5b7d47232a1d6facbde71d4cca35986eb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="61cfcec5b7d47232a1d6facbde71d4cca35986eb"
 Merge pull request #2120 from ramiro/schema-creation-quoting

 Fixed #21692 -- Quote table name when creating 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/064.7460fd16518f6e40c6a1bb155c31042d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21692: 'CREATE TABLE' of initial migration doesn't quote table name

2013-12-27 Thread Django 
#21692: 'CREATE TABLE' of initial migration doesn't quote table name
-+-
 Reporter:  ramiro   |Owner:  Ramiro
 Type:  Bug  |  Morales 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Ramiro Morales ):

 * owner:   => Ramiro Morales 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"3efd1b8b939c0a600b2d63317d224ebaab766f01"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3efd1b8b939c0a600b2d63317d224ebaab766f01"
 Fixed #21692 -- Quote table name when creating 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/064.0aa180d761fc74a118f89f28e1f6ebb8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 14bcbd: Avoided %r formatting on possibly unicode strings.

2013-12-27 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 14bcbd9937f50ec21196dbb2bc3126e6a4427b37
  
https://github.com/django/django/commit/14bcbd9937f50ec21196dbb2bc3126e6a4427b37
  Author: Aymeric Augustin 
  Date:   2013-12-27 (Fri, 27 Dec 2013)

  Changed paths:
M django/apps/base.py
M django/apps/registry.py

  Log Message:
  ---
  Avoided %r formatting on possibly unicode strings.

The u prefix looks bad on Python 2.


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

Re: [Django] #21678: Simplify Apps.register_model

2013-12-27 Thread Django 
#21678: Simplify Apps.register_model
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  app-loading  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Considering the train wreck that was #1796, it isn't too surprising that
 some code was accidentally left in even though it couldn't be encountered.

 This patch is quite safe: at worst, people will hit a RuntimeError at
 import time, which is obviously a blocker but not as perverse as app
 registry corruption.

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

Re: [Django] #21678: Simplify Apps.register_model

2013-12-27 Thread Django 
#21678: Simplify Apps.register_model
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  app-loading  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #21692: 'CREATE TABLE' of initial migration doesn't quote table name

2013-12-27 Thread Django 
#21692: 'CREATE TABLE' of initial migration doesn't quote table name
+-
 Reporter:  ramiro  |Owner:
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Ready for checkin
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by charettes):

 * stage:  Accepted => Ready for checkin


Comment:

 Patch makes sense and passes tests on Py2/3 SQLite/Postgres

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

Re: [Django] #21692: 'CREATE TABLE' of initial migration doesn't quote table name

2013-12-27 Thread Django 
#21692: 'CREATE TABLE' of initial migration doesn't quote table name
+
 Reporter:  ramiro  |Owner:
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by ramiro):

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


Comment:

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

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

Re: [Django] #21681: Simplify Apps.populate_models

2013-12-27 Thread Django 
#21681: Simplify Apps.populate_models
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  app-loading  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by aaugustin):

 This behavior was added without a test in
 c63dcdda372d4d8a37abd39432deb62b8d4b1d23 to fix #1796.

 While the example I'm showing is obviously an unintended consequence, we
 should proceed carefully.

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

Re: [Django] #21681: Simplify Apps.populate_models

2013-12-27 Thread Django 
#21681: Simplify Apps.populate_models
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  app-loading  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Regarding the 2nd point, here's an... interesting... behavior.

 {{{
 # myapp/models.py

 from django.db import models

 class MyModel(models.Model):
 pass

 first_model_class = MyModel  # save a reference

 class MyModel(models.Model):
 pass

 second_model_class = MyModel  # save a reference

 if second_model_class is first_model_class:
 raise RuntimeError("WTF")
 }}}

 Thank you
 
https://github.com/django/django/blob/efddae25/django/db/models/base.py#L153-L156.

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

Re: [Django] #21093: regressiontests.mail.tests.MailTests.test_dont_base64_encode() fails with Python >=3.3.3

2013-12-27 Thread Django 
#21093: regressiontests.mail.tests.MailTests.test_dont_base64_encode() fails 
with
Python >=3.3.3
---+
 Reporter:  Arfrever   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  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 apollo13):

 * version:  1.5 => master
 * severity:  Normal => Release blocker


Comment:

 We should review if our smtp backend properly sends mails on python 3.3+

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

Re: [Django] #21685: admin_doc/model_index.html should use application names

2013-12-27 Thread Django 
#21685: admin_doc/model_index.html should use application names
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admindocs |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by aaugustin):

 * easy:  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.204efc8001290cfde087fee6ab9c5570%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21692: 'CREATE TABLE' of initial migration doesn't quote table name

2013-12-27 Thread Django 
#21692: 'CREATE TABLE' of initial migration doesn't quote table name
+
 Reporter:  ramiro  |  Owner:
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 If yo add a model whose table name is e.g. 'select' you get this error
 when running the corresponding migration:

 Postgres:
 {{{
 LINE 1: CREATE TABLE select ("when" varchar(1) NOT NULL PRIMARY KEY)
 }}}

 SQLite:
 {{{
 near "select": syntax error
 }}}

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

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

[django/django] efddae: Refactored dumpdata with app configs instead of mo...

2013-12-27 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: efddae252ce8fe469196839a29a564c0b4942c89
  
https://github.com/django/django/commit/efddae252ce8fe469196839a29a564c0b4942c89
  Author: Aymeric Augustin 
  Date:   2013-12-27 (Fri, 27 Dec 2013)

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

  Log Message:
  ---
  Refactored dumpdata with app configs instead of models modules.


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

[django/django] 40b876: Fixed a couple flake8 warnings.

2013-12-27 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 40b876763539e1700826ebffcd9402043054b13b
  
https://github.com/django/django/commit/40b876763539e1700826ebffcd9402043054b13b
  Author: Aymeric Augustin 
  Date:   2013-12-27 (Fri, 27 Dec 2013)

  Changed paths:
M tests/apps/apps.py
M tests/apps/tests.py

  Log Message:
  ---
  Fixed a couple flake8 warnings.


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

[Django] #21691: created_models arg of post_migrate deprecated but still used

2013-12-27 Thread Django 
#21691: created_models arg of post_migrate deprecated but still used
+
   Reporter:  aaugustin |  Owner:
   Type:  Cleanup/optimization  | Status:  new
  Component:  Migrations|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 |
+
 In django.contrib.auth.management.create_superuser and
 django.contrib.sites.management.create_default_site.

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

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

Re: [Django] #21690: Confusing statement regarding the ADMIN_MEDIA_PREFIX.

2013-12-27 Thread Django 
#21690: Confusing statement regarding the ADMIN_MEDIA_PREFIX.
---+--
 Reporter:  un33k  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords:  admin media| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by un33k):

 Oh, I see.

 I was on 1.4 version of the documentation, clicked on 1.6 version (bottom
 right of the browser) to see if the docs have been updated and it switched
 to 1.6. At least the bottom right of the page was showing 1.6.

 That is why I was confused and thought it was really on 1.6 and that it
 was a leftover artifact from 1.4 that needed to be updated.

 No worries.

 Thx

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

Re: [Django] #21690: Confusing statement regarding the ADMIN_MEDIA_PREFIX.

2013-12-27 Thread Django 
#21690: Confusing statement regarding the ADMIN_MEDIA_PREFIX.
---+--
 Reporter:  un33k  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords:  admin media| Triage Stage:  Unreviewed
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:   => invalid


Comment:

 Thanks for the report, but I don't think it's confusing if you realize
 this reference is part of the 1.4 release notes. It's appropriate for
 people upgrading to 1.4 from an older release (where ADMIN_MEDIA_PREFIX
 exists).

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

Re: [Django] #21690: Confusing statement regarding the ADMIN_MEDIA_PREFIX.

2013-12-27 Thread Django 
#21690: Confusing statement regarding the ADMIN_MEDIA_PREFIX.
---+--
 Reporter:  un33k  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  admin media| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by un33k):

 ADMIN_MEDIA_PREFIX is gone, while an improper reference to it still exist
 which needs to be removed.

 Something like the following will do it.
 -

 '''This line:'''

 "If your ADMIN_MEDIA_PREFIX is set to an specific domain (e.g.
 http://media.example.com/admin/), make sure to also set your STATIC_URL
 setting to the correct URL – for example, http://media.example.com/.";

 '''Should be changed to:'''

 If your STATIC_URL is set to an specific domain (e.g.
 http://media.example.com/), make sure your admin media files are
 accessable at, for example, http://media.example.com/admin/.

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

Re: [Django] #21679: Forbid apps with conflicting labels

2013-12-27 Thread Django 
#21679: Forbid apps with conflicting labels
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 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
--+

Comment (by aaugustin):

 Yes #21683 is most likely a prerequisite to pull this off without getting
 stoned by our users.

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

Re: [Django] #21690: Confusing statement regarding the ADMIN_MEDIA_PREFIX.

2013-12-27 Thread Django 
#21690: Confusing statement regarding the ADMIN_MEDIA_PREFIX.
---+--
 Reporter:  un33k  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  admin media| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 ADMIN_MEDIA_PREFIX is gone.

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

Re: [Django] #21679: Forbid apps with conflicting labels

2013-12-27 Thread Django 
#21679: Forbid apps with conflicting labels
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 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
--+
Changes (by Twidi):

 * cc: Twidi (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/067.bc22b090cb388748f556706a9f998efd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21618: GeoDjango OpenLayers.js admin include does not work over HTTPS

2013-12-27 Thread Django 
#21618: GeoDjango OpenLayers.js admin include does not work over HTTPS
-+-
 Reporter:  kz26 |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  GIS  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  geodjango|  checkin
  openlayers gis |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by timo):

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


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

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

[Django] #21690: Confusing statement regarding the ADMIN_MEDIA_PREFIX.

2013-12-27 Thread Django 
#21690: Confusing statement regarding the ADMIN_MEDIA_PREFIX.
---+-
 Reporter:  un33k  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:  admin media
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 Confusing statement regarding the '''ADMIN_MEDIA_PREFIX'''.

 On this page:
 https://docs.djangoproject.com/en/1.6/releases/1.4/#django-contrib-admin

 (A) It says:
 "This setting has now been deprecated and replaced by the more general
 setting '''STATIC_URL'''.".

 (B) Then few lines later it says:
 "If your '''ADMIN_MEDIA_PREFIX''' ''is'' set to an specific domain (e.g.
 http://media.example.com/admin/), make sure to also set your STATIC_URL
 setting to the correct URL – for example, http://media.example.com/.";

 --
 Now: which one is it. Deprecated or not?
 If '''ADMIN_MEDIA_PREFIX''' is deprecated, then its reference in (B)
 should either be removed or changed to "If your ADMIN_MEDIA_PREFIX ''was''
 ..."

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

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

Re: [Django] #21679: Forbid apps with conflicting labels

2013-12-27 Thread Django 
#21679: Forbid apps with conflicting labels
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 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
--+
Changes (by loic84):

 * cc: loic@… (added)


Comment:

 It seems #21683 proposes to do exactly that which answers all my 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/067.a5ab8b6aa3aa10dc638e05b1bfb007e8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8307: ImageFile use of width_field and height_field is slow with remote storage backends

2013-12-27 Thread Django 
#8307: ImageFile use of width_field and height_field is slow with remote storage
backends
-+-
 Reporter:  sebastian.serrano@…  |Owner:  jacob
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  File |   Resolution:
  uploads/storage| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:  imagefile height |  Patch needs improvement:  0
  width  |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by viciu):

 * cc: wiktor@… (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/085.0d9d543777d0ae2182976a1c5cb8d8e8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21420: Runserver autoreload defect on OSX (was: Runserver autoreload defect on Windows 8)

2013-12-27 Thread Django 
#21420: Runserver autoreload defect on OSX
-+-
 Reporter:  bouke|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 Severity:  Release blocker  | 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 timo):

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


Comment:

 Hi geniofuturo,

 Looking at the first traceback, your problem seems to be an issue with
 unicode handling in either your app or grappelli:

 `UnicodeEncodeError: 'latin-1' codec can't encode character u'\u2013' in
 position 6414: ordinal not in range(256)`

 Please use our [https://docs.djangoproject.com/en/dev/#getting-help
 support channels] rather than this ticket tracker to get help.

 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/063.0e15e1e7ef15836ec38f564c7774e73b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21420: Runserver autoreload defect on Windows 8

2013-12-27 Thread Django 
#21420: Runserver autoreload defect on Windows 8
-+-
 Reporter:  bouke|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by geniofuturo@…):

 I'm using the django version 1.6.1

 Python 2.7.5
 OS: Windows 8

 Added the 'grappelli' version 2.5.1 package and am having the same
 problem.

 {{{
 0 errors found
 December 27, 2013 - 13:11:21
 Django version 1.6.1, using settings '.settings'
 Starting development server at http://127.0.0.1:8000/
 Quit the server with CTRL-BREAK.
 [27/Dec/2013 13:11:26] "GET /admin/votacao/funcionario/1/ HTTP/1.1" 200 0
 Traceback (most recent call last):
   File "C:\Python27\lib\wsgiref\handlers.py", line 86, in run
 self.finish_response()
   File "C:\Python27\lib\wsgiref\handlers.py", line 127, in finish_response
 for data in self.result:
   File "C:\Python27\lib\site-packages\django\utils\six.py", line 414, in
 next
 return type(self).__next__(self)
   File "C:\Python27\lib\site-packages\django\http\response.py", line 295,
 in __next__
 return self.make_bytes(next(self._iterator))
   File "C:\Python27\lib\site-packages\django\http\response.py", line 285,
 in make_bytes
 return bytes(value.encode(self._charset))
   File "C:\Python27\lib\site-packages\django\utils\functional.py", line
 15, in _curried
 return _curried_func(*(args + moreargs), **dict(kwargs, **morekwargs))
   File "C:\Python27\lib\site-packages\django\utils\safestring.py", line
 93, in _proxy_method
 data = method(self, *args, **kwargs)
 UnicodeEncodeError: 'latin-1' codec can't encode character u'\u2013' in
 position 6414: ordinal not in range(256)
 [27/Dec/2013 13:11:26] "GET /admin/votacao/funcionario/1/ HTTP/1.1" 500 59
 Traceback (most recent call last):
   File "C:\Python27\lib\SocketServer.py", line 593, in
 process_request_thread
 self.finish_request(request, client_address)
   File "C:\Python27\lib\SocketServer.py", line 334, in finish_request
 self.RequestHandlerClass(request, client_address, self)
   File "C:\Python27\lib\site-packages\django\core\servers\basehttp.py",
 line 126, in __init__
 super(WSGIRequestHandler, self).__init__(*args, **kwargs)
   File "C:\Python27\lib\SocketServer.py", line 649, in __init__
 self.handle()
   File "C:\Python27\lib\wsgiref\simple_server.py", line 124, in handle
 handler.run(self.server.get_app())
   File "C:\Python27\lib\wsgiref\handlers.py", line 92, in run
 self.close()
   File "C:\Python27\lib\wsgiref\simple_server.py", line 33, in close
 self.status.split(' ',1)[0], self.bytes_sent
 AttributeError: 'NoneType' object has no attribute 'split'
 
 Exception happened during processing of request from ('127.0.0.1', 57720)
 
 }}}

 Importantly, the problem only started to occur after I added the
 'grappelli' package.

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

Re: [Django] #21420: Runserver autoreload defect on Windows 8 (was: Runserver autoreload defect on OSX)

2013-12-27 Thread Django 
#21420: Runserver autoreload defect on Windows 8
-+-
 Reporter:  bouke|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Release blocker  | 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 geniofuturo@…):

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


Comment:

 I'm using the django version 1.6.1

 Python 2.7.5
 OS: Windows 8

 Added the 'grappelli' version 2.5.1 package and am having the same
 problem.

 {{{
 0 errors found
 December 27, 2013 - 13:11:21
 Django version 1.6.1, using settings 'Caefe.settings'
 Starting development server at http://127.0.0.1:8000/
 Quit the server with CTRL-BREAK.
 [27/Dec/2013 13:11:26] "GET /admin/votacao/funcionario/1/ HTTP/1.1" 200 0
 Traceback (most recent call last):
   File "C:\Python27\lib\wsgiref\handlers.py", line 86, in run
 self.finish_response()
   File "C:\Python27\lib\wsgiref\handlers.py", line 127, in finish_response
 for data in self.result:
   File "C:\Python27\lib\site-packages\django\utils\six.py", line 414, in
 next
 return type(self).__next__(self)
   File "C:\Python27\lib\site-packages\django\http\response.py", line 295,
 in __next__
 return self.make_bytes(next(self._iterator))
   File "C:\Python27\lib\site-packages\django\http\response.py", line 285,
 in make_bytes
 return bytes(value.encode(self._charset))
   File "C:\Python27\lib\site-packages\django\utils\functional.py", line
 15, in _curried
 return _curried_func(*(args + moreargs), **dict(kwargs, **morekwargs))
   File "C:\Python27\lib\site-packages\django\utils\safestring.py", line
 93, in _proxy_method
 data = method(self, *args, **kwargs)
 UnicodeEncodeError: 'latin-1' codec can't encode character u'\u2013' in
 position 6414: ordinal not in range(256)
 [27/Dec/2013 13:11:26] "GET /admin/votacao/funcionario/1/ HTTP/1.1" 500 59
 Traceback (most recent call last):
   File "C:\Python27\lib\SocketServer.py", line 593, in
 process_request_thread
 self.finish_request(request, client_address)
   File "C:\Python27\lib\SocketServer.py", line 334, in finish_request
 self.RequestHandlerClass(request, client_address, self)
   File "C:\Python27\lib\site-packages\django\core\servers\basehttp.py",
 line 126, in __init__
 super(WSGIRequestHandler, self).__init__(*args, **kwargs)
   File "C:\Python27\lib\SocketServer.py", line 649, in __init__
 self.handle()
   File "C:\Python27\lib\wsgiref\simple_server.py", line 124, in handle
 handler.run(self.server.get_app())
   File "C:\Python27\lib\wsgiref\handlers.py", line 92, in run
 self.close()
   File "C:\Python27\lib\wsgiref\simple_server.py", line 33, in close
 self.status.split(' ',1)[0], self.bytes_sent
 AttributeError: 'NoneType' object has no attribute 'split'
 
 Exception happened during processing of request from ('127.0.0.1', 57720)
 
 }}}

 Importantly, the problem only started to occur after I added the
 'grappelli' package.

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

[django/django] 3b79fb: [1.6.x] Fixed #21650 -- Corrected bad advice for p...

2013-12-27 Thread GitHub 
  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 3b79fbabcdfefa6c5734a9645be4ffee02e4a270
  
https://github.com/django/django/commit/3b79fbabcdfefa6c5734a9645be4ffee02e4a270
  Author: Tim Graham 
  Date:   2013-12-27 (Fri, 27 Dec 2013)

  Changed paths:
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  [1.6.x] Fixed #21650 -- Corrected bad advice for plural translation.

Thanks nedbatchelder and claudep.

Backport of 85270ef3f5 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/52bd969cb79b5_30786f9d48223ac%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21650: Usage example in i18n docs is bad advice for plurals

2013-12-27 Thread Django 
#21650: Usage example in i18n docs is bad advice for plurals
--+
 Reporter:  nedbatchelder |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"3b79fbabcdfefa6c5734a9645be4ffee02e4a270"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3b79fbabcdfefa6c5734a9645be4ffee02e4a270"
 [1.6.x] Fixed #21650 -- Corrected bad advice for plural translation.

 Thanks nedbatchelder and claudep.

 Backport of 85270ef3f5 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/071.87d57c2f6226d944ac0283b7bbd10884%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21650: Usage example in i18n docs is bad advice for plurals

2013-12-27 Thread Django 
#21650: Usage example in i18n docs is bad advice for plurals
--+
 Reporter:  nedbatchelder |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"85270ef3f5bf96b556e697bc5a46bf925ec4be21"]:
 {{{
 #!CommitTicketReference repository=""
 revision="85270ef3f5bf96b556e697bc5a46bf925ec4be21"
 Fixed #21650 -- Corrected bad advice for plural translation.

 Thanks nedbatchelder and claudep.
 }}}

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

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

[django/django] 85270e: Fixed #21650 -- Corrected bad advice for plural tr...

2013-12-27 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 85270ef3f5bf96b556e697bc5a46bf925ec4be21
  
https://github.com/django/django/commit/85270ef3f5bf96b556e697bc5a46bf925ec4be21
  Author: Tim Graham 
  Date:   2013-12-27 (Fri, 27 Dec 2013)

  Changed paths:
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  Fixed #21650 -- Corrected bad advice for plural translation.

Thanks nedbatchelder and claudep.


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

[django/django] 2504a5: Created a constant for the migrations module name.

2013-12-27 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2504a50cc2285b5e5f17d5403c9a79b620471b25
  
https://github.com/django/django/commit/2504a50cc2285b5e5f17d5403c9a79b620471b25
  Author: Aymeric Augustin 
  Date:   2013-12-27 (Fri, 27 Dec 2013)

  Changed paths:
M django/db/migrations/loader.py
M django/db/migrations/questioner.py

  Log Message:
  ---
  Created a constant for the migrations module name.

Mostly for consistency with MODELS_MODULE_NAME; it's unlikely to change.


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

Re: [Django] #14334: Queries don't ensure that comparison objects are the correct type

2013-12-27 Thread Django 
#14334: Queries don't ensure that comparison objects are the correct type
-+-
 Reporter:  rpbarlow |Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anubhav9042):

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


Comment:

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

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

Re: [Django] #21688: Invalidate internal caches when INSTALLED_APPS changes

2013-12-27 Thread Django 
#21688: Invalidate internal caches when INSTALLED_APPS changes
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:
 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
--+

Comment (by aaugustin):

 Obsolete utilities such as TransRealMixin should also be removed as part
 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/067.4d4ebac284067d7a7496b0312da0402d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21681: Simplify Apps.populate_models

2013-12-27 Thread Django 
#21681: Simplify Apps.populate_models
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  app-loading  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Another related issue: the current implementation of populate_models()
 isn't exactly idempotent. A recursive invocation may return while models
 aren't fully populated, and it won't set _models_loaded. This could
 probably be an issue in some cases, but it would be moot if we got rid of
 the postponing.

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

Re: [Django] #21681: Simplify Apps.populate_models

2013-12-27 Thread Django 
#21681: Simplify Apps.populate_models
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  app-loading  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by aaugustin):

 See also https://github.com/django/django/pull/2089#discussion_r8516536.

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

Re: [Django] #21677: Review Apps.get_model[s]

2013-12-27 Thread Django 
#21677: Review Apps.get_model[s]
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 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
--+

Comment (by aaugustin):

 Have a look at get_migratable_models too.

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

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

[Django] Batch modify: #21018, #21675, #21676, #21677, #21678, #21679, #21680, #21681, #21682, #21683, #21684, #21685, #21688, #21689

2013-12-27 Thread Django 
Batch modification to #21018, #21675, #21676, #21677, #21678, #21679, #21680, 
#21681, #21682, #21683, #21684, #21685, #21688, #21689 by aaugustin:
stage to Accepted

-- 
Tickets URL: 

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/20131227125722.56FE02D824B3%40ve.djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21689: Remove the only_with_models_module argument of get_app_config[s]

2013-12-27 Thread Django 
#21689: Remove the only_with_models_module argument of get_app_config[s]
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component:  Core   |   Keywords:  app-loading
  (Other)|  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 Once #21676 is done, the current logic that calls either populate_apps or
 populate_models won't make sense any more.

 At this point it would be more straightforward to remove this argument and
 let callers filter the results by themselves.

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

Re: [Django] #21688: Invalidate internal caches when INSTALLED_APPS changes

2013-12-27 Thread Django 
#21688: Invalidate internal caches when INSTALLED_APPS changes
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  app-loading  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * keywords:   => app-loading


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

[Django] #21688: Invalidate internal caches when INSTALLED_APPS changes

2013-12-27 Thread Django 
#21688: Invalidate internal caches when INSTALLED_APPS changes
+
   Reporter:  aaugustin |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Testing framework |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 |
+
 We should review all calls to `apps.get_apps_configs` and check if the
 result gets cached, either by the caller or one of its callers,
 recursively.

 When results are cached, the cache should be invalidated when
 INSTALLED_APPS changes.

 (Filed under "testing" because that's the only situation where it's legal
 to change settings and the changes go in django.test.signals.)

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

Re: [Django] #21650: Usage example in i18n docs is bad advice for plurals

2013-12-27 Thread Django 
#21650: Usage example in i18n docs is bad advice for plurals
--+
 Reporter:  nedbatchelder |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by nedbatchelder):

 Looks great, 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/071.55a3f1bf0a26cbd1e5e9467a5d92ee37%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] f00243: Don't try to load app directory templates from app...

2013-12-27 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f00243f36df8dfe504491e03be5d5aea076340b3
  
https://github.com/django/django/commit/f00243f36df8dfe504491e03be5d5aea076340b3
  Author: Florian Apolloner 
  Date:   2013-12-27 (Fri, 27 Dec 2013)

  Changed paths:
M django/template/loaders/app_directories.py

  Log Message:
  ---
  Don't try to load app directory templates from apps with a path (eg eggs)


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

[Django] #21687: Document the abstract models testing

2013-12-27 Thread Django 
#21687: Document the abstract models testing
---+
 Reporter:  jocelyn@…  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:  documentation, testing
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Testing abstract models within reusable apps is easy, as explained
 [https://code.djangoproject.com/ticket/7835#comment:24 here] or
 [http://stackoverflow.com/questions/4281670/django-best-way-to-unit-test-
 an-abstract-model here].

 I think a hint in the doc titled
 [https://docs.djangoproject.com/en/dev/topics/testing/advanced/ advanced
 testing topic] would be usefull, and you ?

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

[django/django] 6aa1a3: Properly app_template_dirs when INSTALLED_APPS cha...

2013-12-27 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6aa1a316604c063db88a8aa4cd2f25065ae1394c
  
https://github.com/django/django/commit/6aa1a316604c063db88a8aa4cd2f25065ae1394c
  Author: Florian Apolloner 
  Date:   2013-12-27 (Fri, 27 Dec 2013)

  Changed paths:
M django/template/loaders/app_directories.py
M django/test/signals.py

  Log Message:
  ---
  Properly app_template_dirs when INSTALLED_APPS change.


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

Re: [Django] #21650: Usage example in i18n docs is bad advice for plurals

2013-12-27 Thread Django 
#21650: Usage example in i18n docs is bad advice for plurals
--+
 Reporter:  nedbatchelder |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 Fine for me. Ned?

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

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