[Django] #21096: Allow setting of 'distance' attribute name

[Django]

#21096: Allow setting of 'distance' attribute name
---+
 Reporter:  simon29|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  GIS|Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  0
---+
 In a
 
[https://docs.djangoproject.com/en/dev/ref/contrib/gis/geoquerysets/#django.contrib.gis.db.models.GeoQuerySet.distance
 distance query], the attribute name is currently hardcoded at 'distance',
 which prevents the use of multiple distance measurements (used in routing
 etc).

 Patch attached that accepts the name as an optional arg.

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

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

[Django] #21095: Release notes and documentation don't mention queryset week_day breakage on mysql if you haven't loaded tzinfo

[Django]

#21095: Release notes and documentation don't mention queryset week_day 
breakage on
mysql if you haven't loaded tzinfo
---+--
 Reporter:  mattaustin |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.6-beta-1
 Severity:  Normal |   Keywords:  releasenotes
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+--
 When switching to Django 1.6b2, queries such as
 {{{MyModel.objects.filter(start_at__week_day=1)}}} started returning empty
 querysets. After investigation, it turned out I had to load tzinfo in to
 the database, as described at
 https://docs.djangoproject.com/en/1.6/ref/models/querysets/#database-time-
 zone-definitions. Although the release notes mention this is required for
 the new QuerySet.datetimes() functionality, there was nothing mentioning
 it was required for using week_day lookups.

 As this could break previously working projects with Django 1.5, it should
 probably be made clear in the release notes and queryset documentation.

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

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

[Django] #21094: Simplify tutorial steps in "using your own package"

[Django]

#21094: Simplify tutorial steps in "using your own package"
--+--
 Reporter:  ylb415@…  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.5
 Severity:  Normal|   Keywords:  tutorial
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 Hello,

 Just a suggestion.

 https://docs.djangoproject.com/en/1.5/intro/reusable-apps/
 Step 1, 2 and 3 in "Using your own package"

 I was wondering if 'python setup.py install --user' could be replaced by
 'pip install --user django-polls-0.1.tar.gz'.

 it simplify the tutorial as it is not needed to untar (except if one of
 the goal of the exercise is to expose to the user what is inside the tar
 file).

 Thank you,

 Yves

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

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

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

[Django]

#21093: regressiontests.mail.tests.MailTests.test_dont_base64_encode() fails 
with
Python >=3.3.3
---+
 Reporter:  Arfrever   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Testing framework  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 regressiontests.mail.tests.MailTests.test_dont_base64_encode() fails with
 Python >=3.3.3 since [http://hg.python.org/cpython/rev/64e004737837 Python
 commit 64e004737837].
 It passes with older versions of Python.
 I use Django 1.5.3.

 {{{
 $ PYTHONPATH="." python3.3 tests/runtests.py --settings=test_sqlite -v0
 mail.MailTests.test_dont_base64_encode
 ==
 FAIL: test_dont_base64_encode (regressiontests.mail.tests.MailTests)
 --
 Traceback (most recent call last):
   File "/tmp/Django-1.5.3/tests/regressiontests/mail/tests.py", line 330,
 in test_dont_base64_encode
 self.assertTrue(str('Content-Transfer-Encoding: 8bit') in s)
 AssertionError: False is not True

 --
 Ran 1 test in 0.025s

 FAILED (failures=1)
 }}}

 Variable 's' contains 'Content-Transfer-Encoding: 8bit' with older
 versions of Python and 'Content-Transfer-Encoding: 7bit' with Python
 >=3.3.3.

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

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

[django/django] e8bb41: [1.6.x] Minor typo fix in django.contrib.auth.mode...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: e8bb41d05ccd4ccb2cb983ad6c895ff40de622df
  
https://github.com/django/django/commit/e8bb41d05ccd4ccb2cb983ad6c895ff40de622df
  Author: Phaneendra Chiruvella 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M docs/ref/contrib/auth.txt

  Log Message:
  ---
  [1.6.x] Minor typo fix in django.contrib.auth.models.User docs

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

[django/django] bd72c2: Minor typo fix in django.contrib.auth.models.User ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bd72c2acb60a7adeb0334a823063d6eab9206081
  
