[django/django] 5ab951: Fix typo that disabled code example highlighting

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5ab95168cc719a59b64eb3923e9641d8b5f619e1
  
https://github.com/django/django/commit/5ab95168cc719a59b64eb3923e9641d8b5f619e1
  Author: Éric Araujo 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M docs/ref/models/instances.txt

  Log Message:
  ---
  Fix typo that disabled code example highlighting


  Commit: 597ab3ce98e1d73975901da0ee3cdcccd825eeb4
  
https://github.com/django/django/commit/597ab3ce98e1d73975901da0ee3cdcccd825eeb4
  Author: Alex Gaynor 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M docs/ref/models/instances.txt

  Log Message:
  ---
  Merge pull request #2654 from merwok/patch-1

Fix typo that disabled code example highlighting


Compare: https://github.com/django/django/compare/b90c112cb1c3...597ab3ce98e1

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

Re: [Django] #22510: Form fields cannot have names that are present as attributes on the form

[Django]

#22510: Form fields cannot have names that are present as attributes on the form
-+--
 Reporter:  gc@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by mjtamlyn):

 Ok fair point I now see why `MyForm.foo !== MyForm['foo']`.

 Having reviewed the available options, I'm happy to make a design decision
 to harden the current recommendation to use `None` into a requirement to
 use `None` assuming that solves this ticket (which I believe it does). If
 there are no objections, I can commit this at the sprints on Friday.

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

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

[django/django] 7fef18: [1.7.x] Dropped fix_IE_for_vary/attach.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 7fef18ba9e5a8b47bc24b5bb259c8bf3d3879f2a
  
https://github.com/django/django/commit/7fef18ba9e5a8b47bc24b5bb259c8bf3d3879f2a
  Author: Aymeric Augustin 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/core/handlers/base.py
M django/http/__init__.py
M django/http/utils.py
M tests/utils_tests/test_http.py

  Log Message:
  ---
  [1.7.x] Dropped fix_IE_for_vary/attach.

This is a security fix. Disclosure following shortly.


  Commit: e7b0cace455c2da24492660636bfd48c45a19cdf
  
https://github.com/django/django/commit/e7b0cace455c2da24492660636bfd48c45a19cdf
  Author: Erik Romijn 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/contrib/auth/tests/test_views.py
M django/utils/http.py
M tests/utils_tests/test_http.py

  Log Message:
  ---
  [1.7.x] Added additional checks in is_safe_url to account for flexible 
parsing.

This is a security fix. Disclosure following shortly.


  Commit: 77f0327d800965716122ead24584a0cffc018e54
  
https://github.com/django/django/commit/77f0327d800965716122ead24584a0cffc018e54
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
A docs/releases/1.4.13.txt
A docs/releases/1.5.8.txt
M docs/releases/1.6.5.txt
M docs/releases/index.txt

  Log Message:
  ---
  Added release notes for 1.4.13, 1.5.8, 1.6.5.


  Commit: 95cf17244c086cb31eef86bdb0db57a0b5d05e38
  
https://github.com/django/django/commit/95cf17244c086cb31eef86bdb0db57a0b5d05e38
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  Bumped version number for release.


  Commit: 9f5adf8db37280e8ddc093a36c9ad1c20142a5ca
  
https://github.com/django/django/commit/9f5adf8db37280e8ddc093a36c9ad1c20142a5ca
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M extras/Makefile

  Log Message:
  ---
  --skip-scripts is no longer a thing.

See 
https://bitbucket.org/pypa/wheel/commits/c29f82b4cf76df71f8d55b0f825af6063d3b9892.


Compare: https://github.com/django/django/compare/50f228ae7c7d...9f5adf8db372

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

[django/django] 1abcf3: [1.6.x] Dropped fix_IE_for_vary/attach.

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 1abcf3a808b35abae5d425ed4d44cb6e886dc769
  
https://github.com/django/django/commit/1abcf3a808b35abae5d425ed4d44cb6e886dc769
  Author: Aymeric Augustin 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/core/handlers/base.py
M django/http/__init__.py
M django/http/utils.py
M tests/utils_tests/test_http.py

  Log Message:
  ---
  [1.6.x] Dropped fix_IE_for_vary/attach.

This is a security fix. Disclosure following shortly.


  Commit: 601107524523bca02376a0ddc1a06c6fdb8f22f3
  
