[Django] #22644: NamedUrlWizardView's done_step_name purpose unclear

[Django]

#22644: NamedUrlWizardView's done_step_name purpose unclear
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The documentation for NamedUrlWizardView's "done_step_name" option is
 unclear. First of all, the documentation says that you have to pass that
 argument, when, in fact, it's optional. Also, it's not super obvious that
 the "done_step_name" argument's value should not be the name of an actual
 URL from the urls.py file. Its just not very clear what the purpose of the
 argument is.

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

Re: [Django] #22638: Form wizard may raise unreasonable exceptions in case of SECRET_KEY change

[Django]

#22638: Form wizard may raise unreasonable exceptions in case of SECRET_KEY 
change
---+
 Reporter:  erikr  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.formtools  |  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 timo):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * 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/063.43d133af19abc50a5fd406e1c45060d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22637: Documentation not clear about the effects of max_length for IntegerField

[Django]

#22637: Documentation not clear about the effects of max_length for IntegerField
---+--
 Reporter:  msn@…  |Owner:
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 I don't think there's value in documenting parameters that don't appear in
 the documentation have no effect.

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

Re: [Django] #22640: Can create model instance with conflicting args and kwargs value for the same field

[Django]

#22640: Can create model instance with conflicting args and kwargs value for the
same field
-+-
 Reporter:  zsoldosp |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 For what it's worth, I didn't realize there was any attempt to support
 positional arguments in model instantiation (although it is tested, is it
 documented anywhere?). May not be worth fixing, in my opinion.

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

Re: [Django] #22639: Fix inconsistency with imports in documentation

[Django]

#22639: Fix inconsistency with imports in documentation
--+
 Reporter:  niclas.ahden  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

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

Re: [Django] #16245: send_robust should include traceback in response when Exception occurs

[Django]

#16245: send_robust should include traceback in response when Exception occurs
-+-
 Reporter:  jsdalton |Owner:
 Type:   |  unaizalakain
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  signals  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ebb0279f4a7a7155c44c09506bbe5b1f9acc83a2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ebb0279f4a7a7155c44c09506bbe5b1f9acc83a2"
 Fixed #16245 -- Included traceback in send_robust()'s response

 Exceptions from the (receiver, exception) tuples returned by
 ``send_robust()`` now have always their traceback attached as their
 ``__traceback__`` argument.
 }}}

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

[django/django] ebb027: Fixed #16245 -- Included traceback in send_robust(...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ebb0279f4a7a7155c44c09506bbe5b1f9acc83a2
  
https://github.com/django/django/commit/ebb0279f4a7a7155c44c09506bbe5b1f9acc83a2
  Author: Unai Zalakain 
  Date:   2014-05-16 (Fri, 16 May 2014)

  Changed paths:
M django/dispatch/dispatcher.py
M docs/releases/1.8.txt
M docs/topics/signals.txt
M tests/dispatch/tests/test_dispatcher.py

  Log Message:
  ---
  Fixed #16245 -- Included traceback in send_robust()'s response

Exceptions from the (receiver, exception) tuples returned by
``send_robust()`` now have always their traceback attached as their
``__traceback__`` argument.


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

[django/django] 0594d2: [1.7.x] Added stub release notes for 1.6.6.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 0594d2d71492653a27e2668c2f18ba128f9277d9
  
https://github.com/django/django/commit/0594d2d71492653a27e2668c2f18ba128f9277d9
  Author: Tim Graham 
  Date:   2014-05-16 (Fri, 16 May 2014)

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

  Log Message:
  ---
  [1.7.x] Added stub release notes for 1.6.6.

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

[django/django] ee075c: [1.6.x] Added stub release notes for 1.6.6.

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: ee075c448461350aeb9bc4829a8581619c95224d
  
https://github.com/django/django/commit/ee075c448461350aeb9bc4829a8581619c95224d
  Author: Tim Graham 
  Date:   2014-05-16 (Fri, 16 May 2014)

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

  Log Message:
  ---
  [1.6.x] Added stub release notes for 1.6.6.

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

[django/django] 79e9da: Added stub release notes for 1.6.6.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 79e9da3d1ef8c4bdc20d53b668228abb219ac55b
  
https://github.com/django/django/commit/79e9da3d1ef8c4bdc20d53b668228abb219ac55b
  Author: Tim Graham 
  Date:   2014-05-16 (Fri, 16 May 2014)

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

  Log Message:
  ---
  Added stub release notes for 1.6.6.


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

[django/django] b7a67b: [1.7.x] Fixed storing of binary fields and unicode...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: b7a67b788cf2fa59a84f933492413379eb3cab83
  
https://github.com/django/django/commit/b7a67b788cf2fa59a84f933492413379eb3cab83
  Author: Shai Berger 
  Date:   2014-05-17 (Sat, 17 May 2014)

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

  Log Message:
  ---
  [1.7.x] Fixed storing of binary fields and unicode textfields for 
Oracle/Python3

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

Re: [Django] #22641: Add interactive mode to startproject command

[Django]

#22641: Add interactive mode to startproject command
-+-
 Reporter:  giuliettamasina  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Duplicate of #21521

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

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

Re: [Django] #22642: On Django tutorial 5 'Poll' changes to 'Question'

[Django]

#22642: On Django tutorial 5 'Poll' changes to 'Question'
---+--
 Reporter:  Polly.shaw@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 I think you are mixing versions of the tutorial. `Poll` was changed to
 `Question` in the 1.7 version. From a quick look, the 1.6 version look
 okay to me. Please reopen if that's not the case.

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

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

[django/django] 8c5fbc: [1.7.x] Fixed case in form widgets docs

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 8c5fbcf50aecec8ecfb802694af4dd7e0c9d666f
  
https://github.com/django/django/commit/8c5fbcf50aecec8ecfb802694af4dd7e0c9d666f
  Author: Claude Paroz 
  Date:   2014-05-16 (Fri, 16 May 2014)

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

  Log Message:
  ---
  [1.7.x] Fixed case in form widgets docs

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

[django/django] ba40d6: [1.6.x] Fixed case in form widgets docs

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: ba40d6509aac626763e534f555d50be895b53e75
  
https://github.com/django/django/commit/ba40d6509aac626763e534f555d50be895b53e75
  Author: Claude Paroz 
  Date:   2014-05-16 (Fri, 16 May 2014)

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

  Log Message:
  ---
  [1.6.x] Fixed case in form widgets docs

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

