date:20130923

Re: [Django] #21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on windows

2013-09-23 Thread Django

#21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on
windows
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by manfre):

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

Re: [Django] #21145: pk_trace fails with ValueError in case when one of the three interrelated models has different primary key type than the others

2013-09-23 Thread Django

#21145: pk_trace fails with ValueError in case when one of the three 
interrelated
models has different primary key type than the others
-+-
 Reporter:  thepapermen  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by thepapermen):

 Wow, that's marvelous indeed! Than you for your efforts! That's a great
 reason to upgrade! )))

 At least, I hope that the ticket will help some unfortunate soul that
 would stumble upon the issue while still using Django 1.5.

 Good luck!

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

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

Re: [Django] #18333: Aggregating an annotated field does not quote the alias column name

2013-09-23 Thread Django

#18333: Aggregating an annotated field does not quote the alias column name
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  aggregate,annotate   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by manfre):

 * needs_tests:  1 => 0


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

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

Re: [Django] #18333: Aggregating an annotated field does not quote the alias column name

2013-09-23 Thread Django

#18333: Aggregating an annotated field does not quote the alias column name
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  aggregate,annotate   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by manfre):

 Updated pull request with test. https://github.com/django/django/pull/1674

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

Re: [Django] #17671: CursorWrapper in Python 2.7 cannot be used as a contextmanager

2013-09-23 Thread Django

#17671: CursorWrapper in Python 2.7 cannot be used as a contextmanager
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  regression   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by manfre):

 Didn't realize the previous patch didn't make it in to 1.5. Here's a pull
 request against master.

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

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

Re: [Django] #20910: Specify the filename (when appropriate) with code snippets

2013-09-23 Thread Django

#20910: Specify the filename (when appropriate) with code snippets
-+-
 Reporter:  jggramlich@… |Owner:  nsmgr8
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  tutorial, afraid-|  Needs documentation:  0
  to-commit  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

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

Re: [Django] #20910: Specify the filename (when appropriate) with code snippets

2013-09-23 Thread Django

#20910: Specify the filename (when appropriate) with code snippets
-+-
 Reporter:  jggramlich@… |Owner:  nsmgr8
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  tutorial, afraid-|  Needs documentation:  0
  to-commit  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by nsmgr8):

 I have made a new directive for prepending filename to the code snippet.
 All the code snippet in tutorial now includes the prepended filename.

 Please review:
 https://github.com/django/django/pull/1672

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

[django/django] db98c4: [1.6.x] Removed extra p (topppings->toppings)

2013-09-23 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: db98c4888419df10de057978b85f297809e7982f
  
https://github.com/django/django/commit/db98c4888419df10de057978b85f297809e7982f
  Author: Brett Koonce 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/ref/signals.txt

  Log Message:
  ---
  [1.6.x] Removed extra p (topppings->toppings)

Backport of 946a2226ea 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/5240cdea47b83_21e1317d50116447%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 13aff9: [1.5.x] Removed extra p (topppings->toppings)

2013-09-23 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 13aff91ae785b1e39948bf0431b96dc189e2b976
  
https://github.com/django/django/commit/13aff91ae785b1e39948bf0431b96dc189e2b976
  Author: Brett Koonce 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/ref/signals.txt

  Log Message:
  ---
  [1.5.x] Removed extra p (topppings->toppings)

Backport of 946a2226ea 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/5240cdebdabdd_25d733d5410823f%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 946a22: Removed extra p (topppings->toppings)

2013-09-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 946a2226eacfcbc4d7996b36fd9944debdf2d8c2
  
https://github.com/django/django/commit/946a2226eacfcbc4d7996b36fd9944debdf2d8c2
  Author: Brett Koonce 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/ref/signals.txt

  Log Message:
  ---
  Removed extra p (topppings->toppings)



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

[django/django] 45969b: Removed implication that six is part of Python std...

2013-09-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 45969bdeb56dcd1c1670860b37f96c62f977d9fd
  
https://github.com/django/django/commit/45969bdeb56dcd1c1670860b37f96c62f977d9fd
  Author: Tim Graham 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/topics/python3.txt

  Log Message:
  ---
  Removed implication that six is part of Python stdlib.



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

[django/django] 34f405: [1.6.x] Removed implication that six is part of Py...

2013-09-23 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 34f4053409da0338b4592d376e026b8ab1016c6b
  
https://github.com/django/django/commit/34f4053409da0338b4592d376e026b8ab1016c6b
  Author: Tim Graham 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/topics/python3.txt

  Log Message:
  ---
  [1.6.x] Removed implication that six is part of Python stdlib.

Backport of 45969bdeb5 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/5240c109ab043_583fc1d54956a4%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 959adc: [1.5.x] Removed implication that six is part of Py...

2013-09-23 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 959adcc1def92550966eef05622c3de30bebf855
  
https://github.com/django/django/commit/959adcc1def92550966eef05622c3de30bebf855
  Author: Tim Graham 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/topics/python3.txt

  Log Message:
  ---
  [1.5.x] Removed implication that six is part of Python stdlib.

Backport of 45969bdeb5 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/5240c104fb14_3a2e05d581575eb%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21148: Test isolation errors on master.

2013-09-23 Thread Django

#21148: Test isolation errors on master.
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  app-refactor, app,   |  Needs documentation:  0
  refactor   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Description changed by apollo13:

Old description:

> {{{
> ./runtests.py select_for_update swappable_models --settings=test_sqlite
> Creating test database for alias 'default'...
> Creating test database for alias 'other'...
> .E
> ==
> ERROR: test_generated_data (swappable_models.tests.SwappableModelTests)
> Permissions and content types are not created for a swapped model
> --
> Traceback (most recent call last):
>   File "/home/florian/sources/django.git/django/test/utils.py", line 220,
> in inner
> return test_func(*args, **kwargs)
>   File
> "/home/florian/sources/django.git/tests/swappable_models/tests.py", line
> 39, in test_generated_data
> ContentType.objects.filter(app_label='swappable_models').delete()
>   File "/home/florian/sources/django.git/django/db/models/query.py", line
> 558, in delete
> collector.delete()
>   File "/home/florian/sources/django.git/django/db/models/deletion.py",
> line 262, in delete
> qs._raw_delete(using=self.using)
>   File "/home/florian/sources/django.git/django/db/models/query.py", line
> 570, in _raw_delete
> sql.DeleteQuery(self.model).delete_qs(self, using)
>   File
> "/home/florian/sources/django.git/django/db/models/sql/subqueries.py",
> line 86, in delete_qs
> self.get_compiler(using).execute_sql(None)
>   File
> "/home/florian/sources/django.git/django/db/models/sql/compiler.py", line
> 763, in execute_sql
> cursor.execute(sql, params)
>   File "/home/florian/sources/django.git/django/db/utils.py", line 101,
> in inner
> return func(*args, **kwargs)
>   File "/home/florian/sources/django.git/django/db/utils.py", line 94, in
> __exit__
> six.reraise(dj_exc_type, dj_exc_value, traceback)
>   File "/home/florian/sources/django.git/django/db/utils.py", line 101,
> in inner
> return func(*args, **kwargs)
>   File
> "/home/florian/sources/django.git/django/db/backends/sqlite3/base.py",
> line 476, in execute
> return Database.Cursor.execute(self, query, params)
> OperationalError: no such table: multiple_database_review
>
> --
> Ran 10 tests in 0.046s
>
> FAILED (errors=1, skipped=8)
> Destroying test database for alias 'default'...
> Destroying test database for alias 'other'...
> }}}
>
> This is caused by #15903 -- I don't see an obvious fix though, some stuff
> requires all models to be registered (tests come to mind where you change
> INSTALLED_APPS on demand, but the related cache is only filled once)
> while other stuff (like the collector) should never see models from not
> installed applications.