https://github.com/django/django/commit/bd72c2acb60a7adeb0334a823063d6eab9206081
  Author: Phaneendra Chiruvella 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M docs/ref/contrib/auth.txt

  Log Message:
  ---
  Minor typo fix in django.contrib.auth.models.User docs


  Commit: 37faf12e66a74642d73639569225c95e400bbae2
  
https://github.com/django/django/commit/37faf12e66a74642d73639569225c95e400bbae2
  Author: Simon Charette 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M docs/ref/contrib/auth.txt

  Log Message:
  ---
  Merge pull request #1618 from pcx/minor_typo_fix

Minor typo fix in django.contrib.auth.models.User docs


Compare: https://github.com/django/django/compare/e61cc8712972...37faf12e66a7

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

Re: [Django] #11320: Over aggressive join promotion with exclude()

[Django]

#11320: Over aggressive join promotion with exclude()
-+-
 Reporter:  Alex |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by timo):

 Confirmed this is still an issue on master.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.eb98d093cba23c43e830928ac15b4780%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

[Django]

#14028: setting db_column to same value as another column should not validate
-+-
 Reporter:  akaariai |Owner:  tttallis
 Type:  Bug  |   Status:  new
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 timo):

 * easy:  0 => 1


Comment:

 Seems like this would be a fairly easy addition to
 django/core/management/validation.py with a test in
 django/tests/invalid_models/tests.py.

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

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

[Django] #21092: regressiontests.test_runner.tests.DeprecationDisplayTest.test_runner_deprecation_verbosity_zero() fails with enabled warnings

[Django]

#21092: 
regressiontests.test_runner.tests.DeprecationDisplayTest.test_runner_deprecation_verbosity_zero()
fails with enabled warnings
---+
 Reporter:  Arfrever   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Testing framework  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 When warnings are enabled (using PYTHONWARNINGS="d" environmental
 variable), then
 