https://github.com/django/django/commit/601107524523bca02376a0ddc1a06c6fdb8f22f3
  Author: Erik Romijn 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/contrib/auth/tests/test_views.py
M django/utils/http.py
M tests/utils_tests/test_http.py

  Log Message:
  ---
  [1.6.x] Added additional checks in is_safe_url to account for flexible 
parsing.

This is a security fix. Disclosure following shortly.


  Commit: b053eb929b7d8ea191a2b0c13959bbf50cc68f1e
  
https://github.com/django/django/commit/b053eb929b7d8ea191a2b0c13959bbf50cc68f1e
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
A docs/releases/1.4.13.txt
A docs/releases/1.5.8.txt
M docs/releases/1.6.5.txt
M docs/releases/index.txt

  Log Message:
  ---
  Added release notes for 1.4.13, 1.5.8, 1.6.5.


  Commit: b5bacdea00c8ca980ff5885e15f7cd7b26b4dbb9
  
https://github.com/django/django/commit/b5bacdea00c8ca980ff5885e15f7cd7b26b4dbb9
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  Updated version numbers for release.


  Commit: 9dc7f69a4b91f98011396489a6b352c6af47a901
  
https://github.com/django/django/commit/9dc7f69a4b91f98011396489a6b352c6af47a901
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  Updated version numbers post-release.


Compare: https://github.com/django/django/compare/e05a6222cd40...9dc7f69a4b91

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

[django/django] 4001ec: [1.5.x] Dropped fix_IE_for_vary/attach.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 4001ec8698f577b973c5a540801d8a0bbea1205b
  
https://github.com/django/django/commit/4001ec8698f577b973c5a540801d8a0bbea1205b
  Author: Aymeric Augustin 
  Date:   2014-05-12 (Mon, 12 May 2014)

  Changed paths:
M django/core/handlers/base.py
M django/http/__init__.py
M django/http/utils.py
M tests/regressiontests/utils/http.py

  Log Message:
  ---
  [1.5.x] Dropped fix_IE_for_vary/attach.

This is a security fix. Disclosure following shortly.


  Commit: ad32c218850ad40972dcef57beb460f8c979dd6d
  
https://github.com/django/django/commit/ad32c218850ad40972dcef57beb460f8c979dd6d
  Author: Erik Romijn 
  Date:   2014-05-12 (Mon, 12 May 2014)

  Changed paths:
M django/contrib/auth/tests/views.py
M django/utils/http.py
M tests/regressiontests/utils/http.py

  Log Message:
  ---
  [1.5.x] Added additional checks in is_safe_url to account for flexible 
parsing.

This is a security fix. Disclosure following shortly.


  Commit: ffcb0091783c637670afeee6faa616e912f23279
  
https://github.com/django/django/commit/ffcb0091783c637670afeee6faa616e912f23279
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
A docs/releases/1.4.13.txt
A docs/releases/1.5.8.txt
M docs/releases/index.txt

  Log Message:
  ---
  Added release notes for 1.4.13, 1.5.8.


  Commit: 4e922f608424b36e83ff54a106392476e9e24c3e
  
https://github.com/django/django/commit/4e922f608424b36e83ff54a106392476e9e24c3e
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/__init__.py
M docs/conf.py
M setup.py

  Log Message:
  ---
  Bumped version numbers for release.


  Commit: 4752580881643d38b8c6c1b471d1ab8429c873d1
  
https://github.com/django/django/commit/4752580881643d38b8c6c1b471d1ab8429c873d1
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  Bumped version number post release.


Compare: https://github.com/django/django/compare/41ab97b6a4e7...475258088164

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

[django/django] 28e233: [1.4.x] Dropped fix_IE_for_vary/attach.

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 28e23306aa538fb87db85f99d970b051026c
  
https://github.com/django/django/commit/28e23306aa538fb87db85f99d970b051026c
  Author: Aymeric Augustin 
  Date:   2014-05-12 (Mon, 12 May 2014)

  Changed paths:
M django/core/handlers/base.py
M django/http/utils.py
M tests/regressiontests/utils/http.py

  Log Message:
  ---
  [1.4.x] Dropped fix_IE_for_vary/attach.

This is a security fix. Disclosure following shortly.


  Commit: 7feb54bbae3f637ab3c4dd4831d4385964f574df
  
https://github.com/django/django/commit/7feb54bbae3f637ab3c4dd4831d4385964f574df
  Author: Tim Graham 
  Date:   2014-05-12 (Mon, 12 May 2014)

  Changed paths:
M django/contrib/auth/tests/views.py
M django/utils/http.py
M tests/regressiontests/utils/http.py

  Log Message:
  ---
  [1.4.x] Added additional checks in is_safe_url to account for flexible 
parsing.

This is a security fix. Disclosure following shortly.


  Commit: fe5b3e36a2734581add6cfc11f55eb667887f092
  
https://github.com/django/django/commit/fe5b3e36a2734581add6cfc11f55eb667887f092
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
A docs/releases/1.4.13.txt
M docs/releases/index.txt

  Log Message:
  ---
  Added release notes for 1.4.13.


  Commit: 53b98b5a7cd7febc97add511c36d91285e03d86a
  
https://github.com/django/django/commit/53b98b5a7cd7febc97add511c36d91285e03d86a
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/__init__.py
M docs/conf.py
M setup.py

  Log Message:
  ---
  Bumped version numbers for release.


  Commit: 37d6821d35074ccbf1b0deeeb03561b07dbafd45
  
https://github.com/django/django/commit/37d6821d35074ccbf1b0deeeb03561b07dbafd45
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  Bumped version numbers post-release.


Compare: https://github.com/django/django/compare/e1812617cf53...37d6821d3507

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

[django/django] 8a2f04: typo: urlaprse -> urlparse

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8a2f04db914a66c4bfca7fc2f9a523c14dbbf3eb
  
https://github.com/django/django/commit/8a2f04db914a66c4bfca7fc2f9a523c14dbbf3eb
  Author: Collin Anderson 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/utils/http.py

  Log Message:
  ---
  typo: urlaprse -> urlparse


  Commit: b90c112cb1c3d6f80a748c784a191741f4ea3948
  
https://github.com/django/django/commit/b90c112cb1c3d6f80a748c784a191741f4ea3948
  Author: Alex Gaynor 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/utils/http.py

  Log Message:
  ---
  Merge pull request #2653 from collinanderson/patch-1

typo: urlaprse -> urlparse


Compare: https://github.com/django/django/compare/d4069a0a0dcd...b90c112cb1c3

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

[django/django] 3800f6: Dropped fix_IE_for_vary/attach.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3800f63721f6fc1c940abfb10fe21257dcf13521
  
https://github.com/django/django/commit/3800f63721f6fc1c940abfb10fe21257dcf13521
  Author: Aymeric Augustin 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/core/handlers/base.py
M django/http/__init__.py
M django/http/utils.py
M tests/utils_tests/test_http.py

  Log Message:
  ---
  Dropped fix_IE_for_vary/attach.

This is a security fix. Disclosure following shortly.


  Commit: 255449c1ee61c14778658caae8c430fa4d76afd6
  
https://github.com/django/django/commit/255449c1ee61c14778658caae8c430fa4d76afd6
  Author: Erik Romijn 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
M django/contrib/auth/tests/test_views.py
M django/utils/http.py
M tests/utils_tests/test_http.py

  Log Message:
  ---
  Added additional checks in is_safe_url to account for flexible parsing.

This is a security fix. Disclosure following shortly.


  Commit: d4069a0a0dcddf18d44d2c86227cb08adada0c6b
  
https://github.com/django/django/commit/d4069a0a0dcddf18d44d2c86227cb08adada0c6b
  Author: Jacob Kaplan-Moss 
  Date:   2014-05-14 (Wed, 14 May 2014)

  Changed paths:
A docs/releases/1.4.13.txt
A docs/releases/1.5.8.txt
M docs/releases/1.6.5.txt
M docs/releases/index.txt

  Log Message:
  ---
  Added release notes for 1.4.13, 1.5.8, 1.6.5.


Compare: https://github.com/django/django/compare/a06808d370ab...d4069a0a0dcd

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

Re: [Django] #22605: Impossible to delete two models with a M2M field

[Django]

#22605: Impossible to delete two models with a M2M field
-+--
 Reporter:  andrewgodwin |Owner:  andrewsg
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by andrewsg):

 andrewgodwin: this commit:
 