New description:

 {{{
 ./runtests.py select_for_update swappable_models --settings=test_sqlite
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 .E
 ==
 ERROR: test_generated_data (swappable_models.tests.SwappableModelTests)
 Permissions and content types are not created for a swapped model
 --
 Traceback (most recent call last):
   File "/home/florian/sources/django.git/django/test/utils.py", line 220,
 in inner
 return test_func(*args, **kwargs)
   File "/home/florian/sources/django.git/tests/swappable_models/tests.py",
 line 39, in test_generated_data
 ContentType.objects.filter(app_label='swappable_models').delete()
   File "/home/florian/sources/django.git/django/db/models/query.py", line
 558, in delete
 collector.delete()
   File "/home/florian/sources/django.git/django/db/models/deletion.py",
 line 262, in delete
 qs._raw_delete(using=self.using)
   File "/home/florian/sources/django.git/django/db/models/query.py", line
 570, in _raw_delete
 sql.DeleteQuery(self.model).delete_qs(self, using)
   File
 "/home/florian/sources/django.git/django/db/models/sql/subqueries.py",
 line 86, in delete_qs
 self.get_compiler(using).execute_sql(None)
   File

Re: [Django] #21148: Test isolation errors on master.

2013-09-23 Thread Django

#21148: Test isolation errors on master.
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  app-refactor, app,   |  Needs documentation:  0
  refactor   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Description changed by apollo13:

Old description:

> ```
> ./runtests.py select_for_update swappable_models --settings=test_sqlite
> Creating test database for alias 'default'...
> Creating test database for alias 'other'...
> .E
> ==
> ERROR: test_generated_data (swappable_models.tests.SwappableModelTests)
> Permissions and content types are not created for a swapped model
> --
> Traceback (most recent call last):
>   File "/home/florian/sources/django.git/django/test/utils.py", line 220,
> in inner
> return test_func(*args, **kwargs)
>   File
> "/home/florian/sources/django.git/tests/swappable_models/tests.py", line
> 39, in test_generated_data
> ContentType.objects.filter(app_label='swappable_models').delete()
>   File "/home/florian/sources/django.git/django/db/models/query.py", line
> 558, in delete
> collector.delete()
>   File "/home/florian/sources/django.git/django/db/models/deletion.py",
> line 262, in delete
> qs._raw_delete(using=self.using)
>   File "/home/florian/sources/django.git/django/db/models/query.py", line
> 570, in _raw_delete
> sql.DeleteQuery(self.model).delete_qs(self, using)
>   File
> "/home/florian/sources/django.git/django/db/models/sql/subqueries.py",
> line 86, in delete_qs
> self.get_compiler(using).execute_sql(None)
>   File
> "/home/florian/sources/django.git/django/db/models/sql/compiler.py", line
> 763, in execute_sql
> cursor.execute(sql, params)
>   File "/home/florian/sources/django.git/django/db/utils.py", line 101,
> in inner
> return func(*args, **kwargs)
>   File "/home/florian/sources/django.git/django/db/utils.py", line 94, in
> __exit__
> six.reraise(dj_exc_type, dj_exc_value, traceback)
>   File "/home/florian/sources/django.git/django/db/utils.py", line 101,
> in inner
> return func(*args, **kwargs)
>   File
> "/home/florian/sources/django.git/django/db/backends/sqlite3/base.py",
> line 476, in execute
> return Database.Cursor.execute(self, query, params)
> OperationalError: no such table: multiple_database_review
>
> --
> Ran 10 tests in 0.046s
>
> FAILED (errors=1, skipped=8)
> Destroying test database for alias 'default'...
> Destroying test database for alias 'other'...
> ```
>
> This is caused by #15903 -- I don't see an obvious fix though, some stuff
> requires all models to be registered (tests come to mind where you change
> INSTALLED_APPS on demand, but the related cache is only filled once)
> while other stuff (like the collector) should never see models from not
> installed applications.

New description:

 {{{
 ./runtests.py select_for_update swappable_models --settings=test_sqlite
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 .E
 ==
 ERROR: test_generated_data (swappable_models.tests.SwappableModelTests)
 Permissions and content types are not created for a swapped model
 --
 Traceback (most recent call last):
   File "/home/florian/sources/django.git/django/test/utils.py", line 220,
 in inner
 return test_func(*args, **kwargs)
   File "/home/florian/sources/django.git/tests/swappable_models/tests.py",
 line 39, in test_generated_data
 ContentType.objects.filter(app_label='swappable_models').delete()
   File "/home/florian/sources/django.git/django/db/models/query.py", line
 558, in delete
 collector.delete()
   File "/home/florian/sources/django.git/django/db/models/deletion.py",
 line 262, in delete
 qs._raw_delete(using=self.using)
   File "/home/florian/sources/django.git/django/db/models/query.py", line
 570, in _raw_delete
 sql.DeleteQuery(self.model).delete_qs(self, using)
   File
 "/home/florian/sources/django.git/django/db/models/sql/subqueries.py",
 line 86, in delete_qs
 self.get_compiler(using).execute_sql(None)
   File

[Django] #21148: Test isolation errors on master.

2013-09-23 Thread Django

#21148: Test isolation errors on master.
-+-
   Reporter:  apollo13   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  master
  layer (models, ORM)|   Keywords:  app-refactor, app,
   Severity:  Normal |  refactor
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 ```
 ./runtests.py select_for_update swappable_models --settings=test_sqlite
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 .E
 ==
 ERROR: test_generated_data (swappable_models.tests.SwappableModelTests)
 Permissions and content types are not created for a swapped model
 --
 Traceback (most recent call last):
   File "/home/florian/sources/django.git/django/test/utils.py", line 220,
 in inner
 return test_func(*args, **kwargs)
   File "/home/florian/sources/django.git/tests/swappable_models/tests.py",
 line 39, in test_generated_data
 ContentType.objects.filter(app_label='swappable_models').delete()
   File "/home/florian/sources/django.git/django/db/models/query.py", line
 558, in delete
 collector.delete()
   File "/home/florian/sources/django.git/django/db/models/deletion.py",
 line 262, in delete
 qs._raw_delete(using=self.using)
   File "/home/florian/sources/django.git/django/db/models/query.py", line
 570, in _raw_delete
 sql.DeleteQuery(self.model).delete_qs(self, using)
   File
 "/home/florian/sources/django.git/django/db/models/sql/subqueries.py",
 line 86, in delete_qs
 self.get_compiler(using).execute_sql(None)
   File
 "/home/florian/sources/django.git/django/db/models/sql/compiler.py", line
 763, in execute_sql
 cursor.execute(sql, params)
   File "/home/florian/sources/django.git/django/db/utils.py", line 101, in
 inner
 return func(*args, **kwargs)
   File "/home/florian/sources/django.git/django/db/utils.py", line 94, in
 __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/home/florian/sources/django.git/django/db/utils.py", line 101, in
 inner
 return func(*args, **kwargs)
   File
 "/home/florian/sources/django.git/django/db/backends/sqlite3/base.py",
 line 476, in execute
 return Database.Cursor.execute(self, query, params)
 OperationalError: no such table: multiple_database_review

 --
 Ran 10 tests in 0.046s

 FAILED (errors=1, skipped=8)
 Destroying test database for alias 'default'...
 Destroying test database for alias 'other'...
 ```

 This is caused by #15903 -- I don't see an obvious fix though, some stuff
 requires all models to be registered (tests come to mind where you change
 INSTALLED_APPS on demand, but the related cache is only filled once) while
 other stuff (like the collector) should never see models from not
 installed applications.

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

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

[django/django] ab643c: Fixed test suite bisection on Python 3.

2013-09-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ab643cd63402ef8ed4776faebc0ed4f00b933e1d
  
https://github.com/django/django/commit/ab643cd63402ef8ed4776faebc0ed4f00b933e1d
  Author: Simon Charette 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M tests/runtests.py

  Log Message:
  ---
  Fixed test suite bisection on Python 3.

Thanks to @marfire for spotting this.



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

Re: [Django] #19649: Cookie message storage does not set Vary: Cookie

2013-09-23 Thread Django

Comment (by carljm):

Replying to [comment:5 bigkevmcd]:
> Adding the Vary: Cookie header when set_cookie is called on the response
is trivial enough, connecting access to the request to changes in the
response would be a lot more complex from what I can see.
>
> I'm happy to put up a pull-request with test/fix for set_cookie if
that's a start.

Unfortunately that doesn't fix the problem. It's not just the response
with the Set-Cookie header that needs Vary: Cookie, it's every subsequent
response that makes decisions based on the cookie values that came in with
the request.

Any real fix for this problem will need to involve setting Vary: Cookie on
the response based on access to the request. Which means it will either
need to happen in the request handler itself or in a response middleware,
since that's where we have access to both request and response. The two
choices I presented in the ticket description are either to have
`contrib.messages` handle this for itself (in which case it would happen
in the `MessageMiddleware`), or for Django to handle it generally, in
which case there would be a design decision: either it would need to be
hardcoded behavior in the request handler, or it could be handled in
`CommonMiddleware`.

I still think that having Django handle it is the right approach. My gut
feeling is that this is core HTTP behavior and thus it makes sense to bake
it right into `BaseHandler`, since there is no guarantee people are using
`CommonMiddleware`, but I could be talked out of that. I'd need to play
around with an implementation and see how it looks.

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

Re: [Django] #19649: Cookie message storage does not set Vary: Cookie

2013-09-23 Thread Django

#19649: Cookie message storage does not set Vary: Cookie
---+-
 Reporter:  carljm |Owner:  bigkevmcd
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  1.4
 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 bigkevmcd):

 Adding the Vary: Cookie header when set_cookie is called on the response
 is trivial enough, connecting access to the request to changes in the
 response would be a lot more complex from what I can see.

 I'm happy to put up a pull-request with test/fix for set_cookie if that's
 a start.

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

[django/django] 411676: Fixed #14028 - Added validation for clashing db_co...

2013-09-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 41167645b1039067127fa215d4d28296bfa4cfdc
  
https://github.com/django/django/commit/41167645b1039067127fa215d4d28296bfa4cfdc
  Author: Helen ST 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M django/core/management/validation.py
M tests/invalid_models/invalid_models/models.py

  Log Message:
  ---
  Fixed #14028 - Added validation for clashing db_columns.

Thanks akaariai 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/524063bb53057_2059a9d54109155%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14028: setting db_column to same value as another column should not validate

2013-09-23 Thread Django

#14028: setting db_column to same value as another column should not validate
-+-
 Reporter:  akaariai |Owner:  helenst
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  validation,  |  Needs documentation:  0
  sprintdec2010  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"41167645b1039067127fa215d4d28296bfa4cfdc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="41167645b1039067127fa215d4d28296bfa4cfdc"
 Fixed #14028 - Added validation for clashing db_columns.

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

Re: [Django] #21001: Non working SQL generated for Oracle when doing .exclude('')

2013-09-23 Thread Django

#21001: Non working SQL generated for Oracle when doing .exclude('')
-+-
 Reporter:  greenRocker  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (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|
-+-
Changes (by charettes):

 * status:  closed => new
 * has_patch:  0 => 1
 * resolution:  fixed =>
 * stage:  Unreviewed => Accepted


Comment:

 The patch makes sense but I unfortunately don't have an Oracle setup to
 test the provided patch on 1.4 and master thus I can't mark the patch as
 RFC.

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

[django/django] 4ec6d2: Fixed #21001 -- Added a regression test for empty ...

2013-09-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4ec6d281cdc67bee1c7ac272272ae500b600fe49
  
https://github.com/django/django/commit/4ec6d281cdc67bee1c7ac272272ae500b600fe49
  Author: Simon Charette 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M tests/queries/tests.py

  Log Message:
  ---
  Fixed #21001 -- Added a regression test for empty string exclusion on Oracle.

The issue was present in 1.4.x but has been reported to be fixed in master.

Thanks to @timgraham for the 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/5240878f8b6b2_214ddfd4c908d8%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21001: Non working SQL generated for Oracle when doing .exclude('')

2013-09-23 Thread Django

#21001: Non working SQL generated for Oracle when doing .exclude('')
-+-
 Reporter:  greenRocker  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 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|
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"4ec6d281cdc67bee1c7ac272272ae500b600fe49"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4ec6d281cdc67bee1c7ac272272ae500b600fe49"
 Fixed #21001 -- Added a regression test for empty string exclusion on
 Oracle.

 The issue was present in 1.4.x but has been reported to be fixed in
 master.

 Thanks to @timgraham for the 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/069.7f4d98e359dd6b873b53567ab82039ba%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] cdb567: [1.6.x] Fixed #21120 -- Added more explicit text o...

2013-09-23 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: cdb56725d4424cc58147e2ffd4426511aa95775e
  
https://github.com/django/django/commit/cdb56725d4424cc58147e2ffd4426511aa95775e
  Author: Ben Huckvale 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/ref/forms/validation.txt

  Log Message:
  ---
  [1.6.x] Fixed #21120 -- Added more explicit text on using validators and link 
to writing validators.

Thanks nicolas at niconomicon.net for the suggestion.

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

Re: [Django] #8620: ModelForm.Meta.exclude only excludes model fields, not form fields

2013-09-23 Thread Django

#8620: ModelForm.Meta.exclude only excludes model fields, not form fields
-+
 Reporter:  levity   |Owner:  loic84
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by loic84):

 * status:  new => assigned
 * owner:  shimonrura => loic84


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

Re: [Django] #21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on windows

2013-09-23 Thread Django

#21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on
windows
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by manfre):

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

 The newly added {{{get_backend_timeout}}} is intentionally not documented
 to avoid it becoming an officially supported part of the API.

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

[django/django] 6a3007: Fixed #21140 -- Added 'Using cached sessions' to t...

2013-09-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6a30075eaa52b3d91665195a34901ac450df5bbb
  
https://github.com/django/django/commit/6a30075eaa52b3d91665195a34901ac450df5bbb
  Author: Åke Forslund 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/topics/performance.txt

  Log Message:
  ---
  Fixed #21140 -- Added 'Using cached sessions' to the performance guide.

Thanks EvilDMP 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/52405597ee791_2fa1413d58969f2%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #4492: Provide tests for mixed-case column names

2013-09-23 Thread Django

#4492: Provide tests for mixed-case column names
-+-
 Reporter:  John Shaffer |Owner:  nobody
     |   Status:  closed
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:  fixed
Component:  Database layer   | Triage Stage:  Accepted
  (models, ORM)  |  Needs documentation:  0
 Severity:  Normal   |  Patch needs improvement:  1
 Keywords:  postgresql psycopg   |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by timo):

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


Comment:

 On further investigation, I think we have tests to cover this. In
 particular, if I comment out the fix from [6507], I get a failure in
 `test_generic_relation (backends.tests.SequenceResetTest)`, and here are
 some models with mixed case column names:

 {{{
 aggregation_regress/models.py:Entry = models.CharField(unique=True,
 max_length=50)
 aggregation_regress/models.py:Clue = models.CharField(max_length=150)
 }}}

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

[django/django] a722df: [1.5.x] Fixed #21120 -- Added more explicit text o...

2013-09-23 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: a722dfda93eafd6ff02b91f7a222eaccfc444ef4
  
https://github.com/django/django/commit/a722dfda93eafd6ff02b91f7a222eaccfc444ef4
  Author: Ben Huckvale 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/ref/forms/validation.txt

  Log Message:
  ---
  [1.5.x] Fixed #21120 -- Added more explicit text on using validators and link 
to writing validators.

Thanks nicolas at niconomicon.net for the suggestion.

Backport of 98e0453f00 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/52405592ea47d_2a609fbd48935bb%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e15f7f: Fixed #21070 -- Added a more complex database conf...

2013-09-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e15f7f31d048ead5453b5ee810235cf88b42b3cc
  
https://github.com/django/django/commit/e15f7f31d048ead5453b5ee810235cf88b42b3cc
  Author: Louis Fill 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  Fixed #21070 -- Added a more complex database configuration example.

Thanks joejasinski 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/524069dbd22f0_3a60ca1d541299fc%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21120: documentation talks about validators but separates definition and usage

2013-09-23 Thread Django

#21120: documentation talks about validators but separates definition and usage
-+-
 Reporter:  nicolas@…|Owner:
 Type:   |  benhuckvale
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:  afraid-to-commit |   Resolution:  fixed
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"cdb56725d4424cc58147e2ffd4426511aa95775e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cdb56725d4424cc58147e2ffd4426511aa95775e"
 [1.6.x] Fixed #21120 -- Added more explicit text on using validators and
 link to writing validators.

 Thanks nicolas at niconomicon.net for the suggestion.

 Backport of 98e0453f00 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/081.6671fe5f2ba670e2522cb798252c7dd5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on windows

2013-09-23 Thread Django

#21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on
windows
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Core (Cache system)  |  Version:
 Severity:  Release blocker  |  1.6-beta-1
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by manfre):

 * stage:  Unreviewed => Accepted


Comment:

 Regression introduced with changeset
 89955cc35f3636684ea6f2a6c9504b35a3050f0f #9595

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

Re: [Django] #21070: Clarify document DATABASES change

2013-09-23 Thread Django

#21070: Clarify document DATABASES change
--+
 Reporter:  joejasinski   |Owner:  LouisF
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"a6a5c8b06df9334e546795b96566d25c6396209a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a6a5c8b06df9334e546795b96566d25c6396209a"
 [1.6.x] Fixed #21070 -- Added a more complex database configuration
 example.

 Thanks joejasinski for the suggestion.

 Backport of e15f7f31d0 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/069.1fbdcee04b35a8905796192b0406d83e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] a6a5c8: [1.6.x] Fixed #21070 -- Added a more complex datab...