regressiontests.test_runner.tests.DeprecationDisplayTest.test_runner_deprecation_verbosity_zero()
 fails.
 I use Django 1.5.3.

 {{{
 $ PYTHONPATH="." python3.3 tests/runtests.py --settings=test_sqlite -v0
 test_runner.DeprecationDisplayTest.test_runner_deprecation_verbosity_zero
 --
 Ran 1 test in 1.086s

 OK
 $ PYTHONPATH="." PYTHONWARNINGS="d" python3.3 tests/runtests.py
 --settings=test_sqlite -v0
 test_runner.DeprecationDisplayTest.test_runner_deprecation_verbosity_zero
 ==
 FAIL: test_runner_deprecation_verbosity_zero
 (regressiontests.test_runner.tests.DeprecationDisplayTest)
 --
 Traceback (most recent call last):
   File "/tmp/Django-1.5.3/tests/regressiontests/test_runner/tests.py",
 line 368, in test_runner_deprecation_verbosity_zero
 self.assertFalse("DeprecationWarning: warning from test" in err)
 AssertionError: True is not False

 --
 Ran 1 test in 1.060s

 FAILED (failures=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/051.69d32577cf97296e85785c96d63846f0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

[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|
-+-
Changes (by timo):

 * easy:  0 => 1


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

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

Re: [Django] #19750: Postgres conflict on CREATE INDEX: "relation exists"

[Django]

#19750: Postgres conflict on CREATE INDEX: "relation exists"
-+-
 Reporter:  pricco@… |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.5-beta-1
 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
-+-

Comment (by timo):

 I can reproduce this using 1.6 and Postgres. `syncdb` with the above
 models gives the error `Failed to install index for polls.Organization
 model: relation "organization_type_id_like" already exists`. The patch
 still lacks tests, however.

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

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

Re: [Django] #21091: Specify where TEMPLATE_DIRS should be added in settings.py

[Django]

#21091: Specify where TEMPLATE_DIRS should be added in settings.py
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.5
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 I'm sorry, but I think you're confused. The order in which settings are
 declared doesn't matter.

 The StackOverflow question you link to doesn't discuss the order of
 TEMPLATE_DIRS and INSTALLED_APPS.

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

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

[django/django] e61cc8: Fixed #21090 -- Allowed backends to provide dotted...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e61cc87129727c66120b67c376feda3533544db1
  
https://github.com/django/django/commit/e61cc87129727c66120b67c376feda3533544db1
  Author: Michael Manfre 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M django/core/management/commands/inspectdb.py
M tests/inspectdb/tests.py

  Log Message:
  ---
  Fixed #21090 -- Allowed backends to provide dotted field path to inspectdb.



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

[Django] #21091: Specify where TEMPLATE_DIRS should be added in settings.py

[Django]

#21091: Specify where TEMPLATE_DIRS should be added in settings.py
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 If the code

 TEMPLATE_DIRS = (
 '/path/to/mysite/templates', # Change this to your own directory.
 )

 is added before INSTALLED_APPS it does not work. This should be pointed
 out.

 Judging by the upvotes at the below link it is a fairly common oversight.
 http://stackoverflow.com/questions/11793890/custom-django-admin-templates-
 not-working

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

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

Re: [Django] #14497: ModelAdmin.readonly_fields isn't graceful with filefields.

[Django]

#14497: ModelAdmin.readonly_fields isn't graceful with filefields.
-+-
 Reporter:  Keryn Knight |Owner:
|  paulcollins
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  feature admin| Triage Stage:  Accepted
  readonly filefield |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-

Comment (by aaugustin):

 I marked this ticket as "accepted" when we removed "design decision
 needed"; it seemed more appropriate than closing it. But I haven't looked
 at 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/094.17422dcb6b39296180afaf1a2e2575dd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21090: inspectdb shouldn't include 'models.' prefix if field_type is a dotted path

[Django]

#21090: inspectdb shouldn't include 'models.' prefix if field_type is a dotted 
path
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  inspectdb|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e61cc87129727c66120b67c376feda3533544db1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e61cc87129727c66120b67c376feda3533544db1"
 Fixed #21090 -- Allowed backends to provide dotted field path to
 inspectdb.
 }}}

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

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

Re: [Django] #14497: ModelAdmin.readonly_fields isn't graceful with filefields.

[Django]

#14497: ModelAdmin.readonly_fields isn't graceful with filefields.
-+-
 Reporter:  Keryn Knight |Owner:
|  paulcollins
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  feature admin| Triage Stage:  Accepted
  readonly filefield |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-

Comment (by paulcollins):

 @aaugustin
 So I see you've marked this as accepted. I can dig back into this issue
 again and see if my horrible hack solution would even still apply here.
 Assuming it does is that the direction I should move this in?

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

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

[Django] #21090: inspectdb shouldn't include 'models.' prefix if field_type is a dotted path

[Django]

#21090: inspectdb shouldn't include 'models.' prefix if field_type is a dotted 
path
+---
 Reporter:  manfre  |  Owner:  nobody
 Type:  New feature | Status:  new
Component:  Core (Management commands)  |Version:  1.5
 Severity:  Normal  |   Keywords:  inspectdb
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  1   |  UI/UX:  0
+---
 To allow backends to better provide custom field types to inspectdb, it
 should not include the 'models.' prefix if the field_type contains a dot.

 This would allow for:
 {{{
 id = sqlserver_ado.fields.BigAutoField()
 }}}

 instead of:
 {{{
 id = models.sqlserver_ado.fields.BigAutoField()
 }}}

 This ticket intentionally does not address the lack of import for
 `sqlserver_ado.fields`

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

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

Re: [Django] #21060: Refactor admin's autodiscover method to make it reusable

[Django]

#21060: Refactor admin's autodiscover method to make it reusable
-+
 Reporter:  jcatalan |Owner:  jcatalan
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Left comments on PR.

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

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

Re: [Django] #21090: inspectdb shouldn't include 'models.' prefix if field_type is a dotted path

[Django]

#21090: inspectdb shouldn't include 'models.' prefix if field_type is a dotted 
path
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  inspectdb|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * version:  1.5 => master
 * easy:  1 => 0
 * needs_tests:  0 => 1
 * stage:  Unreviewed => 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/064.1a46e73b91ec2d358fc0bfde91f7f26f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21090: inspectdb shouldn't include 'models.' prefix if field_type is a dotted path

[Django]

#21090: inspectdb shouldn't include 'models.' prefix if field_type is a dotted 
path
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.5
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  inspectdb|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by manfre):

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


Comment:

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

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

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

Re: [Django] #21089: TestCase can't define an empty list of fixtures

[Django]

#21089: TestCase can't define an empty list of fixtures
---+
 Reporter:  lgs|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:  fixed
 Keywords:  fixtures   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by lgs):

 Thanks for fixing this so fast :-)

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

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

