Re: [Django] #17552: The GZip Middleware's browser checking is buggy, as it does not send compressed content to modern versions of IE that support it.

[Django]

#17552: The GZip Middleware's browser checking is buggy, as it does not send
compressed content to modern versions of IE that support it.
-+-
 Reporter:  cannona  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  gzip middleware  | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"df09d854828bcff56eb72f48ff1ba8fce7e90c90"]:
 {{{
 #!CommitTicketReference repository=""
 revision="df09d854828bcff56eb72f48ff1ba8fce7e90c90"
 Fixed #17552 -- Removed a hack for IE6 and earlier.

 It prevented the GZipMiddleware from compressing some data types even on
 more recent version of IE where the corresponding bug was fixed.

 Thanks Aaron Cannon for the report and Tim Graham for the 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/065.d3437036c742f1c155c9555e8a998b53%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] df09d8: Fixed #17552 -- Removed a hack for IE6 and earlier...

[GitHub]

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

  Changed paths:
M django/middleware/gzip.py
M docs/ref/middleware.txt
M docs/releases/1.8.txt
M tests/middleware/tests.py

  Log Message:
  ---
  Fixed #17552 -- Removed a hack for IE6 and earlier.

It prevented the GZipMiddleware from compressing some data types even on
more recent version of IE where the corresponding bug was fixed.

Thanks Aaron Cannon for the report and Tim Graham for the review.


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

Re: [Django] #12708: Django raises DoesNotExist when consulting an empty ForeignKey field

[Django]

#12708: Django raises DoesNotExist when consulting an empty ForeignKey field
-+-
 Reporter:  lsaffre  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  ForeignKey   |  Unreviewed
  DoesNotExist   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by orshansk@…):

 Incompatibilities where you check if an order has a journal by trying to
 access it and checking for an exception. Unless people were proactive
 (think paranoid) and also checked for None, even though it was never
 allowed to be None, such a change would plainly break any and all such
 checks.

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

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

[django/django] eeea58: [1.7.x] Removed unused import.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: eeea58306178a7ae010767332693ed28e1ce03ac
  
https://github.com/django/django/commit/eeea58306178a7ae010767332693ed28e1ce03ac
  Author: Tim Graham 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M tests/admin_views/tests.py

  Log Message:
  ---
  [1.7.x] Removed unused import.

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

[django/django] fea8cc: Removed unused import.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fea8ccdcc4fa47ea1d494843624c92197b4f2153
  
https://github.com/django/django/commit/fea8ccdcc4fa47ea1d494843624c92197b4f2153
  Author: Tim Graham 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M tests/admin_views/tests.py

  Log Message:
  ---
  Removed unused import.


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

Re: [Django] #17552: The GZip Middleware's browser checking is buggy, as it does not send compressed content to modern versions of IE that support it.

[Django]

#17552: The GZip Middleware's browser checking is buggy, as it does not send
compressed content to modern versions of IE that support it.
-+-
 Reporter:  cannona  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  gzip middleware  | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

[Django]

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  new
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:
  Needs tests:  0| Triage Stage:  Accepted
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 As discussed on IRC, this change broke the tests on Oracle:
 {{{
   Applying migration_test_data_persistence.0001_initial...

 Traceback (most recent call last):
 ...
   File
 
"/var/lib/jenkins/workspace/DjangOra-1.8/database/oracle11/python/python2.7/django/db/backends/oracle/base.py",
 line 894, in execute
 return self.cursor.execute(query, self._param_generator(params))
 django.db.utils.IntegrityError: ORA-01400: cannot insert NULL into
 ("DJANGODJANGORA18_27"."MIGRATION_TEST_DATA_PERSISFB95"."ID")
 }}}

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

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

[django/django] bc0aba: Dropped support for SpatiaLite < 2.4.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bc0aba7786978ec312809eae5ecb3d751608b5b7
  
https://github.com/django/django/commit/bc0aba7786978ec312809eae5ecb3d751608b5b7
  Author: Tim Graham 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M django/contrib/gis/db/backends/spatialite/creation.py
M django/contrib/gis/db/backends/spatialite/operations.py
M django/db/backends/creation.py
M docs/ref/contrib/gis/install/geolibs.txt
M docs/ref/contrib/gis/install/spatialite.txt
M docs/ref/contrib/gis/testing.txt
M docs/releases/1.8.txt

  Log Message:
  ---
  Dropped support for SpatiaLite < 2.4.


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

Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  inspectdb,   |  Patch needs improvement:  0
  introspection, postgresql, |UI/UX:  0
  schema, oracle |
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by shai):

 Oracle doesn't have schemas in the sense of PG; @luzfcb -- are you sure
 Oracle is related here?

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

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

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