2013-09-23 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: a6a5c8b06df9334e546795b96566d25c6396209a
  
https://github.com/django/django/commit/a6a5c8b06df9334e546795b96566d25c6396209a
  Author: Louis Fill 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  [1.6.x] Fixed #21070 -- Added a more complex database configuration example.

Thanks joejasinski for the suggestion.

Backport of e15f7f31d0 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/52406a0d34e30_642c57bd54732d%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21070: Clarify document DATABASES change

2013-09-23 Thread Django

#21070: Clarify document DATABASES change
--+
 Reporter:  joejasinski   |Owner:  LouisF
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e15f7f31d048ead5453b5ee810235cf88b42b3cc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e15f7f31d048ead5453b5ee810235cf88b42b3cc"
 Fixed #21070 -- Added a more complex database configuration example.

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

Re: [Django] #20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"

2013-09-23 Thread Django

#20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"
-+-
 Reporter:  glarrain |Owner:  dchetwynd
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  six, python3,| Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by dchetwynd):

 I have submitted a pull request for this ticket fix.

 As per timo's confirmation that the linking issue is fixed in Sphinx
 1.2b2, I have not changed this. I have modified a few of the link targets,
 added a couple of extra sentences to clarify that Django uses a customised
 version of the six module and changed a section header.

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