[django/django] abb10d: Fixed #21089 -- Allow TransactionTestcase subclass...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: abb10db06fb2ecb3e897462ec72417d10b39b8a4
  
https://github.com/django/django/commit/abb10db06fb2ecb3e897462ec72417d10b39b8a4
  Author: Baptiste Mispelon 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M django/test/testcases.py
M tests/fixtures/tests.py

  Log Message:
  ---
  Fixed #21089 -- Allow TransactionTestcase subclasses to define an empty list 
of fixtures.

Thanks to lgs for the report and initial patch.



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

Re: [Django] #21089: TestCase can't define an empty list of fixtures

[Django]

#21089: TestCase can't define an empty list of fixtures
---+
 Reporter:  lgs|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:  fixed
 Keywords:  fixtures   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"abb10db06fb2ecb3e897462ec72417d10b39b8a4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="abb10db06fb2ecb3e897462ec72417d10b39b8a4"
 Fixed #21089 -- Allow TransactionTestcase subclasses to define an empty
 list of fixtures.

 Thanks to lgs for the report and initial patch.
 }}}

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

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

Re: [Django] #21056: AdminSite app_list may be reverse()'d into an invalid URL endpoint

[Django]

#21056: AdminSite app_list may be reverse()'d into an invalid URL endpoint
-+-
 Reporter:  Keryn Knight |Owner:  Tim
   |  Graham 
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

 * owner:   => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"170f72136758add6c9c0c59240cfce73d5672cc2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="170f72136758add6c9c0c59240cfce73d5672cc2"
 Fixed #21056 -- AdminSite.app_index no longer blindly accepts any app-
 labelish input.
 }}}

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

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

[django/django] 170f72: Fixed #21056 -- AdminSite.app_index no longer blin...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 170f72136758add6c9c0c59240cfce73d5672cc2
  
https://github.com/django/django/commit/170f72136758add6c9c0c59240cfce73d5672cc2
  Author: Keryn Knight 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M django/contrib/admin/sites.py
M tests/admin_views/tests.py

  Log Message:
  ---
  Fixed #21056 -- AdminSite.app_index no longer blindly accepts any 
app-labelish input.



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

Re: [Django] #21089: TestCase can't define an empty list of fixtures

[Django]

#21089: TestCase can't define an empty list of fixtures
---+
 Reporter:  lgs|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  fixtures   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by lgs):

 I don't know about the reasons behind getattr. That code was there before,
 I just added an extra check.

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

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

[django/django] 169594: [1.5.x] Fixed #20887 -- Added a warning to GzipMid...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 169594f5ae09782ab1909fc3a9939a23507b4901
  
https://github.com/django/django/commit/169594f5ae09782ab1909fc3a9939a23507b4901
  Author: Tim Graham 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M docs/ref/middleware.txt
M docs/topics/cache.txt

  Log Message:
  ---
  [1.5.x] Fixed #20887 -- Added a warning to GzipMiddleware in light of BREACH.

Thanks EvilDMP for the report and Russell Keith-Magee
for the draft text.

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

Re: [Django] #20887: Document GzipMiddleware security issues

[Django]