[Django]

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

 * has_patch:  1 => 0
 * version:  1.2 => 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.874817dfe930d17df3057c300f88fb9f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20420: Different query counts under Oracle when savepoints are involved

[Django]

#20420: Different query counts under Oracle when savepoints are involved
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (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 Aymeric Augustin ):

 In [changeset:"5cde9a7018021fc3c005e4ebcfa63967bcf56285"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5cde9a7018021fc3c005e4ebcfa63967bcf56285"
 [1.7.x] Fixed #20420 -- Normalized query counts on Oracle.

 This is achieved by inserting a fake entry in connection.queries when
 not releasing a savepoint (since Oracle doesn't support that operation.)

 Also removed the can_release_savepoints feature that was recently added,
 but is superseded by this solution.

 Backport of 40bfd856 from master.
 }}}

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

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

[django/django] e58798: [1.7.x] Simplified handling of use_debug_cursor.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: e5879811e6854852a2a0d8c850dd2a1795e09e9a
  
https://github.com/django/django/commit/e5879811e6854852a2a0d8c850dd2a1795e09e9a
  Author: Aymeric Augustin 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

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

  Log Message:
  ---
  [1.7.x] Simplified handling of use_debug_cursor.

Turned it from a tri-valued boolean into a regular boolean.

Backport of 127218b9 from master.


  Commit: 5cde9a7018021fc3c005e4ebcfa63967bcf56285
  
https://github.com/django/django/commit/5cde9a7018021fc3c005e4ebcfa63967bcf56285
  Author: Aymeric Augustin 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M django/db/backends/__init__.py
M django/db/backends/oracle/base.py
M tests/admin_views/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #20420 -- Normalized query counts on Oracle.

This is achieved by inserting a fake entry in connection.queries when
not releasing a savepoint (since Oracle doesn't support that operation.)

Also removed the can_release_savepoints feature that was recently added,
but is superseded by this solution.

Backport of 40bfd856 from master.


Compare: https://github.com/django/django/compare/11f0bdc00757...5cde9a701802

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

[django/django] 127218: Simplified handling of use_debug_cursor.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 127218b92bb8482fcb8b02457ed9797486ed3a22
  
https://github.com/django/django/commit/127218b92bb8482fcb8b02457ed9797486ed3a22
  Author: Aymeric Augustin 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

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

  Log Message:
  ---
  Simplified handling of use_debug_cursor.

Turned it from a tri-valued boolean into a regular boolean.


  Commit: 40bfd8561d016f6632c95d03e46a720571ad1a8a
  
https://github.com/django/django/commit/40bfd8561d016f6632c95d03e46a720571ad1a8a
  Author: Aymeric Augustin 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M django/db/backends/__init__.py
M django/db/backends/oracle/base.py
M tests/admin_views/tests.py

  Log Message:
  ---
  Fixed #20420 -- Normalized query counts on Oracle.

This is achieved by inserting a fake entry in connection.queries when
not releasing a savepoint (since Oracle doesn't support that operation.)

Also removed the can_release_savepoints feature that was recently added,
but is superseded by this solution.


Compare: https://github.com/django/django/compare/6b97ae352170...40bfd8561d01

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

Re: [Django] #20420: Different query counts under Oracle when savepoints are involved

[Django]

#20420: Different query counts under Oracle when savepoints are involved
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (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|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"40bfd8561d016f6632c95d03e46a720571ad1a8a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="40bfd8561d016f6632c95d03e46a720571ad1a8a"
 Fixed #20420 -- Normalized query counts on Oracle.

 This is achieved by inserting a fake entry in connection.queries when
 not releasing a savepoint (since Oracle doesn't support that operation.)

 Also removed the can_release_savepoints feature that was recently added,
 but is superseded by this solution.
 }}}

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

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

Re: [Django] #17552: The GZip Middleware's browser checking is buggy, as it does not send compressed content to modern versions of IE that support it.

[Django]

#17552: The GZip Middleware's browser checking is buggy, as it does not send
compressed content to modern versions of IE that support it.
-+
 Reporter:  cannona  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  gzip middleware  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by aaugustin):

 * needs_better_patch:  1 => 0