Re: [Django] #21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on windows

2013-09-23 Thread Django

#21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on
windows
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by manfre):

 * type:  Uncategorized => Bug
 * severity:  Release blocker => Normal


Comment:

 Not a regression. After manually adding the failing test to 1.5.4, it
 still fails. Issue is due to precision of {{{time.time()}} and the speed
 of the system running the tests. On Windows, the precision is ~15 ms.

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

Re: [Django] #21120: documentation talks about validators but separates definition and usage

2013-09-23 Thread Django

#21120: documentation talks about validators but separates definition and usage
-+-
 Reporter:  nicolas@…|Owner:
 Type:   |  benhuckvale
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:  afraid-to-commit |   Resolution:  fixed
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"a722dfda93eafd6ff02b91f7a222eaccfc444ef4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a722dfda93eafd6ff02b91f7a222eaccfc444ef4"
 [1.5.x] Fixed #21120 -- Added more explicit text on using validators and
 link to writing validators.

 Thanks nicolas at niconomicon.net for the suggestion.

 Backport of 98e0453f00 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/081.13b9a2e01c71f8a67a64b8e77d64dc27%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on windows

2013-09-23 Thread Django

#21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on
windows
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Core (Cache system)  |  Version:
 Severity:  Release blocker  |  1.6-beta-1
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:
  Needs tests:  0|  Unreviewed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by manfre):

 * needs_better_patch:   => 0
 * version:  master => 1.6-beta-1
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Worked with Django 1.5. This is a regression.

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

Re: [Django] #21140: Perfomance documentation should mention cached sessions

2013-09-23 Thread Django

#21140: Perfomance documentation should mention cached sessions
--+--
 Reporter:  EvilDMP   |Owner:  forslund
 Type:  Uncategorized |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6a30075eaa52b3d91665195a34901ac450df5bbb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6a30075eaa52b3d91665195a34901ac450df5bbb"
 Fixed #21140 -- Added 'Using cached sessions' to the performance guide.

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

Re: [Django] #20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"

2013-09-23 Thread Django

#20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"
-+-
 Reporter:  glarrain |Owner:  dchetwynd
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  six, python3,| Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Tim Graham ):

 In [changeset:"5e549e7efe7fc5b29124846278a6b30332e40dc4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5e549e7efe7fc5b29124846278a6b30332e40dc4"
 [1.6.x] Fixed #20830 -- Clarified that Django uses a customized version of
 six.

 Thanks glarrain for the suggestion.

 Backport of a53caf28bf 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/066.81e581b84c817057126728971ba2bdcf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"

2013-09-23 Thread Django

#20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"
-+-
 Reporter:  glarrain |Owner:  dchetwynd
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  six, python3,| Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"a53caf28bf2ab29cf4e78a968b3887ddb6d6e83d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a53caf28bf2ab29cf4e78a968b3887ddb6d6e83d"
 Fixed #20830 -- Clarified that Django uses a customized version of six.

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

Re: [Django] #4492: Provide tests for mixed-case column names

2013-09-23 Thread Django

#4492: Provide tests for mixed-case column names
-+-
 Reporter:  John Shaffer |Owner:  nobody
     |   Status:  new
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:
Component:  Database layer   | Triage Stage:  Accepted
  (models, ORM)  |  Needs documentation:  0
 Severity:  Normal   |  Patch needs improvement:  1
 Keywords:  postgresql psycopg   |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by velis):

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

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

[django/django] c695f2: [1.5.x] Fixed #20830 -- Clarified that Django uses...

2013-09-23 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: c695f293e3ce74657268e532ee69ae64c92bfa1c
  