#20887: Document GzipMiddleware security issues
---+
 Reporter:  EvilDMP|Owner:  timo
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"169594f5ae09782ab1909fc3a9939a23507b4901"]:
 {{{
 #!CommitTicketReference repository=""
 revision="169594f5ae09782ab1909fc3a9939a23507b4901"
 [1.5.x] Fixed #20887 -- Added a warning to GzipMiddleware in light of
 BREACH.

 Thanks EvilDMP for the report and Russell Keith-Magee
 for the draft text.

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

Re: [Django] #20887: Document GzipMiddleware security issues

[Django]

#20887: Document GzipMiddleware security issues
---+
 Reporter:  EvilDMP|Owner:  timo
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"b05639dcacdd8b2c1dd6db447ce7f20caefc5f54"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b05639dcacdd8b2c1dd6db447ce7f20caefc5f54"
 [1.6.x] Fixed #20887 -- Added a warning to GzipMiddleware in light of
 BREACH.

 Thanks EvilDMP for the report and Russell Keith-Magee
 for the draft text.

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

[django/django] cca302: [1.4.x] Fixed #20887 -- Added a warning to GzipMid...

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: cca302cde6b524992d89add9b9f293d86ac8fba0
  
https://github.com/django/django/commit/cca302cde6b524992d89add9b9f293d86ac8fba0
  Author: Tim Graham 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M docs/ref/middleware.txt
M docs/topics/cache.txt

  Log Message:
  ---
  [1.4.x] Fixed #20887 -- Added a warning to GzipMiddleware in light of BREACH.

Thanks EvilDMP for the report and Russell Keith-Magee
for the draft text.

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

Re: [Django] #20887: Document GzipMiddleware security issues

[Django]

#20887: Document GzipMiddleware security issues
---+
 Reporter:  EvilDMP|Owner:  timo
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"cca302cde6b524992d89add9b9f293d86ac8fba0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cca302cde6b524992d89add9b9f293d86ac8fba0"
 [1.4.x] Fixed #20887 -- Added a warning to GzipMiddleware in light of
 BREACH.

 Thanks EvilDMP for the report and Russell Keith-Magee
 for the draft text.

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

[django/django] b05639: [1.6.x] Fixed #20887 -- Added a warning to GzipMid...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: b05639dcacdd8b2c1dd6db447ce7f20caefc5f54
  
https://github.com/django/django/commit/b05639dcacdd8b2c1dd6db447ce7f20caefc5f54
  Author: Tim Graham 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M docs/ref/middleware.txt
M docs/topics/cache.txt

  Log Message:
  ---
  [1.6.x] Fixed #20887 -- Added a warning to GzipMiddleware in light of BREACH.

Thanks EvilDMP for the report and Russell Keith-Magee
for the draft text.

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

Re: [Django] #20887: Document GzipMiddleware security issues

[Django]

#20887: Document GzipMiddleware security issues
---+
 Reporter:  EvilDMP|Owner:  timo
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"da843e7dba4ae8ed2846475564bb6ded82960827"]:
 {{{
 #!CommitTicketReference repository=""
 revision="da843e7dba4ae8ed2846475564bb6ded82960827"
 Fixed #20887 -- Added a warning to GzipMiddleware in light of BREACH.

 Thanks EvilDMP for the report and Russell Keith-Magee
 for the draft text.
 }}}

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

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

[django/django] da843e: Fixed #20887 -- Added a warning to GzipMiddleware ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: da843e7dba4ae8ed2846475564bb6ded82960827
  
https://github.com/django/django/commit/da843e7dba4ae8ed2846475564bb6ded82960827
  Author: Tim Graham 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M docs/ref/middleware.txt
M docs/topics/cache.txt

  Log Message:
  ---
  Fixed #20887 -- Added a warning to GzipMiddleware in light of BREACH.

Thanks EvilDMP for the report and Russell Keith-Magee
for the draft text.



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

Re: [Django] #21089: TestCase can't define an empty list of fixtures

[Django]

#21089: TestCase can't define an empty list of fixtures
---+
 Reporter:  lgs|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  fixtures   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by bmispelon):

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


Comment:

 This looks useful, but I have some questions about the patch.

 Is there a particular reason that we're using `getattr` instead of simply
 defining a `fixtures` attribute on `TransactionTestCase` (see attached
 diff)?

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

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

Re: [Django] #20887: Document GzipMiddleware security issues

[Django]

#20887: Document GzipMiddleware security issues
---+
 Reporter:  EvilDMP|Owner:  timo
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

 * owner:  nobody => timo
 * status:  new => assigned
 * version:  1.5 => 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/065.04062df2e7078e3e52aae27fb487924c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21089: TestCase can't define an empty list of fixtures

[Django]

#21089: TestCase can't define an empty list of fixtures
---+--
 Reporter:  lgs|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  fixtures   | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by lgs):

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

[django/django] 4f0ea1: [1.6.x] Documentation -- Improved description of c...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 4f0ea1aca4fce75de22878839f077fa1c1d9e21a
  
https://github.com/django/django/commit/4f0ea1aca4fce75de22878839f077fa1c1d9e21a
  Author: Kevin Christopher Henry 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M docs/topics/cache.txt

  Log Message:
  ---
  [1.6.x] Documentation -- Improved description of cache arguments

- Fixed some grammar and formatting mistakes
- Added the type and default for CULL_FREQUENCY
- Made the note on culling the entire cache more precise. (It's actually
  slower on the filesystem backend.)

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

[django/django] 2a7d30: [1.5.x] Documentation -- Improved description of c...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 2a7d3030f9703464fb56e29dbe764eb1b2c88359
  
