Re: [Django] #24866: Add CURRENT_TIMESTAMP function to db.functions

[Django]

#24866: Add CURRENT_TIMESTAMP function to db.functions
-+-
 Reporter:  funkybob |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by jarshwah):

 Below is probably the way to go. We haven't done 0-arity Func expressions
 before though, so there may be some hidden traps waiting. It'd go in
 django.db.models.functions.py

 {{{
 class Now(Func):
 template = 'CURRENT_TIMESTAMP()'
 def __init__(self, output_field=DateTimeField(), **extra):
 super(Func, self).__init__(output_field=output_field, **extra)
 }}}

 This should (famous last words) be a relatively straight forward patch.
 I'd encourage someone that wants to get some basic familiarity with the
 ORM and expressions in general to have a go at implementing.

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

Re: [Django] #24866: Add CURRENT_TIMESTAMP function to db.functions

[Django]

#24866: Add CURRENT_TIMESTAMP function to db.functions
-+-
 Reporter:  funkybob |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by jarshwah):

 * version:  1.8 => master
 * stage:  Unreviewed => Accepted


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

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

[Django] #24866: Add CURRENT_TIMESTAMP function to db.functions

[Django]

#24866: Add CURRENT_TIMESTAMP function to db.functions
-+-
   Reporter:  funkybob   |  Owner:  nobody
   Type:  New| Status:  new
  feature|
  Component:  Database   |Version:  1.8
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  1  |Needs tests:  1
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 00:21 <+jarshwah> or.. Func(template='NOW()',
 output_field=DateTimeFIeld()) would work too


 Postgres, MySQL, SQLite and MS SQL support this function, and it would be
 very handy.

 In the past I've implemented it using an ExpressionNode, but with the new
 functions module, it could be simpler and more useful.

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

Re: [Django] #24699: Add Avg('DurationField') support on Oracle

[Django]

#24699: Add Avg('DurationField') support on Oracle
-+-
 Reporter:  timgraham|Owner:  jarshwah
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jarshwah):

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


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

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

Re: [Django] #24860: Migrations leak stale RelatedManager related_model definitions

[Django]

#24860: Migrations leak stale RelatedManager related_model definitions
-+-
 Reporter:  ecederstrand |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  migration,   | Triage Stage:
  RelatedManager |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * Attachment "24860-test.diff" 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/070.e4e73c4c1756530b84e6bfa1490d672a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24860: Migrations leak stale RelatedManager related_model definitions

[Django]

#24860: Migrations leak stale RelatedManager related_model definitions
-+-
 Reporter:  ecederstrand |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  migration,   | Triage Stage:
  RelatedManager |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I tried to reproduce with a test based on the steps you outlined, but
 didn't have any luck (also tried similar steps in a sample project). Could
 you try tweaking the test until it fails or submit a sample project that
 reproduces the crash?

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

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

[Django]

#24817: Renaming a model field that has null=False makes it nullable in MySQL
-+-
 Reporter:  murfi|Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 Claude, look good to you?

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

Re: [Django] #24853: FK value not inserted in database in data migration

[Django]

#24853: FK value not inserted in database in data migration
-+-
 Reporter:  rakanalh |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  database,| Triage Stage:
  migrations |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


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

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

Re: [Django] #24853: FK value not inserted in database in data migration

[Django]

#24853: FK value not inserted in database in data migration
-+-
 Reporter:  rakanalh |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database,| Triage Stage:
  migrations |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"df6a4cac52b58e471168d0a80e5d1900126b7154" df6a4cac]:
 {{{
 #!CommitTicketReference repository=""
 revision="df6a4cac52b58e471168d0a80e5d1900126b7154"
 [1.8.x] Refs #24853 -- Documented a limitation of RunPython and unmigrated
 apps.
 }}}

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

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

Re: [Django] #24858: Add support for get_foo_display() with ArrayField (was: get_foo_display with the ArrayField)

[Django]

#24858: Add support for get_foo_display() with ArrayField
--+
 Reporter:  MounirMesselmeni  |Owner:
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  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 timgraham):

 * type:  Uncategorized => New feature
 * version:  1.8 => master
 * stage:  Unreviewed => Accepted


Comment:

 Not sure about feasibility, but the request makes sense. If infeasible, it
 would be nice if ArrayField didn't create the method which doesn'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/074.a661278c473c10c4a3dcdf0203a9c48a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24859: UUIDField does not validate query value (was: UUIDField does not Properly Raise TyperError)