https://github.com/django/django/commit/c695f293e3ce74657268e532ee69ae64c92bfa1c
  Author: Daley Chetwynd 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/topics/python3.txt

  Log Message:
  ---
  [1.5.x] Fixed #20830 -- Clarified that Django uses a customized version of 
six.

Thanks glarrain for the suggestion.

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

[django/django] 5e549e: [1.6.x] Fixed #20830 -- Clarified that Django uses...

2013-09-23 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 5e549e7efe7fc5b29124846278a6b30332e40dc4
  
https://github.com/django/django/commit/5e549e7efe7fc5b29124846278a6b30332e40dc4
  Author: Daley Chetwynd 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/topics/python3.txt

  Log Message:
  ---
  [1.6.x] Fixed #20830 -- Clarified that Django uses a customized version of 
six.

Thanks glarrain for the suggestion.

Backport of a53caf28bf 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/52405944d3b76_645adffd54933eb%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"

2013-09-23 Thread Django

#20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"
-+-
 Reporter:  glarrain |Owner:  dchetwynd
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  six, python3,| Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Tim Graham ):

 In [changeset:"c695f293e3ce74657268e532ee69ae64c92bfa1c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c695f293e3ce74657268e532ee69ae64c92bfa1c"
 [1.5.x] Fixed #20830 -- Clarified that Django uses a customized version of
 six.

 Thanks glarrain for the suggestion.

 Backport of a53caf28bf 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/066.f0fba6cf2c94e2458934628700b89966%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] a53caf: Fixed #20830 -- Clarified that Django uses a custo...

2013-09-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a53caf28bf2ab29cf4e78a968b3887ddb6d6e83d
  
https://github.com/django/django/commit/a53caf28bf2ab29cf4e78a968b3887ddb6d6e83d
  Author: Daley Chetwynd 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/topics/python3.txt

  Log Message:
  ---
  Fixed #20830 -- Clarified that Django uses a customized version of six.

Thanks glarrain 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/5240588852d62_bfea09d58838a3%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19941: Make running django's test suite easier

2013-09-23 Thread Django

#19941: Make running django's test suite easier
--+
 Reporter:  akaariai  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by akaariai):

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


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

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

[django/django] 98e045: Fixed #21120 -- Added more explicit text on using ...

2013-09-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 98e0453f00958af63b50e70990903eb6a04e1933
  
https://github.com/django/django/commit/98e0453f00958af63b50e70990903eb6a04e1933
  Author: Ben Huckvale 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/ref/forms/validation.txt

  Log Message:
  ---
  Fixed #21120 -- Added more explicit text on using validators and link to 
writing validators.

Thanks nicolas at niconomicon.net 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/524052861f024_6341223d5430140%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on windows

2013-09-23 Thread Django

#21147: cache.tests.FileBasedCacheTests.test_zero_timeout fails with sqlite on
windows
-+
 Reporter:  manfre   |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Core (Cache system)  |Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 {{{cache.tests.FileBasedCacheTests.test_zero_timeout}}} fails with sqlite
 on windows.

 {{{
 ==
 FAIL: test_zero_timeout (cache.tests.FileBasedCacheTests)
 --
 Traceback (most recent call last):
   File "C:\projects\django\django\tests\cache\tests.py", line 466, in
 test_zero_timeout
 self.assertEqual(self.cache.get('key1'), None)
 AssertionError: u'eggs' != None
 }}}

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

Re: [Django] #21120: documentation talks about validators but separates definition and usage

2013-09-23 Thread Django

#21120: documentation talks about validators but separates definition and usage
-+-
 Reporter:  nicolas@…|Owner:
 Type:   |  benhuckvale
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:  afraid-to-commit |   Resolution:  fixed
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"98e0453f00958af63b50e70990903eb6a04e1933"]:
 {{{
 #!CommitTicketReference repository=""
 revision="98e0453f00958af63b50e70990903eb6a04e1933"
 Fixed #21120 -- Added more explicit text on using validators and link to
 writing validators.

 Thanks nicolas at niconomicon.net 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/081.132512314a90992a5edcee211a562f20%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21070: Clarify document DATABASES change

2013-09-23 Thread Django

#21070: Clarify document DATABASES change
--+
 Reporter:  joejasinski   |Owner:  LouisF
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by LouisF):

 Here is an idea:

 https://github.com/tkman/django/compare/development

 Please have a look and I Will send a pull request if your happy.

 It's based on Joe Jasinski's suggestion in the original ticket
 description.

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

Re: [Django] #18866: model Meta verbose_name too long error message not obvious

2013-09-23 Thread Django

#18866: model Meta verbose_name too long error message not obvious
--+
 Reporter:  elena |Owner:  toyg
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by toyg):

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


Comment:

 Ok, using this bug to track *validation* only - the actual limit will stay
 at 39 as per #8162.

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

Re: [Django] #21142: Referencing the User model and migrations

2013-09-23 Thread Django

#21142: Referencing the User model and migrations
-+
 Reporter:  mario.pfeifer@…  |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  Migration, Auth  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by bmispelon):

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


Comment:

 Hi,

 I can reproduce the issue and from what I can tell, you're following the
 documentation (both for referencing the user model and for making/applying
 migrations) so this is most likely a bug.

 Thanks for the detailed 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/082.46b8f61368a78067d2869473bd99b7ef%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18866: model Meta verbose_name too long error message not obvious

2013-09-23 Thread Django

#18866: model Meta verbose_name too long error message not obvious
--+
 Reporter:  elena |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by toyg):

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


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

Re: [Django] #18866: model Meta verbose_name too long error message not obvious

2013-09-23 Thread Django

#18866: model Meta verbose_name too long error message not obvious
--+-
 Reporter:  elena |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.4
 Severity:  Normal|   Resolution:  duplicate
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by toyg):

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


Comment:

 Duplicate of #8548 and #8162

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

Re: [Django] #21120: documentation talks about validators but separates definition and usage

2013-09-23 Thread Django

#21120: documentation talks about validators but separates definition and usage
-+-
 Reporter:  nicolas@…|Owner:
 Type:   |  benhuckvale
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:  afraid-to-commit |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by benhuckvale):

 I made some changes along the lines suggested, including the link to the
 validators reference guide.
 Pull request is https://github.com/django/django/pull/1663.

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

Re: [Django] #19954: Storing of Binary fields leads to Exceptions

2013-09-23 Thread Django

#19954: Storing of Binary fields leads to Exceptions
-+-
 Reporter:  marcel.ryser.ch@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by webadmin@…):

 Since this was introduced in django 1.5 can the fix also be included in
 the 1.5 branch?

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

Re: [Django] #14028: setting db_column to same value as another column should not validate

2013-09-23 Thread Django

#14028: setting db_column to same value as another column should not validate
-+-
 Reporter:  akaariai |Owner:  helenst
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  validation,  |  Needs documentation:  0
  sprintdec2010  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by helenst):

 I have created a pull request which fixes this:

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

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

Re: [Django] #21072: Square Bullets

2013-09-23 Thread Django

#21072: Square Bullets
-+-
 Reporter:  moc@…|Owner:  amney
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-alpha-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  bullet indentation,  | Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by timo):

 Oops, commit message mistakenly referenced ticket #21702 so this didn't
 get closed automatically.

 commits are
 * 3fd769d03d401b725995792edf83715c0fe1f6da (djangoproject.com)
 * c81b6f7b834da8d8fbcf679679ce158173df3a05 (django)

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

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

Re: [Django] #21072: Square Bullets

2013-09-23 Thread Django

#21072: Square Bullets
-+-
 Reporter:  moc@…|Owner:  amney
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-alpha-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  bullet indentation,  | Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by amney):

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


Comment:

 Fix merged into both repositories successfully

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