Re: [Django] #22643: CheckboxInput has wrong name in docs

[Django]

#22643: CheckboxInput has wrong name in docs
---+--
 Reporter:  david@…|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Forms  |  Version:  1.5
 Severity:  Normal |   Resolution:  fixed
 Keywords:  Documentation  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 This was already fixed on master in [9494f29d]. I backported to 1.5.x and
 later.

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

[django/django] 044a4f: [1.5.x] Fixed case in form widgets docs

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 044a4fd7a898354de1cd6f923e4f929ce2db5faa
  
https://github.com/django/django/commit/044a4fd7a898354de1cd6f923e4f929ce2db5faa
  Author: Claude Paroz 
  Date:   2014-05-16 (Fri, 16 May 2014)

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

  Log Message:
  ---
  [1.5.x] Fixed case in form widgets docs

Backport of 9494f29d 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/537686871b93a_6013de7d44961c6%40hookshot-fe2-cp1-prd.iad.github.net.mail.
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:  closed
Component:  Utilities|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 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
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"62de03ee337e085dbaa9d94a43a2aedbd3cdef84"]:
 {{{
 #!CommitTicketReference repository=""
 revision="62de03ee337e085dbaa9d94a43a2aedbd3cdef84"
 [1.7.x] Optimized make_aware/naive by removing redundant checks. Refs
 #22625.

 Also added tests with pytz and removed misplaced tests.

 Backport of 1109ebd from master
 }}}

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

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

[django/django] 62de03: [1.7.x] Optimized make_aware/naive by removing red...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 62de03ee337e085dbaa9d94a43a2aedbd3cdef84
  
https://github.com/django/django/commit/62de03ee337e085dbaa9d94a43a2aedbd3cdef84
  Author: Aymeric Augustin 
  Date:   2014-05-16 (Fri, 16 May 2014)

  Changed paths:
M django/utils/timezone.py
M tests/timezones/tests.py
M tests/utils_tests/test_timezone.py

  Log Message:
  ---
  [1.7.x] Optimized make_aware/naive by removing redundant checks. Refs #22625.

Also added tests with pytz and removed misplaced tests.

Backport of 1109ebd 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/53767fab4c6ca_6f0cb7dd3850422%40hookshot-fe2-cp1-prd.iad.github.net.mail.
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:  closed
Component:  Utilities|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 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
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"1109ebd7b373e14b68616346ea5dd3e89a8ae2fe"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1109ebd7b373e14b68616346ea5dd3e89a8ae2fe"
 Optimized make_aware/naive by removing redundant checks. Refs #22625.

 Also added tests with pytz and removed misplaced tests.
 }}}

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

[django/django] 1109eb: Optimized make_aware/naive by removing redundant c...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1109ebd7b373e14b68616346ea5dd3e89a8ae2fe
  
https://github.com/django/django/commit/1109ebd7b373e14b68616346ea5dd3e89a8ae2fe
  Author: Aymeric Augustin 
  Date:   2014-05-16 (Fri, 16 May 2014)

  Changed paths:
M django/utils/timezone.py
M tests/timezones/tests.py
M tests/utils_tests/test_timezone.py

  Log Message:
  ---
  Optimized make_aware/naive by removing redundant checks. Refs #22625.

Also added tests with pytz and removed misplaced tests.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/53767f9cf0a85_65305d7d343313a%40hookshot-fe1-cp1-prd.iad.github.net.mail.
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:  closed
Component:  Utilities|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 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
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"6f8301d6cd3815409c7c2c8468dbfd239d39f468"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6f8301d6cd3815409c7c2c8468dbfd239d39f468"
 [1.7.x] Fixed #22625 -- Normalized make_aware/naive errors.

 Also added tests for is/make_aware/naive.

 Thanks Tom Michaelis for the report.

 Backport of fa89acf from master
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/081.9e078ad9515eae0c574c105b099291d7%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:  closed
Component:  Utilities|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 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 Aymeric Augustin ):

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


Comment:

 In [changeset:"fa89acf1d0a4adbf0802c1275494f5159a912c9e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fa89acf1d0a4adbf0802c1275494f5159a912c9e"
 Fixed #22625 -- Normalized make_aware/naive errors.

 Also added tests for is/make_aware/naive.

 Thanks Tom Michaelis for the report.
 }}}

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

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

[django/django] 6f8301: [1.7.x] Fixed #22625 -- Normalized make_aware/naiv...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 6f8301d6cd3815409c7c2c8468dbfd239d39f468
  
https://github.com/django/django/commit/6f8301d6cd3815409c7c2c8468dbfd239d39f468
  Author: Aymeric Augustin 
  Date:   2014-05-16 (Fri, 16 May 2014)

  Changed paths:
M django/utils/timezone.py
M tests/utils_tests/test_timezone.py

  Log Message:
  ---
  [1.7.x] Fixed #22625 -- Normalized make_aware/naive errors.

Also added tests for is/make_aware/naive.

Thanks Tom Michaelis for the report.

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

[django/django] fa89ac: Fixed #22625 -- Normalized make_aware/naive errors...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fa89acf1d0a4adbf0802c1275494f5159a912c9e
  
https://github.com/django/django/commit/fa89acf1d0a4adbf0802c1275494f5159a912c9e
  Author: Aymeric Augustin 
  Date:   2014-05-16 (Fri, 16 May 2014)

  Changed paths:
M django/utils/timezone.py
M tests/utils_tests/test_timezone.py

  Log Message:
  ---
  Fixed #22625 -- Normalized make_aware/naive errors.

Also added tests for is/make_aware/naive.

Thanks Tom Michaelis for the report.


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

Comment (by aaugustin):

 There are two possible semantics when make_aware receives an aware
 datetime (or make_naive receives a naive datetime):

 - raise an exception
 - return the value unchanged

 Since Django uses the first one when pytz is installed, and the docs
 recommend to install pytz, it makes sense to enforce that behavior.

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

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

[django/django] 1efb2e: Fixed typo.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1efb2e73bf13100639c4f06963220549a7eb725c
  
https://github.com/django/django/commit/1efb2e73bf13100639c4f06963220549a7eb725c
  Author: Tim Graham 
  Date:   2014-05-16 (Fri, 16 May 2014)

  Changed paths:
M django/db/models/base.py

  Log Message:
  ---
  Fixed typo.


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

Re: [Django] #22643: CheckboxInput has wrong name in docs

[Django]