Comment:

 New patch: https://github.com/django/django/pull/2781

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

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

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

[Django]

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  closed
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:  fixed
  Needs tests:  0| Triage Stage:  Accepted
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"11f0bdc00757e5646337633f6a045b085f0653b2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="11f0bdc00757e5646337633f6a045b085f0653b2"
 [1.7.x] Added rollback emulation to spatialite backend; refs #22487.

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

[django/django] 11f0bd: [1.7.x] Added rollback emulation to spatialite bac...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 11f0bdc00757e5646337633f6a045b085f0653b2
  
https://github.com/django/django/commit/11f0bdc00757e5646337633f6a045b085f0653b2
  Author: Tim Graham 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M django/contrib/gis/db/backends/spatialite/creation.py

  Log Message:
  ---
  [1.7.x] Added rollback emulation to spatialite backend; refs #22487.

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

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

[Django]

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  closed
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:  fixed
  Needs tests:  0| Triage Stage:  Accepted
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"6b97ae352170d7be47176787056239cfbacb4803"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6b97ae352170d7be47176787056239cfbacb4803"
 Added rollback emulation to spatialite backend; refs #22487.
 }}}

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

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

[django/django] 6b97ae: Added rollback emulation to spatialite backend; re...

[GitHub]

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

  Changed paths:
M django/contrib/gis/db/backends/spatialite/creation.py

  Log Message:
  ---
  Added rollback emulation to spatialite backend; refs #22487.


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

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

[Django]

#22792: Check rule for list_display_links is incorrect
-+--
 Reporter:  bendavis78   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by timo):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Another issue we should also fix is in the previous check `admin.E123` --
 it should be `elif cls.list_display_links and field_name in
 cls.list_display_links` so that if `list_display_links` is `None` there
 isn't a `TypeError: argument of type 'NoneType' is not iterable` error.

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

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

Re: [Django] #17552: The GZip Middleware's browser checking is buggy, as it does not send compressed content to modern versions of IE that support it. (was: The GZip Middleware's browser checking is t

[Django]

#17552: The GZip Middleware's browser checking is buggy, as it does not send
compressed content to modern versions of IE that support it.
-+
 Reporter:  cannona  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  gzip middleware  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

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

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

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

[Django]

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

Comment (by aaugustin):

 Oops. Thank you for reopening.

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

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

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

[Django]

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

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


Comment:

 Replying to [comment:5 aaugustin]:
 > I think usage of IE 6 and Netscape 4 has fallen sufficiently to make
 this unnecessary. Sorry.

 Hi.  I certainly can't argue with this.  However, I suspect you might be
 misunderstanding the nature of the bug this ticket calls out.  As I
 understand it, the current code does not do any compression on certain
 types of content meant for IE, no matter the version.  This is the bug I
 was reporting.

 So, IMHO, the proper solution here, if we don't wish to support the older
 browsers, is to disable any checking of the user agent string, and just
 rely on whether or not they request compressed content.  That way, we're
 not refusing to send compressed content to modern versions of IE when it's
 requested.

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

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

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

[Django]

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  closed
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:  fixed
  Needs tests:  0| Triage Stage:  Accepted
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by andrewgodwin):

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


Comment:

 OK, I've pushed a fix for the test failures in
 f146e70cb1cfe34a9993a9a1d95faf2bb8b15ab1; re-closing optimistically.

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

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

[django/django] 7406fe: [1.7.x] Remove overzealous migration flushes from ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 7406feae33b70319c6e3a3edcd40e863692d29ed
  
https://github.com/django/django/commit/7406feae33b70319c6e3a3edcd40e863692d29ed
  Author: Andrew Godwin 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M tests/migrations/test_executor.py

  Log Message:
  ---
  [1.7.x] Remove overzealous migration flushes from migration test suite


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

[django/django] f146e7: Remove overzealous migration flushes from migratio...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f146e70cb1cfe34a9993a9a1d95faf2bb8b15ab1
  