Re: [Django] #18866: model Meta verbose_name too long error message not obvious

2013-09-23 Thread Django

Comment (by toyg):

Ok, the problem is a bit more complex, and the abovementioned patch does
not fix it.

The problem is that verbose_name is used to generate the auth_permission
table; the "name" field in that table is set to varchar(50) (at least on
PostgreSQL), but this record actually includes sentences ("Can add
", "Can delete " and so on); so '''the actual
practical limit is 39 characters for verbose_name'''. This is a weird
number, common knowledge is that verbose_name can be up to 50 characters.

So the real fix is either to widen that field to 61 or more (50 + "Can
delete ", which is 11 characters), or document that the limit is 39 on
non-sqlite backends.

I have a test and a fix for the validator to spot values that are too
long, but there's no point in submitting a pull request if this point
isn't settled first.

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

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

Re: [Django] #21145: pk_trace fails with ValueError in case when one of the three interrelated models has different primary key type than the others

2013-09-23 Thread Django

#21145: pk_trace fails with ValueError in case when one of the three 
interrelated
models has different primary key type than the others
-+-
 Reporter:  thepapermen  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bmispelon):

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


Comment:

 Hi,

 The issue is not present on the master branch and from a quick `git
 bisect`, it looks like it was fixed in commit
 69597e5bcc89aadafd1b76abf7efab30ee0b8b1a.

 Consequently, I'll mark this ticket as `resolved`.

 Thanks for the detailed 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/069.b79d3dd90bfc9a254b1c3f1bc9e88d7f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21146: DatabaseCache doesn't work if database backend returns datetime values as strings

2013-09-23 Thread Django

#21146: DatabaseCache doesn't work if database backend returns datetime values 
as
strings
-+---
 Reporter:  manfre   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Cache system)  |Version:  master
 Severity:  Normal   |   Keywords:  DatabaseCache
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+---
 DatabaseCache intentionally uses cursors and converts all datetimes to
 naive values. This is a problem for database backends that return
 datetimes from the database as strings that must be converted to a
 datetime before being used. All reads of the '''expires''' column should
 be passed through {{{DatabaseOperations.convert_values}}}, and
 {{{timezone.make_naive}}} to maintain the current naive-only datetimes
 behavior.

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

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

Re: [Django] #21145: pk_trace fails with ValueError in case when one of the three interrelated models has different primary key type than the others

2013-09-23 Thread Django

#21145: pk_trace fails with ValueError in case when one of the three 
interrelated
models has different primary key type than the others
-+-
 Reporter:  thepapermen  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by thepapermen):

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


Comment:

 I'd also like to point that you need a relationship that spans at least
 three models. Two models are not enough to trigger the bug.

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

Re: [Django] #20364: urlize incorrectly includes quotation marks in links

2013-09-23 Thread Django

#20364: urlize incorrectly includes quotation marks in links
-+-
 Reporter:  EmilStenstrom|Owner:  anonymous
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  urlize, quotes   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by GilesGreenway):

 Test pushed, pull request made:
 == https://github.com/django/django/pull/1662 ==

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

[Django] #21145: pk_trace fails with ValueError in case when one of the three interrelated models has different primary key type than the others

2013-09-23 Thread Django

#21145: pk_trace fails with ValueError in case when one of the three 
interrelated
models has different primary key type than the others
--+
 Reporter:  thepapermen   |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5
 Severity:  Release blocker   |   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 In a project in which all of the models have UUIDs as the primary key,
 including the custom user model, this bug renders `django.contrib.auth`
 permission checking unusable (because the Group and Permission models have
 integer primary keys, but the user has UUID one).

 `Permission.objects.filter(**{user_groups_query: user_obj})` in
 `django.contrib.auth.backends.py` fails.

 This bug also renders `django guardian` 3-rd party app unusable.

 The root of the issue is that `pk_trace` incorrectly retrieves the primary
 key type from intermediary model instead of the last model in the chain.

 See line 212:
 
https://github.com/django/django/blob/d04e8f8c7869b79a6f848a94bd51ce71223c2df2/django/db/models/fields/related.py

 Run `check()` below to reproduce:

 {{{
 from django.db import models
 import string
 import random


 class ModelA(models.Model):
 pass


 class ModelB(models.Model):
 modela = models.ManyToManyField(ModelA, blank=True, null=True, )


 class ModelC(models.Model):
 id = models.CharField(primary_key=True, max_length=1)  # Or any non-
 integer PK field
 modelb = models.ManyToManyField(ModelB, blank=True, null=True, )


 def check():
 """
 This function will fail with ValueError: invalid literal for int()
 with base 10: 'y'
 which, in turn, points us to the fact that pk_trace for pk of ModelC
 tries to operate
 with field type of ModelB instead.

 See line 212:
 
https://github.com/django/django/blob/d04e8f8c7869b79a6f848a94bd51ce71223c2df2/django/db/models/fields/related.py
 """
 a = ModelA.objects.create()

 b = ModelB.objects.create()
 b.modela.add(a)

 c = ModelC.objects.create(id=random.choice(string.ascii_letters))
 c.modelb.add(b)

 return ModelA.objects.filter(modelb__modelc=c)  # Will fail

 # But ModelA.objects.filter(modelb__modelc__pk=c.pk) works like a
 charm

 }}}

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

[django/django] c81b6f: Fixed #21702 -- Added different bullet styles for ...

2013-09-23 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c81b6f7b834da8d8fbcf679679ce158173df3a05
  
https://github.com/django/django/commit/c81b6f7b834da8d8fbcf679679ce158173df3a05
  Author: Tim Garner 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/_theme/djangodocs/static/djangodocs.css

  Log Message:
  ---
  Fixed #21702 -- Added different bullet styles for nested lists.

Thanks moc at mocpa.com 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/5240281272f86_2a865f7d5082113%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19941: Make running django's test suite easier

2013-09-23 Thread Django

Comment (by apollo13):

After discussing this a bit more with jezdez in IRC we came to the
following conclusion:
* `pip install -e .` isn't perfect (in the sense that it doesn't mimic a
sdist install by 100%) but still better than `sys.path` hacks.
* drop `sys.path` hacks again.
* Update the documentation to note `pip install -e` and `PYTHONPATH=..`
alternatives.
* Output something like `print("Testing against Django installed in '%s'"
% django.__file__)` to the console, to allow easier debugging.

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

Re: [Django] #19941: Make running django's test suite easier

2013-09-23 Thread Django

#19941: Make running django's test suite easier
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by apollo13):

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

[django/django] 6e6d1b: [1.6.x] Fixed #21702 -- Added different bullet sty...

2013-09-23 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 6e6d1b1ba8cfc78a3f3c14a67f5d59462364dc06
  
https://github.com/django/django/commit/6e6d1b1ba8cfc78a3f3c14a67f5d59462364dc06
  Author: Tim Garner 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/_theme/djangodocs/static/djangodocs.css

  Log Message:
  ---
  [1.6.x] Fixed #21702 -- Added different bullet styles for nested lists.

Thanks moc at mocpa.com for the suggestion.

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

[django/django] 938d98: [1.5.x] Fixed #21702 -- Added different bullet sty...

2013-09-23 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 938d98c8d18a6cba61b54ce0f9cc3af9e7afa134
  
https://github.com/django/django/commit/938d98c8d18a6cba61b54ce0f9cc3af9e7afa134
  Author: Tim Garner 
  Date:   2013-09-23 (Mon, 23 Sep 2013)

  Changed paths:
M docs/_theme/djangodocs/static/djangodocs.css

  Log Message:
  ---
  [1.5.x] Fixed #21702 -- Added different bullet styles for nested lists.

Thanks moc at mocpa.com for the suggestion.

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

Re: [Django] #20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"

2013-09-23 Thread Django

#20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"
-+-
 Reporter:  glarrain |Owner:  dchetwynd
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  six, python3,| Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by timo):

 Yes, I agree to keep the links are they are and add clarification if
 needed.

 I also confirm that the linking issue is fixed with Sphinx 1.2b2 which
 docs.djangoproject.com is now using.

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

Re: [Django] #19649: Cookie message storage does not set Vary: Cookie

2013-09-23 Thread Django

#19649: Cookie message storage does not set Vary: Cookie
---+-
 Reporter:  carljm |Owner:  bigkevmcd
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  1.4
 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 bigkevmcd):

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


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

Re: [Django] #19941: Make running django's test suite easier

2013-09-23 Thread Django

#19941: Make running django's test suite easier
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jezdez):

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


Comment:

 Reopening the sys.path.insert call makes the test setup differ from
 standard installation procedures. We've for a long time tried hard to move
 away from modifying the sys.path.

 As a background, by mangling the sys.path we risk missing import errors
 that happen when Django is installed with tools like pip. Instead we
 should promote the use of ``pip install -e path/to/django`` when
 developing Django.

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

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

Re: [Django] #20910: Specify the filename (when appropriate) with code snippets

2013-09-23 Thread Django

#20910: Specify the filename (when appropriate) with code snippets
-+-
 Reporter:  jggramlich@… |Owner:  nsmgr8
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  tutorial, afraid-|  Needs documentation:  0
  to-commit  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by nsmgr8):

 * owner:  anonymous => nsmgr8


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

Re: [Django] #20910: Specify the filename (when appropriate) with code snippets

2013-09-23 Thread Django

#20910: Specify the filename (when appropriate) with code snippets
-+-
 Reporter:  jggramlich@… |Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  tutorial, afraid-|  Needs documentation:  0
  to-commit  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by anonymous):

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


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

Re: [Django] #5793: Allow custom attributes in Meta classes

2013-09-23 Thread Django

#5793: Allow custom attributes in Meta classes
-+
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Metasystem   |  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 shai):

 On the list, Tim Chase gave this example:
 {{{
 class MyModel(Model):
   class Meta:
 ...
 class MyApp:
   secure_fields = ["cc_num", "ssn"]
 }}}
 The idea was that app-specific properties should be namespaced to avoid
 clashes. I think the approach is fine, I just don't see why these classes
 need to be in Meta; I see nothing wrong with

 {{{
 class MyModel(Model):
   class Meta:
 ...
   class MyApp:
 secure_fields = ["cc_num", "ssn"]
 }}}

 This leaves the app-specific metadata separate from fields and methods, so
 the "API" is clean enough; it avoids clashes reasonably well; and it
 requires no changes in Django.

 Note that this was the approach taken by Admin at first -- and my
 impression (though I wasn't "there" at the time) is that it changed
 because Admin classes became too large for comfort as nested classes, not
 because the first idea was considered so bad.

 I think for most use-cases -- in particular, including the two noted on
 the list, marking fields as "to be published" or "to be censored", this
 can work well.

 The point about extending the ORM stands, but this does not seem to be the
 use-case that motivates the current requests.

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

Re: [Django] #14028: setting db_column to same value as another column should not validate

2013-09-23 Thread Django

#14028: setting db_column to same value as another column should not validate
-+-
 Reporter:  akaariai |Owner:  helenst
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  validation,  |  Needs documentation:  0
  sprintdec2010  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by helenst):

 Consensus on #django-dev was that this should be a valid model.

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

Re: [Django] #20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"

2013-09-23 Thread Django

#20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"
-+-
 Reporter:  glarrain |Owner:  dchetwynd
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  six, python3,| Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by EvilDMP):

 I don't think it's necessarily incorrect to link to the Python version of
 the docs, but it is certainly confusing to link to them with link text
 that suggests we're speaking of Django docs. So I think it's worth noting
 that documentation for (nearly all you need to know about) Django's
 version (rather than 'copy') of six can in fact be found in the Python
 documentation. More clarification rather than correction perhaps.

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

Re: [Django] #20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"

2013-09-23 Thread Django

Comment (by dchetwynd):

In relation to the second issue on links to the six module, there are
inconsistencies between links to the Python version of six and links to
the Django version of six. In the /topics/python3.html documentation page
are seven links to the six module. Four of these links are correct, but
the following three links are to the Python version of six, instead of the
Django version:

1) The "six" link in the third sentence of the "Writing compatible code
with six" section
2) The "django.utils.six" link in the fourth sentence of the "Writing
compatible code with six" section
3) The "six" link in the final sentence of the "PY2" section

I will therefore change these three links to the correct targets.

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

Re: [Django] #21120: documentation talks about validators but separates definition and usage

2013-09-23 Thread Django

#21120: documentation talks about validators but separates definition and usage
-+-
 Reporter:  nicolas@…|Owner:
 Type:   |  benhuckvale
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:  afraid-to-commit |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by benhuckvale):

 * owner:  nobody => benhuckvale
 * 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/081.8c36f4f9f8c9f0f9743a511c8260e233%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20364: urlize incorrectly includes quotation marks in links

2013-09-23 Thread Django

#20364: urlize incorrectly includes quotation marks in links
-+-
 Reporter:  EmilStenstrom|Owner:  anonymous
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  urlize, quotes   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by GilesGreenway):

 aaugustin's example is in fact passed with flying colours after applying
 the patch:

 {{{
 >>> urlize('Email us at "h...@example.com", or phone us at +xx.yy')
 u'Email us at "mailto:h...@example.com;>h...@example.com", or
 phone us at +xx.yy'
 >>>
 >>> urlize('Visit us at "http://www.example.com;, or phone us at +xx.yy')
 u'Visit us at "http://www.example.com;>http://www.example.com", or phone us at
 +xx.yy'
 }}}

 I'll see if I can get a test written. (I'm a newbie contributor at the
 PyConUK Django sprint.)

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

Re: [Django] #21072: Square Bullets

2013-09-23 Thread Django

#21072: Square Bullets
-+-
 Reporter:  moc@…|Owner:  amney
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:  bullet indentation,  | Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by amney):

 I have submitted two pull requests to the main django and the
 djangoproject.com repositories to fix this issue.

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

 https://github.com/django/djangoproject.com/pull/58

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

Re: [Django] #14028: setting db_column to same value as another column should not validate

2013-09-23 Thread Django

#14028: setting db_column to same value as another column should not validate
-+-
 Reporter:  akaariai |Owner:  helenst
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  validation,  |  Needs documentation:  0
  sprintdec2010  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by helenst):

 Should it be valid to do something like this?

 {{{
 class FooBar(models.Model):
 foo = models.IntegerField(db_column='bar')
 bar = models.IntegerField(db_column='foo')
 class Meta:
 db_table = 'foobar'
 }}}

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

Re: [Django] #21140: Perfomance documentation should mention cached sessions

2013-09-23 Thread Django

#21140: Perfomance documentation should mention cached sessions
--+--
 Reporter:  EvilDMP   |Owner:  forslund
 Type:  Uncategorized |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by forslund):

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


Comment:

 Giving this a go during the pyConUK django sprint.

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

Re: [Django] #20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"

2013-09-23 Thread Django

#20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"
-+-
 Reporter:  glarrain |Owner:  dchetwynd
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  six, python3,| Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by dchetwynd):

 I've just rendered this page myself with Sphinx using Firefox 23.0.1 and
 Sphinx version 1.2b2 on Fedora 19. The link in question does render
 correctly in my browser as http://pythonhosted.org/six/index.html#module-
 six.moves, so the "module-" prefix of the link anchor is not omitted,
 unlike on EvilDMP's system. This may therefore only be an issue with some
 versions of Sphinx.

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

Re: [Django] #14028: setting db_column to same value as another column should not validate

2013-09-23 Thread Django

#14028: setting db_column to same value as another column should not validate
-+-
 Reporter:  akaariai |Owner:  helenst
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  validation,  |  Needs documentation:  0
  sprintdec2010  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by helenst):

 * owner:  tttallis => helenst
 * status:  new => assigned


Comment:

 Working on this at the PyConUK Django sprint

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

Re: [Django] #21070: Clarify document DATABASES change

2013-09-23 Thread Django

#21070: Clarify document DATABASES change
--+
 Reporter:  joejasinski   |Owner:  LouisF
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by LouisF):

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


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

Re: [Django] #20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"

2013-09-23 Thread Django

#20830: Bad URL for six.moves in "Porting to Python 3 / Moved modules"
-+-
 Reporter:  glarrain |Owner:  dchetwynd
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  six, python3,| Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by dchetwynd):

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


Comment:

 I am fixing this bug as part of the Django development sprint at PyCon UK
 2013.

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

Re: [Django] #4492: Provide tests for mixed-case column names

2013-09-23 Thread Django

Comment (by velis):

I just want to clarify: it says tests are needed, but the appropriate
checkbox is not ticked. So, is it the tests that are needed or is there
something more to this ticket?
p.s.: I'm sprinting django on PyCon UK and I'm looking at this ticket
because I have dealt with this problem before. So I know what the issue
was, I can write the appropriate tests, but I also want to make it right
so that my first contribution wouldn't end up a failure :)

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

Re: [Django] #21111: generic.View.init should call super

2013-09-23 Thread Django

#2: generic.View.__init__ should call super
--+
 Reporter:  glin@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Generic views |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | 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):

 IMO it's good practice to add it.

 Breaking the `__init__` chain tend to bite you when you least expect it,
 #20619 was an example of that.

 As I already mentioned on IRC, the base implementation of
 `get_context_data()` was specifically added in #16074 to play the role of
 `object.__init__()`, which is, always being there so subclasses can just
 call `super` without thinking about the `__mro__`.

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

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

Re: [Django] #21072: Square Bullets

2013-09-23 Thread Django

#21072: Square Bullets
-+-
 Reporter:  moc@…|Owner:  amney
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:  bullet indentation,  | Triage Stage:  Accepted
  afraid-to-commit   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by amney):

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


Comment:

 I will modify the CSS to support more indentation styles

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

Re: [Django] #12405: django.contrib.auth.views.logout() should support LOGOUT_REDIRECT_URL

2013-09-23 Thread Django

#12405: django.contrib.auth.views.logout() should support LOGOUT_REDIRECT_URL
-+-
 Reporter:  cmwslw   |Owner:  bigkevmcd
 Type:  New feature  |   Status:  assigned
Component:  contrib.auth |  Version:  1.1
 Severity:  Normal   |   Resolution:
 Keywords:  logout   | Triage Stage:  Accepted
  LOGOUT_REDIRECT_URL|  Needs documentation:  1
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bigkevmcd):

 * owner:  dloewenherz => bigkevmcd


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

Re: [Django] #21111: generic.View.init should call super

2013-09-23 Thread Django

#2: generic.View.__init__ should call super
--+
 Reporter:  glin@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Generic views |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by tomchristie):

 This seems like a bit of an anti-pattern to me.
 If more than one intermediate class is defining `__init__()` then it's up
 to the superclass to properly determine the behaviour.
 We don't call into `super` in the base class implementations of, say
 `get_context_data()` it's not at all clear to me that it's ether a
 necessary or a good thing to do in `__init__()`.

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

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

Re: [Django] #21134: Documentation for transaction.atomic needs more explicit warning about catching DatabaseErrors

2013-09-23 Thread Django

#21134: Documentation for transaction.atomic needs more explicit warning about
catching DatabaseErrors
-+-
 Reporter:  RichardOfWard|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-beta-1
 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 aaugustin):

 * status:  new => assigned
 * needs_better_patch:  0 => 1


Comment:

 This patch breaks two tests under PostgreSQL when running the full test
 suite — not in isolation:
 {{{
 ==
 ERROR: test_alter_unique_together
 (migrations.test_operations.OperationTests)
 --
 Traceback (most recent call last):
   File
 "/Users/myk/Documents/dev/django/tests/migrations/test_operations.py",
 line 256, in test_alter_unique_together
 operation.database_backwards("test_alunto", editor, new_state,
 project_state)
   File
 "/Users/myk/Documents/dev/django/django/db/migrations/operations/models.py",
 line 121, in database_backwards
 return self.database_forwards(app_label, schema_editor, from_state,
 to_state)
   File
 "/Users/myk/Documents/dev/django/django/db/migrations/operations/models.py",
 line 117, in database_forwards
 getattr(new_model._meta, "unique_together", set()),
   File "/Users/myk/Documents/dev/django/django/db/backends/schema.py",
 line 271, in alter_unique_together
 ", ".join(columns),
 ValueError: Found wrong number (0) of constraints for
 test_alunto_pony(pink, weight)

 ==
 ERROR: test_unique_together (schema.tests.SchemaTests)
 --
 Traceback (most recent call last):
   File "/Users/myk/Documents/dev/django/tests/schema/tests.py", line 430,
 in test_unique_together
 [],
   File "/Users/myk/Documents/dev/django/django/db/backends/schema.py",
 line 271, in alter_unique_together
 ", ".join(columns),
 ValueError: Found wrong number (0) of constraints for
 schema_uniquetest(year, slug)

 --
 }}}

 It also breaks one test on MySQL, because it's the only database that
 can't defer constraints checks automatically:
 {{{
 ==
 ERROR: test_loaddata_error_message (fixtures.tests.FixtureLoadingTests)
 --
 Traceback (most recent call last):
   File "/Users/myk/Documents/dev/django/tests/fixtures/tests.py", line
 324, in test_loaddata_error_message
 management.call_command('loaddata', 'invalid.json', verbosity=0)
   File
 "/Users/myk/Documents/dev/django/django/core/management/__init__.py", line
 159, in call_command
 return klass.execute(*args, **defaults)
   File "/Users/myk/Documents/dev/django/django/core/management/base.py",
 line 289, in execute
 output = self.handle(*args, **options)
   File
 "/Users/myk/Documents/dev/django/django/core/management/commands/loaddata.py",
 line 55, in handle
 self.loaddata(fixture_labels)
   File
 "/Users/myk/Documents/dev/django/django/core/management/commands/loaddata.py",
 line 84, in loaddata
 self.load_label(fixture_label)
   File
 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/contextlib.py",
 line 35, in __exit__
 self.gen.throw(type, value, traceback)
   File "/Users/myk/Documents/dev/django/django/db/backends/__init__.py",
 line 417, in constraint_checks_disabled
 self.enable_constraint_checking()
   File "/Users/myk/Documents/dev/django/django/db/backends/mysql/base.py",
 line 490, in enable_constraint_checking
 self.cursor().execute('SET foreign_key_checks=1')
   File "/Users/myk/Documents/dev/django/django/db/backends/utils.py", line
 47, in execute
 self.db.validate_no_broken_transaction()
   File "/Users/myk/Documents/dev/django/django/db/backends/__init__.py",
 line 367, in validate_no_broken_transaction
 "An error occurred in the current transaction. You can't "
 TransactionManagementError: An error occurred in the current transaction.
 You can't execute queries until the end of the 'atomic' block.

 --
 }}}

 Under Oracle it appears to be fine (I'm not getting a clean

97 matches

Mail list logo