https://github.com/django/django/commit/2a7d3030f9703464fb56e29dbe764eb1b2c88359
  Author: Kevin Christopher Henry 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M docs/topics/cache.txt

  Log Message:
  ---
  [1.5.x] Documentation -- Improved description of cache arguments

- Fixed some grammar and formatting mistakes
- Added the type and default for CULL_FREQUENCY
- Made the note on culling the entire cache more precise. (It's actually
  slower on the filesystem backend.)

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

[django/django] 5eca02: Documentation -- Improved description of cache arg...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5eca021d48cc388d89347d01cb7bfafc9fcfa331
  
https://github.com/django/django/commit/5eca021d48cc388d89347d01cb7bfafc9fcfa331
  Author: Kevin Christopher Henry 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M docs/topics/cache.txt

  Log Message:
  ---
  Documentation -- Improved description of cache arguments

- Fixed some grammar and formatting mistakes
- Added the type and default for CULL_FREQUENCY
- Made the note on culling the entire cache more precise. (It's actually
  slower on the filesystem backend.)



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

Re: [Django] #21089: TestCase can't define an empty list of fixtures

[Django]

#21089: TestCase can't define an empty list of fixtures
---+--
 Reporter:  lgs|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  fixtures   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by lgs):

 No, it is not solved by setting fixtures = None

 The Github branch with the testcase to reproduce this error and the fix is
 located at: https://github.com/lorenzogil/django/compare/ticket_21089

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

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

Re: [Django] #21089: TestCase can't define an empty list of fixtures

[Django]

#21089: TestCase can't define an empty list of fixtures
---+--
 Reporter:  lgs|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  fixtures   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by mjtamlyn):

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