https://github.com/django/django/commit/f146e70cb1cfe34a9993a9a1d95faf2bb8b15ab1
  Author: Andrew Godwin 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M tests/migrations/test_executor.py

  Log Message:
  ---
  Remove overzealous migration flushes from migration test suite


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

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

[Django]

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  new
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:
  Needs tests:  0| Triage Stage:  Accepted
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by andrewgodwin):

 What looks to be happening in those failures is that somehow the 0001
 migration for `migration_test_data_persistence` is being applied but not
 being marked as such, and so the call to migrate in
 `proxy_model_inheritance` tests is trying to re-apply it. Not sure why.

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

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

Re: [Django] #14296: 'manage.py test' failing for apps that access read-only databases

[Django]

#14296: 'manage.py test' failing for apps that access read-only databases
---+
 Reporter:  kthhrv |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.2
 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 gchp):

 * cc: gregchapple1@… (added)


Comment:

 As of b7aa7c4ab4372d2b7994d252c8bc87f77dd217ae you can use the `--keepdb`
 parameter to use an existing database rather than creating a new one for
 testing. This sounds more or less like what shai is describing above. It
 will run any outstanding migrations, and flush the data, but ultimately
 the database will be preserved at the end of the run.

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

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

[django/django] 417da8: [1.7.x] Doc edits for refs #22487.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 417da8a78277a14bd2348aec12d79b43f3dac6ee
  
https://github.com/django/django/commit/417da8a78277a14bd2348aec12d79b43f3dac6ee
  Author: Tim Graham 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M docs/ref/migration-operations.txt
M docs/ref/settings.txt
M docs/releases/1.7.txt
M docs/spelling_wordlist
M docs/topics/testing/advanced.txt
M docs/topics/testing/overview.txt

  Log Message:
  ---
  [1.7.x] Doc edits for refs #22487.

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

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

[Django]

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  new
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:
  Needs tests:  0| Triage Stage:  Accepted
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"417da8a78277a14bd2348aec12d79b43f3dac6ee"]:
 {{{
 #!CommitTicketReference repository=""
 revision="417da8a78277a14bd2348aec12d79b43f3dac6ee"
 [1.7.x] Doc edits for refs #22487.

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

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

[Django]

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  new
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:
  Needs tests:  0| Triage Stage:  Accepted
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"c17cd151d855ca1b8fcec894c5fccaa4a05be512"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c17cd151d855ca1b8fcec894c5fccaa4a05be512"
 Doc edits for refs #22487.
 }}}

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

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

[django/django] c17cd1: Doc edits for refs #22487.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c17cd151d855ca1b8fcec894c5fccaa4a05be512
  
https://github.com/django/django/commit/c17cd151d855ca1b8fcec894c5fccaa4a05be512
  Author: Tim Graham 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M docs/ref/migration-operations.txt
M docs/ref/settings.txt
M docs/releases/1.7.txt
M docs/spelling_wordlist
M docs/topics/testing/advanced.txt
M docs/topics/testing/overview.txt

  Log Message:
  ---
  Doc edits for refs #22487.


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

[django/django] 0a515b: [1.7.x] Fixed flake8 errors.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 0a515b02fcfa937e2a148148ca7be3e291e31d2e
  
https://github.com/django/django/commit/0a515b02fcfa937e2a148148ca7be3e291e31d2e
  Author: Tim Graham 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M django/db/backends/creation.py
M django/test/testcases.py

  Log Message:
  ---
  [1.7.x] Fixed flake8 errors.

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

[django/django] 4b25eb: Fixed flake8 error.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4b25ebf112d8bf4fcee6ee8339913bffdc81035d
  
https://github.com/django/django/commit/4b25ebf112d8bf4fcee6ee8339913bffdc81035d
  Author: Tim Graham 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M django/test/testcases.py

  Log Message:
  ---
  Fixed flake8 error.


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

[django/django] dd5513: Removed extras/csrf_migration_helper.py

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: dd551326433241f321fef9177e9487fef13348db
  
https://github.com/django/django/commit/dd551326433241f321fef9177e9487fef13348db
  Author: Tim Graham 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M docs/ref/contrib/csrf.txt
R extras/csrf_migration_helper.py

  Log Message:
  ---
  Removed extras/csrf_migration_helper.py


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