https://github.com/andrewsg/django/commit/ccb3843d482d0e9019f5dc9ffab06130fd1eb8fb
 is the current state of my branch, which is an unhappy place between a
 working and inefficient prototype (delete all models with no
 entanglements; delete ALL fields with references from those models; delete
 all remaining models) and my goal, which was for the autodetector to work
 out the strategy with the fewest migrations and operations.

 I stopped work when I realized that I really needed the delete models step
 to be two-phase like you mentioned, and figure out how to do the actual
 work intelligently.  The strategy my code followed initially, mimicking
 the create model code, was too "greedy".  Generalizing this so the
 autodetector does all of the work like this, so the add model and remove
 model special cases can be unified, sounds like a great idea.  Please feel
 free to take over the 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/070.05035dc3fc75eda0e7a409850ce82f0c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17642: min_num on admin inline formsets

[Django]

#17642: min_num on admin inline formsets
-+-
 Reporter:   |Owner:  timo
  krzysztof.szczesny@…   |   Status:  assigned
 Type:  New feature  |  Version:
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  admin min_num|  checkin
  formsets   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 I will give this a final review and merge it tomorrow.

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

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

Re: [Django] #22420: Postgresql connections not being dropped between tests?

[Django]

#22420: Postgresql connections not being dropped between tests?
---+--
 Reporter:  bacongobbler   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:
 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 gabrtv):

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


Comment:

 This is still an issue for us, but we were able to find a workaround I
 wanted to share:

 1. The problem is related to using threads that access the database inside
 a TransactionTestCase
 2. Explicitly closing database connections before the threads exit seems
 to resolve the issue

 We are using the following decorator:

 {{{
 def close_db_connections(func, *args, **kwargs):
 """
 Decorator to close db connections during threaded execution

 Note this is necessary to work around:
 https://code.djangoproject.com/ticket/22420
 """
 def _inner(*args, **kwargs):
 func(*args, **kwargs)
 for conn in connections.all():
 conn.close()
 return _inner
 }}}

 At first blush, it seems like TransactionTestCase may not be threadsafe.

 While I'd love to work on a minimal example of the broken behavior, I
 don't have time. :(

 Hopefully this workaround is helpful to others who may run across this
 problem.  Re-opening in case someone wants to take some action.

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

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

Re: [Django] #22605: Impossible to delete two models with a M2M field

[Django]

#22605: Impossible to delete two models with a M2M field
-+--
 Reporter:  andrewgodwin |Owner:  andrewsg
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by andrewgodwin):

 andrewsg: I have been mulling re-architecting the autodetector to fix this
 and a slew of other dependency bugs, so I think the solution may lie down
 that road (in particular, I want to change the autodetector to be two-
 phase; that is, it works out the changes to make, and then re-orders and
 sorts them so the dependencies line up).

 Given that, I'm not sure it would be a good idea to do any further work
 here, unless you want to; would you mind if I took over the ticket? I'd
 appreciate any code you have so far though, as I can probably use 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/070.a7bf03df7adb0266b6a799c2d4924339%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22628: min_num on formsets should not just be added to extra.

[Django]

#22628: min_num on formsets should not just be added to extra.
-+--
 Reporter:  melinath |Owner:  melinath
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by timo):

 * cc: timo (added)
 * severity:  Normal => Release blocker
 * 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/066.474d49e232403f93ad981bba0682eb40%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9532: Add min_num and validate_min on formsets

[Django]

#9532: Add min_num and validate_min on formsets
-+-
 Reporter:  gsf  |Owner:  yokomizor
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by melinath):

 Opened a new ticket for this: #22628

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

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

Re: [Django] #22628: min_num on formsets should not just be added to extra.

[Django]

#22628: min_num on formsets should not just be added to extra.
--+--
 Reporter:  melinath  |Owner:  melinath
 Type:  Bug   |   Status:  assigned
Component:  Forms |  Version:  1.7-beta-2
 Severity:  Normal|   Resolution:
 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 melinath):

 * owner:  nobody => melinath
 * needs_docs:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_better_patch:   => 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/066.d4f3a9904b78f8f85e99b1c1b4c619a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22628: min_num on formsets should not just be added to extra.

[Django]