Comment:

 Is this problem solved by setting `fixtures = 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/061.9ec9d5aec14bbf2e18dcb5518bd80cbd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 3203f6: Fixed failing test introduced by 87d2750b39.

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 3203f684e8e51cbfa1b39d7b6a56e340981ad4d5
  
https://github.com/django/django/commit/3203f684e8e51cbfa1b39d7b6a56e340981ad4d5
  Author: Loic Bistuer 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M tests/regressiontests/templates/tests.py

  Log Message:
  ---
  Fixed failing test introduced by 87d2750b39.

The {% ssi %} tag in Django 1.4 doesn't support spaces in its argument.
Skip the test if run from a location that contains a space.


  Commit: 434d122a74647c647f906aaabe235ae62601682d
  
https://github.com/django/django/commit/434d122a74647c647f906aaabe235ae62601682d
  Author: Florian Apolloner 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M tests/regressiontests/templates/tests.py

  Log Message:
  ---
  Merge pull request #1616 from loic/fix1.4

Fixed failing test introduced by 87d2750b39.


Compare: https://github.com/django/django/compare/fba6af5a1ed5...434d122a7464

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

[Django] #21089: TestCase can't define an empty list of fixtures

[Django]

#21089: TestCase can't define an empty list of fixtures
---+--
 Reporter:  lgs|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  1.5
 Severity:  Normal |   Keywords:  fixtures
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 This could be useful if you have a TestCase base class that define some
 very basic fixtures that are used across all your tests but then, there is
 a few particular tests that do not want such fixtures.

 Let's say you have something like:

 {{{
 class BaseTestCase(TestCase):

   fixtures = ['basic_data.json']


 class NoFixturesTestCase(BaseTestCase):

   fixtures = []
 }}}

 If you do this you will get this error:

 {{{
 Traceback (most recent call last):
   File "/home/lgs/proyectos/personal/django/django/test/testcases.py",
 line 173, in __call__
 self._pre_setup()
   File "/home/lgs/proyectos/personal/django/django/test/testcases.py",
 line 716, in _pre_setup
 self._fixture_setup()
   File "/home/lgs/proyectos/personal/django/django/test/testcases.py",
 line 848, in _fixture_setup
 'skip_validation': True,
   File
 "/home/lgs/proyectos/personal/django/django/core/management/__init__.py",
 line 159, in call_command
 return klass.execute(*args, **defaults)
   File
 "/home/lgs/proyectos/personal/django/django/core/management/base.py", line
 289, in execute
 output = self.handle(*args, **options)
   File
 
"/home/lgs/proyectos/personal/django/django/core/management/commands/loaddata.py",
 line 49, in handle
 "No database fixture specified. Please provide the path "
 CommandError: No database fixture specified. Please provide the path of at
 least one fixture in the command line.
 }}}

 You can use this hack as a workaround:


 {{{
 class NoFixturesTestCase(BaseTestCase):

   fixtures = ['non-existing-file.json']
 }}}

 And now you will get a warning instead of an error.

 I'll create a Github branch with a test showing this behaviour and a fix
 for it.

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

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

[django/django] 91a073: [1.5.x] Bump version post-release.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 91a073a337ddcd9a4efa7a5828b01e1efc28988f
  
https://github.com/django/django/commit/91a073a337ddcd9a4efa7a5828b01e1efc28988f
  Author: Tim Graham 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  [1.5.x] Bump version post-release.



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

[django/django] fba6af: [1.4.x] Bump version post-release.

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: fba6af5a1ed5924f400666f6747e706a20cceadc
  
https://github.com/django/django/commit/fba6af5a1ed5924f400666f6747e706a20cceadc
  Author: Tim Graham 
  Date:   2013-09-11 (Wed, 11 Sep 2013)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  [1.4.x] Bump version post-release.



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

Re: [Django] #21087: "datatime" objects can not be JSON-serialized to be held in sessions

[Django]

#21087: "datatime" objects can not be JSON-serialized to be held in sessions
-+-
 Reporter:  epandurski@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core |  Version:  master
  (Serialization)|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 This was discussed quite a bit during the implementation, and the caveats
 of JSON serialization have been documented:

 https://docs.djangoproject.com/en/dev/releases/1.6/#default-session-
 serialization-switched-to-json

 https://docs.djangoproject.com/en/dev/topics/http/sessions/#session-
 serialization

 You can continue to use the `PickleSerializer` if needed.

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

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

Re: [Django] #21087: "datatime" objects can not be JSON-serialized to be held in sessions

[Django]

#21087: "datatime" objects can not be JSON-serialized to be held in sessions
-+-
 Reporter:  epandurski@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core |  Version:  master
  (Serialization)|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * resolution:  fixed => wontfix


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

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

Re: [Django] #16284: djangojs uses en as fallback language rather than projects language code

[Django]

#16284: djangojs uses en as fallback language rather than projects language code
--+
 Reporter:  anonymous |Owner:  KJ
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by ramiro):

 Replying to [comment:8 KJ]:
 > Replying to [comment:7 ramiro]:
 > > Replying to [comment:6 KJ]:
 > > > 1. Loading of English translation. As there is a priori no reason to
 treat English differently than other languages, this is a no-brainer.
 > >
 > > We can discuss about this. I think it might be possible to give no
 special treatment to English in JS i18n because it's not tied to the GNU
 gettext runtime translation machinery (through the Python gettext stdlib
 module) that is the one known to have some en-us preference hardcoded
 behavior.
 >
 > I didn’t know about that. I have done some googling and grepping in
 gettext’s source code for that en-us-centric behavior and found nothing,
 which may mean that it is not a feature that gettext is very proud of.

 I'll need to search for this myself too. I rememeber reading about it...
 And here it is, it was in this same issue tracker: #8626

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

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

Re: [Django] #10098: LazySettings.get function with default value

[Django]

#10098: LazySettings.get function with default value
---+--
 Reporter:  fero   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by anonymous):

 * ui_ux:   => 0


Comment:

 dsdsdfd

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

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

Re: [Django] #21088: Misleading doc for overriding model save method.

[Django]

#21088: Misleading doc for overriding model save method.
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  model,   |  Unreviewed
  documentation  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by akaariai):

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


Comment:

 It doesn't need to do that. The Model.save() doesn't return anything.

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

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

[Django] #21088: Misleading doc for overriding model save method.

[Django]

#21088: Misleading doc for overriding model save method.
--+--
 Reporter:  anonymous |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.5
 Severity:  Normal|   Keywords:  model, documentation
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+--
 Documentation does not make it clear than overriding a model's save method
 should return the model object.

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

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

Re: [Django] #21087: "datatime" objects can not be JSON-serialized to be held in sessions

[Django]

#21087: "datatime" objects can not be JSON-serialized to be held in sessions
-+-
 Reporter:  epandurski@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core |  Version:  master
  (Serialization)|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 The JSON format doesn't provide a type for dates/datetimes. We'll have to
 resort to a hack to support this use case.

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

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

[Django] #21087: "datatime" objects can not be JSON-serialized to be held in sessions

[Django]

#21087: "datatime" objects can not be JSON-serialized to be held in sessions
--+
 Reporter:  epandurski@…  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Serialization)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I am using Django 1.6 beta 3.

 In my view I try:
 {{{
 now = datetime.datetime.now(pytz.utc)
 request.session['lstts'] = now
 }}}
 But I get the following error: http://dpaste.com/hold/1375033/

 I presume the reason is the new serializer for session objects. I also
 presume that "datatime" objects must be supported, because they are quite
 useful and used.

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

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

Re: [Django] #16284: djangojs uses en as fallback language rather than projects language code

[Django]

#16284: djangojs uses en as fallback language rather than projects language code
--+
 Reporter:  anonymous |Owner:  KJ
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by KJ):

 * needs_better_patch:  0 => 1


Comment:

 Replying to [comment:7 ramiro]:
 > Replying to [comment:6 KJ]:
 > > 1. Loading of English translation. As there is a priori no reason to
 treat English differently than other languages, this is a no-brainer.
 >
 > We can discuss about this. I think it might be possible to give no
 special treatment to English in JS i18n because it's not tied to the GNU
 gettext runtime translation machinery (through the Python gettext stdlib
 module) that is the one known to have some en-us preference hardcoded
 behavior.

 I didn’t know about that. I have done some googling and grepping in
 gettext’s source code for that en-us-centric behavior and found nothing,
 which may mean that it is not a feature that gettext is very proud of.

 > Replying to [comment:6 KJ]:
 > > 2. Loading of language specified in LANGUAGE_CODE setting. This has to
 be done because there is no way to determine what language we’re
 translating from. For example, if we have source texts written in Polish
 and LANGUAGE_CODE is set to “es”, we want to get no translations for users
 with language set to “pl”. If Spanish translation was present, this would
 be impossible with current solution.
 >
 > Well, that would change the behavior. By definition LANGUAGE_CODE is the
 language to which runtime translation fallbacks when no translation is
 available for a given literal in the user-preferred language. Also, it's
 the way to dictate which global translation to use when no per-user
 preference language detection mechanism is in effect (localmiddleware). As
 you've well described this LANGUAGE_CODE can be different from the
 language of the Python/JS source code files/templates.
 >
 > We need to find a way to cover your use case (fallback to source code
 language without taking in account LANGUAGE_CODE) but without breaking
 existing use and deployments.

 One way would be to provide more flexible way of specifying language
 preference (like a setting which points to a function which returns an
 iterable of language codes, in order of preference). However this would
 still leave some potential holes, for example if:

 - App A is written in English and translated into Polish.
 - App B is written in Polish and translated into English.

 , then I see no way to make a satisfactory global language preference
 order. In this case it would be better to introduce a setting which allows
 programmer to specify “source code natural language”, but this setting
 should be assigned per app, which is currently not possible in an elegant
 way. So I propose to cut my pull request to only removing English-centric
 behavior for now, as the second problem doesn’t seem to be an easy one to
 handle.

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

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

Re: [Django] #21086: XViewMiddleware clarification

[Django]

#21086: XViewMiddleware clarification
-+-
 Reporter:  OBu  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  admindocs|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 I don't think this bug report is correct.

 First, if something had to go into `INSTALLED_APPS`, it would be
 `"django.contrib.admindocs"` and not
 `"django.contrib.admindocs.middleware"`.

 Second, to activate a middleware, you need to add it in
 `MIDDLEWARE_CLASSES`, not in `INSTALLED_APPS`.

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

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

Re: [Django] #16184: GeoDjango inspectdb fails for PostGIS

[Django]

#16184: GeoDjango inspectdb fails for PostGIS
+
 Reporter:  radim.blazek@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  inspectdb   | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by anonymous):

 Doesn't work for two geometry-columns in one Table!

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

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

Re: [Django] #21082: django 1.5.1 custom User models bug

[Django]

#21082: django 1.5.1  custom User models bug
-+-
 Reporter:  xmmilk@… |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by claudep):

 * resolution:  needsinfo => worksforme


Comment:

 You are welcome. And yes, testing bugs with the latest version of Django
 is a good practice :-)

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

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