#22643: CheckboxInput has wrong name in docs
---+--
 Reporter:  david@…|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  Documentation  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by david@…):

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


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

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

[Django] #22643: CheckboxInput has wrong name in docs

[Django]

#22643: CheckboxInput has wrong name in docs
---+---
 Reporter:  david@…|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Forms  |Version:  1.5
 Severity:  Normal |   Keywords:  Documentation
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 In the documentation on widgets, CheckBoxInput should be changed to match
 the class name in widgets.py (CheckboxInput).

 Maybe best to follow convention with other widgets and capitalize the
 start of each word (i.e. CheckBoxInput vs CheckboxInput).

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

[Django] #22642: On Django tutorial 5 'Poll' changes to 'Question'

[Django]

#22642: On Django tutorial 5 'Poll' changes to 'Question'
---+
 Reporter:  Polly.shaw@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 About halfway down tutorial 5 the code starts using the word 'Question' in
 place of 'Poll' which means that the app & test code don't work.

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

Re: [Django] #16883: Importing models.py from not-installed app prevents any other app with that label from loading

[Django]

#16883: Importing models.py from not-installed app prevents any other app with 
that
label from loading
-+-
 Reporter:  carljm   |Owner:  nott
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  app-loading  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * keywords:   => app-loading
 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 I believe this is solved by the app loading refactor in 1.7, or will be in
 1.9. Such invalid combinations will raise an exception, possibly after a
 deprecation path.

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

[django/django] 6bb6df: Fix storing of binary fields and unicode textfield...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6bb6df29431b606937637be5837cc671836b142b
  
https://github.com/django/django/commit/6bb6df29431b606937637be5837cc671836b142b
  Author: Shai Berger 
  Date:   2014-05-16 (Fri, 16 May 2014)

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

  Log Message:
  ---
  Fix storing of binary fields and unicode textfields for Oracle/Python3


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5376585e63f2_5e1f12bbd34883aa%40hookshot-fe1-cp1-prd.iad.github.net.mail.
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:  xelnor
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | 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 xelnor):

 * stage:  Accepted => Ready for checkin


Comment:

 I've updated the patch, which has been reviewed by shai.

 Marking "Ready for Checkin" with his benediction.

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

Re: [Django] #22637: Documentation not clear about the effects of max_length for IntegerField

[Django]

#22637: Documentation not clear about the effects of max_length for IntegerField
---+--
 Reporter:  msn@…  |Owner:
 Type:  Bug|   Status:  new
Component:  Documentation  |  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:  1  |UI/UX:  0
---+--
Changes (by sabinemaennel):

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


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

Re: [Django] #22637: Documentation not clear about the effects of max_length for IntegerField

[Django]

#22637: Documentation not clear about the effects of max_length for IntegerField
---+-
 Reporter:  msn@…  |Owner:  sabinemaennel
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  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:  1  |UI/UX:  0
---+-

Comment (by sabinemaennel):

 Hello ,
 I just tested this. This is my result:

 Assigning the option `max_length` to an `IntegerField` in your model does
 not have any effect, neither on the database where the field is just
 generated as an `models.IntegerField()` nor on the Admin Form, where the
 field is always generated as `"type=text"`and `class="vIntegerField"`.  So
 it does not really make sense to have that option here.

 I talked about this with chai about this and the opinion was that the
 option should not be forbidden in order to keep Django upward compatible,
 but that it also does not make sense for the `IntegerField`.

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

Re: [Django] #12663: Information provided by Model._meta should be documented in /models/options/

[Django]

#12663: Information provided by Model._meta should be documented in
/models/options/
-+-
 Reporter:  MadeR|Owner:  pirosb3
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  Model Meta   | Triage Stage:  Accepted
  Documentation  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by pirosb3):

 * cc: pirosb3 (added)
 * status:  new => assigned
 * owner:  adamv => pirosb3
 * stage:  Someday/Maybe => Accepted


Comment:

 Hi!

 I will pick this up as SoC 2014, where I will be refactoring Meta:
 
https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo/edit#

 For anything, ping me on #django-dev or on the Google Groups

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

Re: [Django] #21584: prefetch_related child queryset does not update on create

[Django]

#21584: prefetch_related child queryset does not update on create
-+-
 Reporter:  lucaswiman   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by lucaswiman):

 > This is not a bug, I'm afraid.


  It's very unintuitive that the child_set won't keep track of what
 elements are in it when it is mutated by its own methods. This seems to
 break the "iterable" abstraction.


  >There may be some small exceptions, such as when you update a FK object,
 and the FK ID on that object may be updated as well, but only those that
 can be done with no dependency tracking


 Isn't that precisely the behavior that's being described here?  The
 foreign key relationship should know that a new entry was created, because
 the create method was called on the child_set itself.  Create should
 invalidate the cache, because there's no way the cache can remain valid
 after create is called.  Couldn't create set self._results_cache to None,
 and self.prefetch_done to False when create is called?

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

Re: [Django] #22630: models.EmailField allows a dict to be saved without raising an error resulting in Python dict strings saved to the DB

[Django]

#22630: models.EmailField allows a dict to be saved without raising an error
resulting in Python dict strings saved to the DB
-+-
 Reporter:  joe@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:  email orm field  |  Unreviewed
  validators |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by joe@…):

 So that does raise an error:

 {{{
 In [1]: from wasatch.models import User

 In [2]: from accounts.models import AlternateEmail

 In [3]: email = AlternateEmail(user=User.objects.get(pk=1))

 In [4]: email.email = {'verified': True, 'email': 'j...@example.com'}

 In [5]: email.full_clean()
 ---
 ValidationError   Traceback (most recent call
 last)
 /Users/jstump/Dropbox/jstump/.virtualenvs/sprint.ly/lib/python2.7/site-
 packages/django/core/management/commands/shell.pyc in ()
 > 1 email.full_clean()

 /Users/jstump/Dropbox/jstump/.virtualenvs/sprint.ly/lib/python2.7/site-
 packages/django/db/models/base.pyc in full_clean(self, exclude)
 822
 823 if errors:
 --> 824 raise ValidationError(errors)
 825
 826 def clean_fields(self, exclude=None):

 ValidationError: {'email': [u'Enter a valid e-mail address.']}
 }}}

 Still not sure why that form is marked as valid though.

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

Re: [Django] #22630: models.EmailField allows a dict to be saved without raising an error resulting in Python dict strings saved to the DB