[django/django] 3a926c: Tweaked order of create_test_db arguments for back...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3a926c077863f0491ef66edbe451ee67c8fe59df
  
https://github.com/django/django/commit/3a926c077863f0491ef66edbe451ee67c8fe59df
  Author: Tim Graham 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M django/db/backends/creation.py
M docs/topics/testing/advanced.txt

  Log Message:
  ---
  Tweaked order of create_test_db arguments for backwards compatibility.

Since `serialize` was backported to 1.7, it should appear before `keepdb`.


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

Re: [Django] #22391: fallback to pymysql if MySQLdb not available

[Django]

#22391: fallback to pymysql if MySQLdb not available
-+-
 Reporter:  CollinAnderson   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 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 CollinAnderson):

 * needs_better_patch:  1 => 0


Comment:

 My branch merges cleanly again.
 https://github.com/django/django/pull/2520#issuecomment-45358916
 https://github.com/collinanderson/django/compare/ticket_22391

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

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

Re: [Django] #19973: Management commands migration to argparse

[Django]

#19973: Management commands migration to argparse
-+-
 Reporter:  jose |Owner:  jose
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  optparse, argparse,  |  Patch needs improvement:  0
  basecommand|UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 Here is the pull request with my work so far:
 https://github.com/django/django/pull/2780

 Comments welcome.

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

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

[Django] #22799: GET and POST on HttpRequest should be QueryDicts

[Django]

#22799: GET and POST on HttpRequest should be QueryDicts
---+
 Reporter:  duncan@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  HTTP handling  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 On a new HttpRequest object, GET and POST are are empty dictionaries when
 they really ought to be QueryDicts. This is not something you would
 usually notice causing trouble in production as you get a WSGIRequest
 instead of an HttpRequest, but in testing using the test client, calling
 .getlist on GET or POST for a request with no get/post data results in an
 AttributeError.

 I've made a pull request to change this:
 https://github.com/django/django/pull/2778

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

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

Re: [Django] #20766: Deprecate fastcgi support

[Django]

#20766: Deprecate fastcgi support
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  fastcgi   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"67ce2e74e1aafd3f85f6d64059d204e434e0e5f4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="67ce2e74e1aafd3f85f6d64059d204e434e0e5f4"
 Added missing deprecation note for fastcgi in 1.7 release notes; refs
 #20766.
 }}}

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

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

Re: [Django] #20766: Deprecate fastcgi support

[Django]

#20766: Deprecate fastcgi support
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  fastcgi   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"a11ed8dcfdce6820012ea219d1bbadb28c67b60d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a11ed8dcfdce6820012ea219d1bbadb28c67b60d"
 [1.7.x] Added missing deprecation note for fastcgi in 1.7 release notes;
 refs #20766.

 Backport of 67ce2e74e1 from master
 }}}

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

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

[django/django] a11ed8: [1.7.x] Added missing deprecation note for fastcgi...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: a11ed8dcfdce6820012ea219d1bbadb28c67b60d
  
https://github.com/django/django/commit/a11ed8dcfdce6820012ea219d1bbadb28c67b60d
  Author: Tim Graham 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  [1.7.x] Added missing deprecation note for fastcgi in 1.7 release notes; refs 
#20766.

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

[django/django] 67ce2e: Added missing deprecation note for fastcgi in 1.7 ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 67ce2e74e1aafd3f85f6d64059d204e434e0e5f4
  
https://github.com/django/django/commit/67ce2e74e1aafd3f85f6d64059d204e434e0e5f4
  Author: Tim Graham 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  Added missing deprecation note for fastcgi in 1.7 release notes; refs #20766.


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

Re: [Django] #8408: Add a new meta option: don't do count(*) in admin

[Django]

#8408: Add a new meta option: don't do count(*) in admin
---+
 Reporter:  lidaobing  |Owner:  oinopion
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by giuliettamasina):

 * cc: markus.magnuson@… (added)


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

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

Re: [Django] #22079: TestClient serialization of POST params with empty list as value

[Django]

#22079: TestClient serialization of POST params with empty list as value
-+-
 Reporter:   |Owner:  nobody
  code.djangoproject.com@…   |   Status:  new
 Type:  Bug  |  Version:  master
Component:  Testing framework|   Resolution:
 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|