[Django]

#24859: UUIDField does not validate query value
-+-
 Reporter:  cancan101|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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
-+-

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

Re: [Django] #24859: UUIDField does not Properly Raise TyperError

[Django]

#24859: UUIDField does not Properly Raise TyperError
-+-
 Reporter:  cancan101|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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 timgraham):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Database layer (models, ORM)
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Accepting in a similar vein to #24319. Here's a test that can be used to
 reproduce the issue:
 {{{
 #!diff
 diff --git a/tests/model_fields/test_uuid.py
 b/tests/model_fields/test_uuid.py
 index 21c2869..95d47b5 100644
 --- a/tests/model_fields/test_uuid.py
 +++ b/tests/model_fields/test_uuid.py
 @@ -37,6 +37,9 @@ class TestSaveLoad(TestCase):
  loaded = NullableUUIDModel.objects.get()
  self.assertEqual(loaded.field, None)

 +def test_pk_validated(self):
 +PrimaryKeyUUIDModel.objects.get(pk={})
 +
  def test_wrong_value(self):
  self.assertRaisesMessage(
  ValueError, 'badly formed hexadecimal UUID string',
 }}}

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

Re: [Django] #24865: Add a feature to programmatically remove stale content types (was: Adding a feature to programmatically remove stale content types)

[Django]

#24865: Add a feature to programmatically remove stale content types
--+
 Reporter:  Protosac  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  stale contenttypes| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * component:  Uncategorized => contrib.contenttypes
 * needs_tests:   => 1
 * version:  1.7 => master
 * needs_docs:   => 1
 * stage:  Unreviewed => Accepted


Comment:

 Could you please send a pull request with tests and documentation? You may
 find the [https://docs.djangoproject.com/en/dev/internals/contributing
 /writing-code/submitting-patches/#patch-review-checklist patch review
 checklist] helpful.

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

[Django] #24865: Adding a feature to programmatically remove stale content types

[Django]

#24865: Adding a feature to programmatically remove stale content types
---+
 Reporter:  Protosac   |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.7
 Severity:  Normal |   Keywords:  stale contenttypes
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 This patch creates a new method `remove_contenttypes` that, when called
 from a migration, will programmatically remove the stale content type.

 Diff:
 https://github.com/django/django/compare/master...Protosac:removalUtility

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

Re: [Django] #24851: Regression in reverse one-to-one field in list_display

[Django]

#24851: Regression in reverse one-to-one field in list_display
-+-
 Reporter:  jerivas  |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.8
 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 timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/4717 PR]

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

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

Re: [Django] #24851: Regression in reverse one-to-one field in list_display

[Django]

#24851: Regression in reverse one-to-one field in list_display
-+-
 Reporter:  jerivas  |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.8
 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 timgraham):

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


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

Re: [Django] #24847: Items set on a RequestContext after creation get lost

[Django]

#24847: Items set on a RequestContext after creation get lost
-+
 Reporter:  pmdhazy  |Owner:  pwmarcz
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Tim Graham ):

 In [changeset:"7ee6043dba983bd30bdb880a216cb573d76c7fc5" 7ee6043]:
 {{{
 #!CommitTicketReference repository=""
 revision="7ee6043dba983bd30bdb880a216cb573d76c7fc5"
 Fixed #24847 -- Prevented items set on a RequestContext from being lost.

 Backport of 300e8baf9429dbf1c5dff478558d793638dc2f54 from master
 }}}

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

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

Re: [Django] #24847: Items set on a RequestContext after creation get lost

[Django]

#24847: Items set on a RequestContext after creation get lost
-+
 Reporter:  pmdhazy  |Owner:  pwmarcz
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"300e8baf9429dbf1c5dff478558d793638dc2f54" 300e8baf]:
 {{{
 #!CommitTicketReference repository=""
 revision="300e8baf9429dbf1c5dff478558d793638dc2f54"
 Fixed #24847 -- Prevented items set on a RequestContext from being lost.
 }}}

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

Re: [Django] #24836: force_text doesn't force SimpleLazyObject into a string

[Django]