[Django]

#22630: models.EmailField allows a dict to be saved without raising an error
resulting in Python dict strings saved to the DB
-+-
 Reporter:  joe@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:  email orm field  |  Unreviewed
  validators |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timo):

 In the example gist, you haven't actually
 [https://docs.djangoproject.com/en/dev/ref/models/instances/#validating-
 objects invoked model validation] before you saved the object. Does adding
 `email.full_clean()` before `save()` change anything?

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

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

[Django] #22641: Add interactive mode to startproject command

[Django]

#22641: Add interactive mode to startproject command
+
 Reporter:  giuliettamasina |  Owner:  nobody
 Type:  New feature | Status:  new
Component:  Core (Management commands)  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 A few of us at !DjangoCon EU 2014 have been discussing the idea of an
 interactive mode for the management command `startproject` (or
 `startapp`).

 Passing `--interactive` or `-i` to the command would let you answer a few
 questions about your project, from which an ideal project setup is
 created, regarding settings etc.

 This could for example be "Do you want to use a database?" or "Do you want
 to configure the new project according to your current location?" and so
 on.

 Nothing very concrete at the moment, but I just wanted to probe the
 interest in such a feature before going into details. If in favor by the
 core devs, this is the kind of thing that would probably benefit from open
 discussion, to gather further ideas.

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

Re: [Django] #22630: models.EmailField allows a dict to be saved without raising an error resulting in Python dict strings saved to the DB

[Django]

#22630: models.EmailField allows a dict to be saved without raising an error
resulting in Python dict strings saved to the DB
-+-
 Reporter:  joe@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:  email orm field  |  Unreviewed
  validators |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by joe@…):

 I don't believe that will fix this issue given that the simple
 `f.is_valid()` returns `True` for a `dict`, but I will test and report
 back.

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

Re: [Django] #22501: The testing client of LiveServerTestCase has the wrong server address

[Django]

#22501: The testing client of LiveServerTestCase has the wrong server address
---+--
 Reporter:  daonb  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by magopian):

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


Comment:

 Hi,

 this is actually a feature, to have reproducible tests wherever you run
 them:
 https://github.com/django/django/blob/master/django/test/client.py#L236

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

Re: [Django] #22111: Signal can throw ValueError in debug mode

[Django]

#22111: Signal can throw ValueError in debug mode
--+
 Reporter:  ilya_pirogov  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Python 3  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timo):

 I don't think there's a need to alias all of `inspect` under
 `django.utils.inspect`. Maybe the fix is too specific to Django, but I
 wonder if it wouldn't be better to try to include this in a Python 2/3
 compatibility library like [http://pythonhosted.org/six/ six].

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

Re: [Django] #18586: Rewrite unit tests migrated from doctests

[Django]

#18586: Rewrite unit tests migrated from doctests
--+
 Reporter:  konk  |Owner:  judy2k
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  unit tests| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by zsoldosp):

 * cc: zsoldosp (added)


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

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

Re: [Django] #18586: Rewrite unit tests migrated from doctests

[Django]

#18586: Rewrite unit tests migrated from doctests
--+
 Reporter:  konk  |Owner:  judy2k
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  unit tests| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by zsoldosp):

 * has_patch:  0 => 1


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

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

Re: [Django] #22639: Fix inconsistency with imports in documentation

[Django]

#22639: Fix inconsistency with imports in documentation
-+-
 Reporter:  niclas.ahden |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 Sure, we could use dot imports. I guess it would be good to encourage
 that.

 I don't think it's true that snippets should be safe to copy and paste. We
 use `...` in a lot of places where, for example purposes, the contents of
 a function don't matter. Adding the rest of the method body or whatever
 the ellipses are replacing is just going to obfuscate the purpose of the
 example.  For example:

 {{{
 from django.forms.models import BaseInlineFormSet

 class CustomInlineFormSet(BaseInlineFormSet):
 def clean(self):
 super(CustomInlineFormSet, self).clean()
 # example custom validation across forms in the formset
 for form in self.forms:
 # your custom formset validation
 ...
 }}}

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

Re: [Django] #21062: Transition to Generic Views Reference to Changing Poll_ID to PK, Yet No change is visible

[Django]

#21062: Transition to Generic Views Reference to Changing Poll_ID to PK, Yet No
change is visible
-+-
 Reporter:  john@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.6-beta-1
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by cyberyt):

 I also came here regarding that, I think the bullet point should be moved
 up, or make an explicit reference to that it's talking about urls.py and
 not views.py?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/077.50bd0ec2e2e9c05513f1af969d2984fe%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:  xelnor
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |  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
-+-
Changes (by xelnor):

 * has_patch:  0 => 1


Comment:

 A full patch including test has been added at
 https://github.com/django/django/pull/2670 (pull request against
 stable/1.7.x).

 This patch also fixes a slight issue in the SQLite backend when re-making
 a table: default values for new fields where incorrectly quoted with
 "column name" quoting rules.

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

Re: [Django] #22633: LANGUAGE_CODE should be automatically set based on system locale

[Django]

#22633: LANGUAGE_CODE should be automatically set based on system locale
--+
 Reporter:  hakanw|Owner:  hakanw
 Type:  New feature   |   Status:  assigned
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by hakanw):

 * has_patch:  0 => 1


Comment:

 Now there's code + tests that pass above.

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

Re: [Django] #6668: Optimise utils.text wrap

[Django]

#6668: Optimise utils.text wrap
-+-
 Reporter:  SmileyChris  |Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by giuliettamasina):

 However, I have no idea why the `wordwrap` tests are in
 `test_wordcount()`. I added another commit to just move them to their own
 method.

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

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

Re: [Django] #22639: Fix inconsistency with imports in documentation

[Django]

#22639: Fix inconsistency with imports in documentation
-+-
 Reporter:  niclas.ahden |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by niclas.ahden):

 Before your comment we had a short discussion with bmispelon about this
 and agreed that adding a brief guideline to the contributor documentation
 would be good. The general rule being that snippets should preferably be
 safe to copy and paste.

 What do you think?

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

[django/django] 2e364a: Fixed #15716 - Authentication backends can short-c...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2e364a0aacb49a5160896b1ca5a2619baa3f4d9b
  
https://github.com/django/django/commit/2e364a0aacb49a5160896b1ca5a2619baa3f4d9b
  Author: Jorge C. Leitão 
  Date:   2014-05-16 (Fri, 16 May 2014)

  Changed paths:
M django/contrib/auth/models.py
M django/contrib/auth/tests/test_auth_backends.py
M docs/releases/1.8.txt
M docs/topics/auth/customizing.txt

  Log Message:
  ---
  Fixed #15716 - Authentication backends can short-circuit authorization.

Authorization backends can now raise PermissionDenied in "has_perm"
and "has_module_perms" to short-circuit authorization process.


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

Re: [Django] #15716: The has_perm() method of authorization backends should be able to explicitly deny permission

[Django]

#15716: The has_perm() method of authorization backends should be able to
explicitly deny permission
--+--
 Reporter:  Kronuz|Owner:  jorgecarleitao
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"2e364a0aacb49a5160896b1ca5a2619baa3f4d9b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2e364a0aacb49a5160896b1ca5a2619baa3f4d9b"
 Fixed #15716 - Authentication backends can short-circuit authorization.

 Authorization backends can now raise PermissionDenied in "has_perm"
 and "has_module_perms" to short-circuit authorization process.
 }}}

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

Re: [Django] #22630: models.EmailField allows a dict to be saved without raising an error resulting in Python dict strings saved to the DB

[Django]

#22630: models.EmailField allows a dict to be saved without raising an error
resulting in Python dict strings saved to the DB
-+-
 Reporter:  joe@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:  email orm field  |  Unreviewed
  validators |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by joe@…):

 Using your example you can see it's failing on the forms as well:

 {{{
 In [14]: f = EmailForm({'email': {'test': 'foo', 'email':
 'j...@example.com'}})

 In [15]: f.is_valid()
 Out[15]: 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/074.37366aedcfe37a90d3b0ff67c43593e4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22424: Default value for TextField

[Django]

#22424: Default value for TextField
-+--
 Reporter:  Nevsky   |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-1
 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 syphar):

 Update the PR with some comments:
 https://github.com/django/django/pull/2634

 short version:
 PR failing when there are empty or string defaults.
 But with fixed everything (in this ticket) seems fine.

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

Re: [Django] #22424: Default value for TextField

[Django]

#22424: Default value for TextField
-+--
 Reporter:  Nevsky   |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-1
 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 syphar):

 * cc: denis.cornehl@… (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/064.8a74b3940301419f87b91f03e13dc8f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22630: models.EmailField allows a dict to be saved without raising an error resulting in Python dict strings saved to the DB (was: EmailField allows invalid text to be saved as long as a

[Django]

#22630: models.EmailField allows a dict to be saved without raising an error
resulting in Python dict strings saved to the DB
-+-
 Reporter:  joe@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:  email orm field  |  Unreviewed
  validators |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  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/074.e41690879577b4fb14ba19d86847738c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22019: add section for definitive Model.objects documentation

[Django]

#22019: add section for definitive Model.objects documentation
-+-
 Reporter:  cjerdonek|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  models nlsprint14|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by gtvblame):

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


Comment:

 Take this ticket to work on during DjangoCon Europe 2014 sprint.

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

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

Re: [Django] #12233: Redirect logged in user

[Django]

#12233: Redirect logged in user
-+-
 Reporter:  dmathieu |Owner:
 Type:  New feature  |  aaronbassett
Component:  contrib.auth |   Status:  assigned
 Severity:  Normal   |  Version:
 Keywords:   |   Resolution:
  authentication,login   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by olethanh):

 * cc: olethanh (added)


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

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

Re: [Django] #22003: LiveServerTestCase with ATOMIC_REQUESTS leaves Postgres connections open after socket error

[Django]

#22003: LiveServerTestCase with ATOMIC_REQUESTS leaves Postgres connections open
after socket error
---+--
 Reporter:  garron |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:  worksforme
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by magopian):

 might be related to #22414 and #22420

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

Re: [Django] #22424: Default value for TextField

[Django]

#22424: Default value for TextField
-+--
 Reporter:  Nevsky   |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-1
 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 syphar):

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


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

Re: [Django] #16883: Importing models.py from not-installed app prevents any other app with that label from loading

[Django]

#16883: Importing models.py from not-installed app prevents any other app with 
that
label from loading
-+-
 Reporter:  carljm   |Owner:  nott
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by nott):

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


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

Re: [Django] #22414: Persistent connections not closed by LiveServerTestCase, preventing dropping test databases

[Django]

#22414: Persistent connections not closed by LiveServerTestCase, preventing
dropping test databases
---+
 Reporter:  Koterpillar|Owner:
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by magopian):

 * needs_better_patch:  0 => 1


Comment:

 This patch is still not working for me on an up to date master.

 On a side note, it might be related to #22420 and #22003.

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

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

Re: [Django] #22630: EmailField allows invalid text to be saved as long as an email address is inside the text

[Django]

#22630: EmailField allows invalid text to be saved as long as an email address 
is
inside the text
-+-
 Reporter:  joe@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:  email orm field  |  Unreviewed
  validators |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by joe@…):

 I am able to reproduce this by assigning a dict to the email. Also, please
 note this is a bug with the Django ORM and not (that I know of) an issue
 with the forms (though if they use the same validator this could possibly
 be an issue).

 https://gist.github.com/joestump/9b76fd94378c960ed7c3

 So the issue appears to be that there's no type checking combined with the
 blind split on the @ sign.

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

Re: [Django] #22639: Fix inconsistency with imports in documentation

[Django]

#22639: Fix inconsistency with imports in documentation
-+-
 Reporter:  niclas.ahden |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 I don't mind the current state of things. There was a couple of patches a
 while back that added a lot of imports, e.g.
 1fe587d80bfcf062a94252fb532c8ac035c833b9
 08b501e7d314e9c45dd51d3ba27b2ecb0287df3b
 1d543949d7acc93a172e8a2c9272d8b983a421ef.

 The first time a concept is introduced in a section, it probably makes
 sense to include all imports, but if the example is tweaked later, I don't
 think the imports need to be repeated.

 If there are spots that bother you right now, feel free to send a PR.
 Otherwise, I don't think we need to keep a ticket open for this.

 We'll never be able to make all code snippets safe to copy and paste
 because examples have example dependencies like `from myapp.models import
 Article`.

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

Re: [Django] #22634: Making Session model and SessionStore classes more easily extendable

[Django]

#22634: Making Session model and SessionStore classes more easily extendable
-+-
 Reporter:  sergeykolosov|Owner:
 Type:   |  sergeykolosov
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.sessions |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by sergeykolosov):

 * has_patch:  0 => 1