-+-
Changes (by gchp):

 * cc: gregchapple1@… (added)


Comment:

 What is the desired behaviour here?

 From what I can see, the difference lies with using
 `django.utils.http.urlencode` to process the get params.

 {{{
 >>> from django.utils.http import urlencode

 >>> data = {'test': ['value1', 'value2']
 >>> urlencode(data, doseq=True)
 'test=value1&test=value2'

 >>> data = {'test': []}
 >>> urlencode(data, doseq=True)
 ''
 }}}

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

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

Re: [Django] #22798: pluralize filter should pluralize float/Decimal values between 1 and 2

[Django]

#22798: pluralize filter should pluralize float/Decimal values between 1 and 2
-+
 Reporter:  Odd_Bloke|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by aaugustin):

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


Comment:

 Aaah now I get it. Yes, the current behaviour should be changed for
 decimals when `1 < d < 2`. Sorry for closing incorrectly the other ticket.

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

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

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

[Django]

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  new
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:
  Needs tests:  0| Triage Stage:  Accepted
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 This seems to be causing some (non-deterministic?) failures in
 `proxy_model_inheritance.tests.ProxyModelInheritanceTests.test_table_exists`,
 when running the full test suite:
 {{{
 Traceback (most recent call last):
   File
 
"/mnt/jenkinsdata/workspace/django-1.7/database/sqlite3/python/python3.4/django/db/backends/utils.py",
 line 65, in execute
 return self.cursor.execute(sql, params)
   File
 
"/mnt/jenkinsdata/workspace/django-1.7/database/sqlite3/python/python3.4/django/db/backends/sqlite3/base.py",
 line 485, in execute
 return Database.Cursor.execute(self, query, params)
 sqlite3.OperationalError: table "migration_test_data_persistence_book"
 already exists
 }}}
 See:
 * http://djangoci.com/job/django-master/95/
 * http://djangoci.com/job/django-1.7/54/

 I can reproduce it locally; not sure why ci.djangoproject.com doesn't
 appear to be affected.

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

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

[Django] #22798: pluralize filter should pluralize float/Decimal values between 1 and 2

[Django]

#22798: pluralize filter should pluralize float/Decimal values between 1 and 2
-+
 Reporter:  Odd_Bloke|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.6
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 The pluralize filter works as expected for floats/Decimals outside of the
 range 1-2:

 {{{
 >>> pluralize(0.9)
 u's'
 >>> pluralize(2.1)
 u's'
 }}}

 However, when applied to a decimal number between 1 and 2, it
 (incorrectly) does not pluralize:

 {{{
 >>> pluralize(1.2)
 u''
 }}}

 Not only is this incorrect from an English standpoint, it also contradicts
 pluralize's docstring: "Returns a plural suffix if the value is not 1."

 The problem appears to be at
 
[https://github.com/django/django/blob/master/django/template/defaultfilters.py#L937
 line 937] where the given value is converted directly to an integer; this
 chops the decimal part of the number off, making it appear to be 1.

 The specific use case for this is:

 {{{
 {{ widget_count|floatformat:"-2" }} widget{{ widget_count|pluralize }}
 }}}

 This will produce "0.5 widgets", "1 widget", and "2.1 widgets" correctly,
 but "1.2 widget" incorrectly.


 (This ticket is a descendant of #16723, but that ticket was about a
 broader issue that encompassed this, and so ended up being closed as
 invalid.)

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

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

Re: [Django] #22351: New django migrations and places where lambdas are supposed

[Django]

#22351: New django migrations and places where lambdas are supposed
--+
 Reporter:  dimyur27@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  migrations lambdas| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by stefankoegl):

 * cc: stefankoegl (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/076.40a1193a75117503ad03b669673a7573%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[Django]

#19905: ResourceWarning in formtools tests
---+
 Reporter:  apollo13   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.formtools  |  Version:  master
 Severity:  Release blocker|   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Claude Paroz ):

 In [changeset:"d4623d13b731efef499b49576f883a5578297fdd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d4623d13b731efef499b49576f883a5578297fdd"
 [1.7.x] Fixed formtools tests with Python 2

 Fixes #19905 again.
 Backport of 1aaf4053f5 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.541ada48c8dc6e45109bb7c177719aac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] d4623d: [1.7.x] Fixed formtools tests with Python 2

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: d4623d13b731efef499b49576f883a5578297fdd
  