#22628: min_num on formsets should not just be added to extra.
+
 Reporter:  melinath|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  1.7-beta-2
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 The current implementation is slightly broken.

 I would set min_num=3 if there should be at least three things. I would
 set extra=3 if I wanted three blank forms presented.

 The implementation that was added in 1.7 means that there will *always* be
 six blank forms - initial data is *not* taken into account.
 To put it another way, if min_num is 3, and extra is 2, and there is
 initial data for two forms, I would expect to have either 4 forms (2 extra
 on top of existing objects) or 5 forms (2 extra on top of the minimum.)
 With the code as it is, I will instead get seven forms - two for the
 existing objects, and an additional seven from extra.

 See note on #9532.

 (Is this a release blocker, since it's a bug in a new feature?)

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

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

Re: [Django] #22557: staticfiles.json keeps deleted entries when collectstatic is run

[Django]

#22557: staticfiles.json keeps deleted entries when collectstatic is run
-+-
 Reporter:  tedtieken|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:
 Severity:  Release blocker  |  1.7-beta-2
 Keywords:  hashed_files,|   Resolution:
  collectstatic, manifest| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 The release blocker flag is typically warranted for bugs in new features.
 I have looked at this a little, but it would be great if Jannis could do a
 final 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/067.7b85800a4464c15206d93a7710b4f014%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22620: "Multiple databases" chapter of docs says 'default':{} can start DATABASES setting; Django says no

[Django]

#22620: "Multiple databases" chapter of docs says 'default':{} can start 
DATABASES
setting; Django says no
--+
 Reporter:  moc@… |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:  multiple_databases| 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):

 * stage:  Unreviewed => Accepted


Comment:

 I think it's beyond the scope of the documentation to describe how to
 configure Django without a default database (and I imagine it's not a very
 common use case), but we could add a note that with the default settings
 of storing sessions in the DB, it won't work.

 I guess some improvements need to be made with respect to 2 and 3, though
 it seems rather complicated. I look forward to reviewing a patch if you
 are able to submit one.

 For future reference, it would be better to submit a separate ticket for
 each individual issue, thanks.

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

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

Re: [Django] #22605: Impossible to delete two models with a M2M field

[Django]

#22605: Impossible to delete two models with a M2M field
-+--
 Reporter:  andrewgodwin |Owner:  andrewsg
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by timo):

 * version:  master => 1.7-beta-2
 * 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/070.9e862bb42a875f466d8b2dc54432c56e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22625: Installing pytz breaks code already using django's timezone module

[Django]

#22625: Installing pytz breaks code already using django's timezone module
-+-
 Reporter:  tom.michaelis@…  |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  pytz, timezone   | 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):

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

Re: [Django] #22626: SQLite's DatabaseSchemaEditor.quote_value trips on buffer and memoryview instances

[Django]

#22626: SQLite's DatabaseSchemaEditor.quote_value trips on buffer and memoryview
instances
-+-
 Reporter:  loic84   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * version:  master => 1.7-beta-2
 * 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.35bccfc9c66fcb9a696462cbc5c2608b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22623: PermLookupDict behaves dangerously / inconsistently

[Django]

#22623: PermLookupDict behaves dangerously / inconsistently
-+-
 Reporter:  rob.moore@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  PermLookupDict   | Triage Stage:  Accepted
  permissions|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * component:  Uncategorized => contrib.auth
 * 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/086.c38b033e70a35ed0e5de8e2842052a06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17642: min_num on admin inline formsets

[Django]

#17642: min_num on admin inline formsets
-+-
 Reporter:   |Owner:  melinath
  krzysztof.szczesny@…   |   Status:  assigned
 Type:  New feature  |  Version:
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  admin min_num|  Needs documentation:  0
  formsets   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  1
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by timo):

 Yes, a separate PR to address that issue would be best.

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

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

Re: [Django] #9532: Add min_num and validate_min on formsets

[Django]

#9532: Add min_num and validate_min on formsets
-+-
 Reporter:  gsf  |Owner:  yokomizor
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by timo):

 I agree existing objects should be taken into account so the number of
 blank forms should be (min_num + extra - existing objects). Let's call it
 a bug and fix it now.

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

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

Re: [Django] #20695: "django.contrib.humanize" Turkish Translation Error

[Django]

#20695: "django.contrib.humanize" Turkish Translation Error
-+--
 Reporter:  ruless@… |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Translations |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by claudep):

 * status:  new => assigned


Comment:

 That's right, translation updates and fixes in the 1.6.x stable branch
 have not been ported to 1.7.x/master.

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

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

Re: [Django] #22625: Installing pytz breaks code already using django's timezone module

[Django]

#22625: Installing pytz breaks code already using django's timezone module
-+--
 Reporter:  tom.michaelis@…  |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  pytz, timezone   | 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):

 * owner:  nobody => aaugustin
 * needs_better_patch:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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