Comment:

 Pull request: ​https://github.com/django/django/pull/2667

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

Re: [Django] #6668: Optimise utils.text wrap

[Django]

#6668: Optimise utils.text wrap
-+-
 Reporter:  SmileyChris  |Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by giuliettamasina):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #6668: Optimise utils.text wrap

[Django]

#6668: Optimise utils.text wrap
-+-
 Reporter:  SmileyChris  |Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by giuliettamasina):

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


Comment:

 I've updated this patch to pass all tests, here's a new pull request:

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

 The fix was to wrap the `max_width =` lines in `min()` to make sure it
 never exceeds the given wrap width.

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

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

Re: [Django] #22266: CharField primary keys with underscores are (un)escaped differently in the admin pages

[Django]

#22266: CharField primary keys with underscores are (un)escaped differently in 
the
admin pages
+
 Reporter:  victor.varvariuc@…  |Owner:  nott
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  1.6
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Russell Keith-Magee ):

 In [changeset:"75d2da797e100442d3573dfa7ae490972cea32d8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="75d2da797e100442d3573dfa7ae490972cea32d8"
 [1.7.x] Fixed #22266 - quote PK before redirecting away from add_view
 (django.contrib.admin)

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

[django/django] 75d2da: [1.7.x] Fixed #22266 - quote PK before redirecting...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 75d2da797e100442d3573dfa7ae490972cea32d8
  
https://github.com/django/django/commit/75d2da797e100442d3573dfa7ae490972cea32d8
  Author: Stas Rudakou 
  Date:   2014-05-16 (Fri, 16 May 2014)

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

  Log Message:
  ---
  [1.7.x] Fixed #22266 - quote PK before redirecting away from add_view 
(django.contrib.admin)

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

Re: [Django] #20554: Directly creating model instances on ForeignKey field fails

[Django]

#20554: Directly creating model instances on ForeignKey field fails
-+-
 Reporter:  direx|Owner:  drtyrsa
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by drtyrsa):

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


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

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

Re: [Django] #20458: Add a "My Tickets" report to the Django Trac

[Django]

#20458: Add a "My Tickets" report to the Django Trac
--+
 Reporter:  giuliettamasina   |Owner:
 Type:  Cleanup/optimization  |   Status:  closed
Component:  *.djangoproject.com   |  Version:
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  1
--+
Changes (by giuliettamasina):

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


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

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

[django/django] ebd70d: Fixed #22266 - quote PK before redirecting away fr...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ebd70d4d00c252d5122c13906da5bddc8de0bce5
  
https://github.com/django/django/commit/ebd70d4d00c252d5122c13906da5bddc8de0bce5
  Author: Stas Rudakou 
  Date:   2014-05-16 (Fri, 16 May 2014)

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

  Log Message:
  ---
  Fixed #22266 - quote PK before redirecting away from add_view 
(django.contrib.admin)


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

Re: [Django] #22266: CharField primary keys with underscores are (un)escaped differently in the admin pages

[Django]

#22266: CharField primary keys with underscores are (un)escaped differently in 
the
admin pages
+
 Reporter:  victor.varvariuc@…  |Owner:  nott
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  1.6
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Russell Keith-Magee ):

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


Comment:

 In [changeset:"ebd70d4d00c252d5122c13906da5bddc8de0bce5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ebd70d4d00c252d5122c13906da5bddc8de0bce5"
 Fixed #22266 - quote PK before redirecting away from add_view
 (django.contrib.admin)
 }}}

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

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

Re: [Django] #12233: Redirect logged in user

[Django]

#12233: Redirect logged in user
-+-
 Reporter:  dmathieu |Owner:
 Type:  New feature  |  aaronbassett
Component:  contrib.auth |   Status:  assigned
 Severity:  Normal   |  Version:
 Keywords:   |   Resolution:
  authentication,login   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by olethanh):

 I have improved the branch a little bit and rebased it on top of master in
 https://github.com/olethanh/django/tree/ticket_12233
 I added a simple loop detection which will raise an Exception but it won't
 catch all cases and improved the docs

 Not sure what's the best way to handle this redirection problem either:

 * We could just do nothing and let the user browser  automatically detect
 it but then the admin won't know that something is wrong.
 * We cannot detect this at start time since there is no settings for the
 LOGIN_URL and a project can potentially have multiple login url.
 * We can raise an Exception if we detect it (what is currently done in my
 branch)
 * We can return a 500 if we detect it (what's was previously done in my
 branch)
 * But more importantly we don't really have a reliable way to detect it,
 my current patch won't catch redirection if they have GET parameters
 inside or if we redirect to another login url or if there is another
 redirection afterwards.

 Not sure how important this problem is since it is a corner case that will
 only happen if the settings are badly configured.

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

Re: [Django] #21461: Add pre_update and post_update signals

[Django]

#21461: Add pre_update and post_update signals
-+-
 Reporter:  loic84   |Owner:  loic84
 Type:  New feature  |   Status:  assigned
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|
-+-

Comment (by shai):

 While the idea in comment:11 is interesting, I think the current
 suggestion is lacking.

 First of all, returning values from signals breaks with well-established
 assumptions, and I wouldn't haste to change that. Further, the suggested
 code assumes without checking that the returned values can be used to
 update a dictionary, and worse: Collapses all returned values into one
 dictionary, allowing different signal handlers to step on each other's
 toes with no way to find out about it.

 I think that the general direction of letting the user specify which data
 is received has merit, but this should be implemented via the registration
 API -- that is, either defining different signals ('pre_update',
 'pre_update_with_qset', 'pre_update_with_pks') or specifying different
 senders (something along the lines of `@receiver(pre_update,
 sender=(MyModel, pre_update.WITH_QSET))`). Then, update can calculate the
 required data only if it is, in fact, 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/064.83a7313345dd176468babc59e0c15f6d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 220c09: [1.5.x] Fixed #22167 -- Improved documentation on ...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 220c09e97acb8ca4267a0b754256e522e008c2d8
  
https://github.com/django/django/commit/220c09e97acb8ca4267a0b754256e522e008c2d8
  Author: Moritz 
  Date:   2014-05-16 (Fri, 16 May 2014)

  Changed paths:
M docs/ref/templates/api.txt

  Log Message:
  ---
  [1.5.x] Fixed #22167 -- Improved documentation on context processors

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

Re: [Django] #22167: docs about order of template context processors unclear