https://github.com/django/django/commit/d4623d13b731efef499b49576f883a5578297fdd
  Author: Claude Paroz 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M django/contrib/formtools/tests/wizard/namedwizardtests/tests.py
M django/contrib/formtools/tests/wizard/wizardtests/tests.py

  Log Message:
  ---
  [1.7.x] Fixed formtools tests with Python 2

Fixes #19905 again.
Backport of 1aaf4053f5 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/5395715e4bce2_3f711403d4064877%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 1aaf40: Fixed formtools tests with Python 2

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1aaf4053f5bda3e064448ca5abfa20eb3d029565
  
https://github.com/django/django/commit/1aaf4053f5bda3e064448ca5abfa20eb3d029565
  Author: Claude Paroz 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M django/contrib/formtools/tests/wizard/namedwizardtests/tests.py
M django/contrib/formtools/tests/wizard/wizardtests/tests.py

  Log Message:
  ---
  Fixed formtools tests with Python 2

Fixes #19905 again.


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

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

[Django]

#19905: ResourceWarning in formtools tests
---+
 Reporter:  apollo13   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.formtools  |  Version:  master
 Severity:  Release blocker|   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"1aaf4053f5bda3e064448ca5abfa20eb3d029565"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1aaf4053f5bda3e064448ca5abfa20eb3d029565"
 Fixed formtools tests with Python 2

 Fixes #19905 again.
 }}}

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

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

Re: [Django] #19973: Management commands migration to argparse

[Django]

#19973: Management commands migration to argparse
-+-
 Reporter:  jose |Owner:  jose
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  optparse, argparse,  |  Patch needs improvement:  0
  basecommand|UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Claude Paroz ):

 In [changeset:"96e4b52ab2c6fae3e46a197d44c42cb6ebde7d9c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="96e4b52ab2c6fae3e46a197d44c42cb6ebde7d9c"
 Converted Django scripts to argparse

 Refs #19973.
 }}}

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

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

[django/django] 96e4b5: Converted Django scripts to argparse

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 96e4b52ab2c6fae3e46a197d44c42cb6ebde7d9c
  
https://github.com/django/django/commit/96e4b52ab2c6fae3e46a197d44c42cb6ebde7d9c
  Author: Claude Paroz 
  Date:   2014-06-09 (Mon, 09 Jun 2014)

  Changed paths:
M django/contrib/admin/bin/compress.py
M extras/csrf_migration_helper.py
M scripts/manage_translations.py
M tests/runtests.py

  Log Message:
  ---
  Converted Django scripts to argparse

Refs #19973.


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

[Django] #22797: Base Generic View `_allowed_methods` could accept request args.

[Django]

#22797: Base Generic View `_allowed_methods` could accept request args.
-+
 Reporter:  Keryn Knight   |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Generic views|Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Currently,
 
[https://github.com/django/django/blob/e2f142030b81a37e1c3187f5d336dcb6014fd1c0/django/views/generic/base.py#L107
 View._allowed_methods] doesn't take into account the potential need for
 the request to change the availability/discover of methods, if for example
 the request comes with a token, cookie or whatever that grants additional
 method access.

 `_allowed_methods` is used in the base `View` by the
 
[https://github.com/django/django/blob/e2f142030b81a37e1c3187f5d336dcb6014fd1c0/django/views/generic/base.py#L103
 options HTTP verb] and
 
[https://github.com/django/django/blob/e2f142030b81a37e1c3187f5d336dcb6014fd1c0/django/views/generic/base.py#L96
 in http_method_not_allowed], both of which could pass on `request, *args,
 **kwargs` to `_allowed_methods`, and looking at
 [https://github.com/django/django/search?q=_allowed_methods&ref=cmdform
 GitHub's results] seems to indicate that's the only place it's used.
 Meanwhile [https://sourcegraph.com/search?q=%22_allowed_methods%22
 Sourcegraph] suggests that the only real public usage (admittedly in a
 largely depended upon package) downstream is in
 [https://github.com/tomchristie/django-rest-
 
framework/blob/07cb436d610b0e9b6e60b84412c8d6552c0c55a0/rest_framework/views.py#L106
 Django-Rest-Framework].

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

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