#24836: force_text doesn't force SimpleLazyObject into a string
-+-
 Reporter:  riklaunim|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  1.8
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"70be31bba7f8658f17235e33862319780c3dfad1" 70be31bb]:
 {{{
 #!CommitTicketReference repository=""
 revision="70be31bba7f8658f17235e33862319780c3dfad1"
 Fixed #24836 -- Made force_text() resolve lazy objects.
 }}}

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

Re: [Django] #12091: Support for WSGI applications within Django (was: [PATCH] Support for WSGI applications within Django)

[Django]

#12091: Support for WSGI applications within Django
---+
 Reporter:  Gustavo|Owner:  Gustavo
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  WSGI   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

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

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

Re: [Django] #24864: Django will not listen to same port on IPv4 and IPv6 at the same time

[Django]

#24864: Django will not listen to same port on IPv4 and IPv6 at the same time
--+--
 Reporter:  erikano   |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  Version:  1.8
 Severity:  Normal|   Resolution:  wontfix
 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 timgraham):

 * component:  Uncategorized => Core (Other)
 * resolution:   => wontfix
 * status:  new => closed
 * type:  Uncategorized => New feature


Comment:

 I think integrating with a more fully featured web server is a better long
 term solution than trying to enhance the built-in webserver (#21978). This
 is consistent with the decision about [https://groups.google.com/d/topic
 /django-developers/PgBcSEiUdw0/discussion whether or not to add SSL
 support] to runserver.

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

Re: [Django] #21978: Add optional gunicorn support to runserver

[Django]

#21978: Add optional gunicorn support to runserver
-+-
 Reporter:  timo |Owner:
 |  berkerpeksag
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 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 timgraham):

 See also a [https://groups.google.com/d/topic/django-
 developers/PgBcSEiUdw0/discussion request on django-developers] to add SSL
 support to runserver. It discusses some alternatives to gunicorn.

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

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

Re: [Django] #24836: force_text doesn't force SimpleLazyObject into a string

[Django]

#24836: force_text doesn't force SimpleLazyObject into a string
-+-
 Reporter:  riklaunim|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"b16f84f15b1344d2a3df8149565cfc8de803eb77" b16f84f1]:
 {{{
 #!CommitTicketReference repository=""
 revision="b16f84f15b1344d2a3df8149565cfc8de803eb77"
 [1.8.x] Refs #24836 -- Reverted "Simplified the lazy CSRF token
 implementation in csrf context processor."

 This reverts commit 8099d33b6553c9ee7de779ae9d191a1bf22adbda as it caused
 a regression that cannot be solved without changing force_text() which has
 a small risk of introducing regressions. This change will remain in master
 along with an update to force_text().
 }}}

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

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

Re: [Django] #21231: Limiting the number of variables and files that a POST request can contain

[Django]

#21231: Limiting the number of variables and files that a POST request can 
contain
---+
 Reporter:  epandurski@…   |Owner:  timo
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  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 edevil):

 Any comments?

 Something I should improve?

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

Re: [Django] #17914: reverse() does not support namespaced view references

[Django]

#17914: reverse() does not support namespaced view references
-+-
 Reporter:  Bradley Ayers|Owner:  nobody
    |
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  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 apollo13):

 Replying to [comment:15 guettli]:
 > For me the view-name is redundant. We try to avoid it. Reversing by
 function reference works fine (except this bug). Jumping through the code
 with an IDE is much more fun if you use function references.

 If I remember correctly we've been over the redundancy point on the ML
 already, you can always just write your own url function which sets the
 path of the function as name, not really redundant imo. Also reversing by
 function reference is something which is ugly in templates etc imo… And
 redundant is relative anyways, "app:view_name" is imo way nicer than
 "app.views.view_name" -- especially if you have nested imports.

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

Re: [Django] #17914: reverse() does not support namespaced view references

[Django]

#17914: reverse() does not support namespaced view references
-+-
 Reporter:  Bradley Ayers|Owner:  nobody
    |
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  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 guettli):

 Replying to [comment:13 apollo13]:
 > Can someone present a usecase for using function references in reverse?
 IMO this should just get closed as wontfix and names should be used
 throughout instead.

 For me the view-name is redundant. We try to avoid it. Reversing by
 function reference works fine (except this bug). Jumping through the code
 with an IDE is much more fun if you use function references.

 It would be nice if this could be solved. For our team this means: don't
 use namespaced URLs :-(

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

Re: [Django] #24864: Django will not listen to same port on IPv4 and IPv6 at the same time

[Django]

#24864: Django will not listen to same port on IPv4 and IPv6 at the same time
---+--
 Reporter:  erikano|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by erikano):

 @timgraham: For consistency between dev and prod.

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