[Django]

#22167: docs about order of template context processors unclear
--+
 Reporter:  anonymous |Owner:  erikr
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Erik Romijn ):

 In [changeset:"220c09e97acb8ca4267a0b754256e522e008c2d8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="220c09e97acb8ca4267a0b754256e522e008c2d8"
 [1.5.x] Fixed #22167 -- Improved documentation on context processors

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

[django/django] 20215f: [1.6.x] Fixed #22167 -- Improved documentation on ...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 20215f4cae4f69f2bcbc4bbdbcd84651bee64634
  
https://github.com/django/django/commit/20215f4cae4f69f2bcbc4bbdbcd84651bee64634
  Author: Moritz 
  Date:   2014-05-16 (Fri, 16 May 2014)

  Changed paths:
M docs/ref/templates/api.txt

  Log Message:
  ---
  [1.6.x] Fixed #22167 -- Improved documentation on context processors

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

Re: [Django] #22167: docs about order of template context processors unclear

[Django]

#22167: docs about order of template context processors unclear
--+
 Reporter:  anonymous |Owner:  erikr
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Erik Romijn ):

 In [changeset:"20215f4cae4f69f2bcbc4bbdbcd84651bee64634"]:
 {{{
 #!CommitTicketReference repository=""
 revision="20215f4cae4f69f2bcbc4bbdbcd84651bee64634"
 [1.6.x] Fixed #22167 -- Improved documentation on context processors

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

Re: [Django] #22167: docs about order of template context processors unclear

[Django]

#22167: docs about order of template context processors unclear
--+
 Reporter:  anonymous |Owner:  erikr
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Erik Romijn ):

 In [changeset:"bd45139d4e17304229da5464c907c614e64278d1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bd45139d4e17304229da5464c907c614e64278d1"
 [1.7.x] Fixed #22167 -- Improved documentation on context processors

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

[django/django] bd4513: [1.7.x] Fixed #22167 -- Improved documentation on ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: bd45139d4e17304229da5464c907c614e64278d1
  
https://github.com/django/django/commit/bd45139d4e17304229da5464c907c614e64278d1
  Author: Moritz 
  Date:   2014-05-16 (Fri, 16 May 2014)

  Changed paths:
M docs/ref/templates/api.txt

  Log Message:
  ---
  [1.7.x] Fixed #22167 -- Improved documentation on context processors

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

[django/django] e7ffba: Fixed #22167 -- Improved documentation on context ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e7ffba8f78849fbf60b98fb8d67ef4577b585e3b
  
https://github.com/django/django/commit/e7ffba8f78849fbf60b98fb8d67ef4577b585e3b
  Author: Moritz 
  Date:   2014-05-16 (Fri, 16 May 2014)

  Changed paths:
M docs/ref/templates/api.txt

  Log Message:
  ---
  Fixed #22167 -- Improved documentation on context processors

Clarified the explanation on the order in which user provided variables
to render_to_response, RequestContext and context processors are
loaded.


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

Re: [Django] #22167: docs about order of template context processors unclear

[Django]

#22167: docs about order of template context processors unclear
--+
 Reporter:  anonymous |Owner:  erikr
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Erik Romijn ):

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


Comment:

 In [changeset:"e7ffba8f78849fbf60b98fb8d67ef4577b585e3b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e7ffba8f78849fbf60b98fb8d67ef4577b585e3b"
 Fixed #22167 -- Improved documentation on context processors

 Clarified the explanation on the order in which user provided variables
 to render_to_response, RequestContext and context processors are
 loaded.
 }}}

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

Re: [Django] #22263: KeyError: 'to' in MigrationAutodetector with uncommon rel.to setup (django-taggit)

[Django]

#22263: KeyError: 'to' in MigrationAutodetector with uncommon rel.to setup 
(django-
taggit)
+
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by MarkusH):

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


Comment:

 This issue was django-taggit related and not a problem in Django itself.
 Has been fixed in https://github.com/alex/django-taggit/pull/207

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

Re: [Django] #22167: docs about order of template context processors unclear

[Django]

#22167: docs about order of template context processors unclear
--+
 Reporter:  anonymous |Owner:  erikr
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.5
 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 erikr):

 * owner:  tibidat => erikr


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

Re: [Django] #22266: CharField primary keys with underscores are (un)escaped differently in the admin pages

[Django]

#22266: CharField primary keys with underscores are (un)escaped differently in 
the
admin pages
+
 Reporter:  victor.varvariuc@…  |Owner:  nott
 Type:  Bug |   Status:  assigned
Component:  contrib.admin   |  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
+

Comment (by nott):

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

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

Re: [Django] #22550: QuerySet last() and reverse() confusing when used with ordered slices

[Django]

#22550: QuerySet last() and reverse() confusing when used with ordered slices
-+-
 Reporter:  jdufresne|Owner:  merll
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by merll):

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


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

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

[Django] #22640: Can create model instance with conflicting args and kwargs value for the same field

[Django]

#22640: Can create model instance with conflicting args and kwargs value for the
same field
--+
 Reporter:  zsoldosp  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Discovered while working on #18586

 To reproduce it, add the following test (it's using
 tests.basic.models.Article)
 {{{#!python
 def test_cannot_specify_same_field_with_args_and_kwargs_too(self):
 six.assertRaisesRegex(
 self,
 TypeError,
 "'foo' is an invalid keyword argument for this function",
 Article,
 None, # id
 'args based headline',
 headline='kwargs based headline',
 pub_date=datetime(2005, 7, 31),
 )
 }}}

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

Re: [Django] #22436: migrations fail on custom upload_to on ImageField

[Django]

#22436: migrations fail on custom upload_to on ImageField
-+-
 Reporter:  David Binetti|Owner:
     |  chriscauley
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MarkusH):

 For the why and how to prevent problems with custom fields, I want to
 point you to #21499

-- 
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/092.4135039af1072a7deac2faebf2b70bcf%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:  xelnor
 Type:  Bug  |   Status:  assigned
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 xelnor):

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


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

[Django] #22639: Fix inconsistency with imports in documentation

[Django]