Re: [Django] #24616: date_hierarchy with USE_TZ=True won't work with Amazon RDS

[Django]

#24616: date_hierarchy with USE_TZ=True won't work with Amazon RDS
-+-
 Reporter:  iiilx|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Accepted
  pytz,mysql_tzinfo_to_sql,USE_TZ|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Closing as "won't fix" given Adam's comment. Feel free to reopen if you
 can provide more details to indicate that he's incorrect.

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

Re: [Django] #24864: Django will not listen to same port on IPv4 and IPv6 at the same time

[Django]

#24864: Django will not listen to same port on IPv4 and IPv6 at the same time
---+--
 Reporter:  erikano|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 What's your use case for development such that you need to listen to both
 protocols?

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

[Django] #24864: Django will not listen to same port on IPv4 and IPv6 at the same time

[Django]

#24864: Django will not listen to same port on IPv4 and IPv6 at the same time
---+
 Reporter:  erikano|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 By itself, `python3 manage.py runserver 0.0.0.0:8000` works.

 By itself, `python3 manage.py runserver [::]:8000` works.

 But if I try first `python3 manage.py runserver 0.0.0.0:8000` and then
 `python3 manage.py runserver[::]:8000`, I am told, incorrectly, by the
 second process that:

 Error: That port is already in use.

 Same goes if I run `python3 manage.py runserver [::]:8000` first followed
 by `python3 manage.py runserver 0.0.0.0:8000`; the first process runs but
 the second process will report:

 Error: That port is already in use.

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

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

Re: [Django] #24616: date_hierarchy with USE_TZ=True won't work with Amazon RDS

[Django]

#24616: date_hierarchy with USE_TZ=True won't work with Amazon RDS
-+-
 Reporter:  iiilx|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  pytz,mysql_tzinfo_to_sql,USE_TZ|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by adamchainz):

 I've been running Django 1.6+ fine on RDS MySQL (5.5) for over a year and
 a half, in two separate deployments. The timezone tables are preloaded for
 you, iirc. If you log in with your master user and run {{{SHOW TABLES IN
 `mysql`;}}} you should see them. You may need to run the following grants
 to your application's username to give it access to read the data:

 {{{
 GRANT SELECT ON `mysql`.`time_zone` TO 'application'@'%';
 GRANT SELECT ON `mysql`.`time_zone_leap_second` TO 'application'@'%';
 GRANT SELECT ON `mysql`.`time_zone_name` TO 'application'@'%';
 GRANT SELECT ON `mysql`.`time_zone_transition` TO 'application'@'%';
 GRANT SELECT ON `mysql`.`time_zone_transition_type` TO 'application'@'%';
 }}}

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

[Django] #24863: Make `django.db.models.Manager.from_queryset` copy over properties and not just methods

[Django]

#24863: Make `django.db.models.Manager.from_queryset` copy over properties and 
not
just methods
--+
 Reporter:  coolRR|  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 When I define a `QuerySet` subclass, I like defining not only methods but
 properties on it.

 The function `django.db.models.Manager.from_queryset` was introduced so we
 could succinctly create a `Manager` subclass that gets the same
 functionality that we defined on our `QuerySet` subclass. It copies over
 all the methods defind in the `QuerySet` class to the `Manager` class. But
 it doesn't copy properties, so they remain inaccessible from the `Manager`
 class.

 I want `django.db.models.Manager.from_queryset` to copy over the
 properties as well.

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

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

Re: [Django] #24858: get_foo_display with the ArrayField

[Django]

#24858: get_foo_display with the ArrayField
--+--
 Reporter:  MounirMesselmeni  |Owner:
 Type:  Uncategorized |   Status:  new
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Description changed by MounirMesselmeni:

Old description:

> I think using ArrayField as a many choices field would be awesome.
> Passing choices to ArrayField works fine with MultipleChoiceField on the
> form.
> But calling get_foo_display return a TypeError: unhashable type: 'list',
> maybe this method need to check if the field is an ArrayField it can
> return a string representation of the choices separated by comma.
>

> {{{#!python
> class Example(models.Model):
> CHOICES = (
> (1, 'value1'),
> (2, 'value2'),
> (3, 'value3'),
> )
>
> multi_choices_array = ArrayField(
> base_field=models.IntegerField(),
> choices=CHOICES,
> )
>
> example = Example.objects.create(multi_choices_array= [1, 2])
> example.get_multi_choices_array_display()
> # Will raise a Type Error exception
>
> }}}

New description:

 I think using ArrayField as a many choices field would be awesome.
 Passing choices to ArrayField works fine with MultipleChoiceField on the
 form.
 But calling get_foo_display return a TypeError: unhashable type: 'list',
 maybe this method need to check if the field is an ArrayField it can
 return a string representation of the choices separated by comma.


 {{{#!python
 class Example(models.Model):
 CHOICES = (
 (1, 'value1'),
 (2, 'value2'),
 (3, 'value3'),
 )

 multi_choices_array = ArrayField(
 base_field=models.IntegerField(),
 choices=CHOICES,
 )

 # Adding this method will show the values
 def multi_choices_array_display(self):
 result = ''
 choices = dict(self.CHOICES)
 for index, value in enumerate(self.multi_choices_array):
 result += "{0}".format(choices[value])
 if not index == len(self.multi_choices_array) - 1:
 result += ', '
 return result

 example = Example.objects.create(multi_choices_array= [1, 2])
 example.get_multi_choices_array_display()
 # Will raise a Type Error exception
 example.multi_choices_array_display()
 # Will print 'value1, value2'

 }}}

--

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

Re: [Django] #24858: get_foo_display with the ArrayField

[Django]

#24858: get_foo_display with the ArrayField
--+--
 Reporter:  MounirMesselmeni  |Owner:
 Type:  Uncategorized |   Status:  new
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Description changed by MounirMesselmeni:

Old description:

> I think using ArrayField as a many choices field would be awesome.
> Passing choices to ArrayField works fine with MultipleChoiceField on the
> form.
> But calling get_foo_display return a TypeError: unhashable type: 'list',
> maybe this method need to check if the field is an ArrayField it can
> return a string representation of the choices separated by comma.

New description:

 I think using ArrayField as a many choices field would be awesome.
 Passing choices to ArrayField works fine with MultipleChoiceField on the
 form.
 But calling get_foo_display return a TypeError: unhashable type: 'list',
 maybe this method need to check if the field is an ArrayField it can
 return a string representation of the choices separated by comma.


 {{{#!python
 class Example(models.Model):
 CHOICES = (
 (1, 'value1'),
 (2, 'value2'),
 (3, 'value3'),
 )

 multi_choices_array = ArrayField(
 base_field=models.IntegerField(),
 choices=CHOICES,
 )

 example = Example.objects.create(multi_choices_array= [1, 2])
 example.get_multi_choices_array_display()
 # Will raise a Type Error exception

 }}}

--

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

Re: [Django] #24862: Patch for GeoDjango to improve error message if database connection is bad

[Django]

#24862: Patch for GeoDjango to improve error message if database connection is 
bad
-+-
 Reporter:  brycenesbitt |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  PostGIS, GeoDjango,  | Triage Stage:  Accepted
  GIS, Usability |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by claudep):

 * needs_better_patch:  0 => 1
 * version:  1.8 => master
 * stage:  Unreviewed => Accepted


Comment:

 Good suggestion. Could you attach a patch against master, either as a
 Github pull request, or as a `git diff` output?

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

Re: [Django] #24836: force_text doesn't force SimpleLazyObject into a string

[Django]

#24836: force_text doesn't force SimpleLazyObject into a string
-+-
 Reporter:  riklaunim|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * stage:  Accepted => Ready for checkin


Comment:

 I'm a bit scared by introducing such a low-level change in a stable
 release. Another scenario would be to revert Alex change in 1.8 and
 introduce this in master only.

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

Re: [Django] #24675: Skip "SET SQL_AUTO_IS_NULL = 0" on versions of MySQL that don't need it

[Django]

#24675: Skip "SET SQL_AUTO_IS_NULL = 0" on versions of MySQL that don't need it
-+-
 Reporter:  ssjunior |Owner:  ssjunior
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 Something like: take a connection object, close it, reopen it and check
 that no `SQL_AUTO_IS_NULL` query is done.

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