#22639: Fix inconsistency with imports in documentation
--+
 Reporter:  niclas.ahden  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 We've noticed that imports are not always included in code snippets which
 means that snippets are not always safe to copy and paste. It's fine to
 not have them copy-paste safe, but it should be consistent.

 '''For example'''
 The tutorial includes imports in all of the snippets (eg. "from
 django.contrib import admin"). Except for at the very bottom where the
 imports are skipped.
 https://docs.djangoproject.com/en/1.6/intro/tutorial02/

 This section has two snippets: one with imports and one without.
 https://docs.djangoproject.com/en/dev/topics/forms/modelforms/#selecting-
 the-fields-to-use

 The imports for this snippet are quite far away in a previous section.
 https://docs.djangoproject.com/en/dev/topics/forms/modelforms
 /#considerations-regarding-model-s-error-messages

 TL;DR should all code snippets be safe to copy and paste?

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

Re: [Django] #22014: `prefetch_related` recursion protection does not cover all cases

[Django]

#22014: `prefetch_related` recursion protection does not cover all cases
---+--
 Reporter:  StillNewb  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  prefetch   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by bmispelon):

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


Comment:

 Hi,

 Correct me if I'm wrong, but from what I can tell, the test you provide
 doesn't demonstrate an infinite loop.

 There does appear to be some repeated queries but I'm not familiar enough
 with the ORM internals to say whether it's actually a bug or a performance
 issue that we could improve.


 I'll mark this ticket as "needs info". Can you reopen it with a testcase
 that shows the infinite recursion?

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

Re: [Django] #20488: Enhance the Storage class with new copy and move methods

[Django]

#20488: Enhance the Storage class with new copy and move methods
--+
 Reporter:  kux   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  File uploads/storage  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by anonymous):

 New PR: https://github.com/django/django/pull/2664

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

Re: [Django] #22436: migrations fail on custom upload_to on ImageField

[Django]

#22436: migrations fail on custom upload_to on ImageField
-+-
 Reporter:  David Binetti|Owner:
     |  chriscauley
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by chriscauley):

 Thank you for upping the severity. I don't understand why it should
 "represent the exact state the model has at a given time", and I can think
 of strong arguments as to why it shouldn't. Using django==1.3 and south I
 can create a model that uses a URLField. If I change the value of the
 verify_exists keyword argument, that does not require me to create a new
 migration file. If I go up to django==1.4 then suddenly the verify exists
 keyword argument is removed and I have to go through and delete it from
 every instance that uses it. No biggy though, just one line here and
 there. However, I don't have to go back and change my migrations because
 verify_exists has no impact on the database and therefore doesn't trigger
 a migration.

 Now imagine that migrations were built into django back in 1.3 and that
 they were made to "represent the exact state the model has at a given
 time". I create a URLField, make a migration. I decide I don't like
 verify_exists and set it to False, make another migration (not a huge
 deal, but pointless). Then I update to 1.4 and so I go through and remove
 verify_exists. A migration is now '''impossible''' because
 `models.URLField(verify_exists=False)` (which is the previous state of the
 model) is not valid django any more (and raises a TypeError as of
 django==1.5). In order to make my migrations work again I need to go back
 and remove every reference to verify_exists from every migration file. The
 migration where I went from verify_exists=True to False now does nothing!
 Then again the migration did nothing in the first place because
 verify_exists doesn't change the database.

 One of my django projects (an online news magazine) has 425 migrations.
 `grep URLField * -r|grep migrations/0| wc -l` shows that this represents
 6439 lines of code for the 50 URLFields in this project. That's insanity.
 That project might still be on 1.3 if upgrading it to 1.4 required
 modifying 6.5k lines of code.

 This is just one example but I can come up with plenty other like it. In
 every case we either have to support legacy code indefinitely (for example
 leave verify_exists as a do-nothing key word argument) or else modifying
 the Field's API would require going back and editing every existing
 migration file. Neither option is pleasant and either way '''none of this
 has any effect on the database'''. I think migrations should be minimal
 and independent of non-database code.

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

Re: [Django] #22167: docs about order of template context processors unclear

[Django]

#22167: docs about order of template context processors unclear
--+
 Reporter:  anonymous |Owner:  tibidat
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by tibidat):

 Pull request added: https://github.com/django/django/pull/2665

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

Re: [Django] #22424: Default value for TextField

[Django]

#22424: Default value for TextField
-+--
 Reporter:  Nevsky   |Owner:  syphar
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 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 syphar):

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


Comment:

 I'll have a look at it and verify the fix.

 (atm I get Nevsky's error when adding the column without the fix, with the
 fix I get another error. But checking it.

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

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

Re: [Django] #22310: Document exact usage of and consequences of rotating SECRET_KEY

[Django]

#22310: Document exact usage of and consequences of rotating SECRET_KEY
--+
 Reporter:  erikr |Owner:  erikr
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by erikr):

 * owner:  Zulu => erikr


Comment:

 I am currently working on this, but it'll have to wait on #22638.

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

[Django] #22638: Form wizard may raise unreasonable exceptions in case of SECRET_KEY change

[Django]

#22638: Form wizard may raise unreasonable exceptions in case of SECRET_KEY 
change
---+
 Reporter:  erikr  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.formtools  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Our form wizard has two storage options: sessions and cookies, with
 `SessionWizardView` and `CookieWizardView`. To prevent manipulation, the
 cookies storage uses the signed cookies from `django.core.signing`. This
 creates a signature based on the `SECRET_KEY`. If the secret key is
 changed, `request.get_signed_cookie` will raise an exception, in which
 case the storage will raise `WizardViewCookieModified`, a subclass of
 `SuspiciousOperation`.

 The cookie is loaded very early in the rendering of a the form wizard
 view. This means that if a user starts a form wizard, and the secret key
 is changed, any requests to the wizard will result in an exception and
 likely a 500 error. The user can only recover from this by deleting the
 cookie or restarting the browser (it seems to only persist in the current
 session).

 It may appear sensible to raise a `SuspiciousOperation` for a possible
 cookie manipulation, but we currently don't do this in any other place,
 like sessions. Currently, user may suddenly get 500 errors for no clear
 reason, and the developer of the project has no ability to help them.
 Leaving this as is may also discourage people from rotating their secret
 key when needed.

 I suggest that in case of an invalid wizard cookie, we simply ignore the
 value and thereby return the user to the first step.

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

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

Re: [Django] #22432: Switching model on an M2M field results in a broken db (no change to the automatic through table)

[Django]

#22432: Switching model on an M2M field results in a broken db (no change to the
automatic through table)
-+--
 Reporter:  melinath |Owner:  xelnor
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 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
-+--
Changes (by xelnor):

 * has_patch:  0 => 1


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

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