Re: [Django] #29403: Make PyLibMCCache backend handle TooBig exception from pylibmc

[Django]

#29403: Make PyLibMCCache backend handle TooBig exception from pylibmc
-+-
 Reporter:  SKisContent  |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  closed
Component:  Core (Cache system)  |  Version:  1.11
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  memcached, TooBig| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  assigned => closed
 * type:  Bug => Cleanup/optimization
 * resolution:   => needsinfo


Comment:

 Like [https://code.djangoproject.com/ticket/29403#comment:3 Flavio
 Curella] and
 [https://github.com/django/django/pull/9811#issuecomment-387895386 Ed
 Morley], I'm not convinced that we should catch this exception, it was
 shortly discussed in
 [https://code.djangoproject.com/ticket/19914#comment:4 #19914]. See also
 arguments in [https://code.djangoproject.com/ticket/28342#comment:8
 #28342] (this is not a duplicate but is related). The main question is:
 should we force consistency between these two backends? IMO it's better to
 respect their different policies of handling errors.

 I think we should go back to the DevelopersMailingList and reach a
 consensus to move it forward.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.bc9049a03b48df89dbe16cbbb717bdaf%40djangoproject.com.

Re: [Django] #31760: Incorrect translation of the words that contain ’ in their msgid

[Django]

#31760: Incorrect translation of the words that contain ’ in their msgid
---+--
 Reporter:  Norserium  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  3.0
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  locale | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by felixxm):

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


Comment:

 Duplicate of #31302.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.7a79e21ef2ab9727867a3fa3c068a3f3%40djangoproject.com.

Re: [Django] #30945: Plural equation changes for some languages are not documented in Django 2.2 release notes

[Django]

#30945: Plural equation changes for some languages are not documented in Django 
2.2
release notes
-+-
 Reporter:  אורי |Owner:  David
 Type:   |  Smith
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.2
 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 David Smith):

 [https://code.djangoproject.com/ticket/30945 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.a5e5aef9a9314f09ea0a764e16b3eb6f%40djangoproject.com.

Re: [Django] #30945: Plural equation changes for some languages are not documented in Django 2.2 release notes

[Django]

#30945: Plural equation changes for some languages are not documented in Django 
2.2
release notes
-+-
 Reporter:  אורי |Owner:  David
 Type:   |  Smith
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.2
 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 David Smith):

 * owner:  nobody => David Smith
 * status:  new => assigned
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.2c2142989c313933be76a159d51aea06%40djangoproject.com.

[Django] #31760: Incorrect translation of the words that contain ’ in their msgid

[Django]

#31760: Incorrect translation of the words that contain ’ in their msgid
-+
   Reporter:  Norserium  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  3.0
   Severity:  Normal |   Keywords:  locale
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+
 For example, in the source code msgid "Yes, I**’**m sure" is used, but in
 the most of locales another form of this msgid  is used ("Yes, I**'**m
 sure").

 `contrib\admin\locale\ru\LC_MESSAGES\django.po`
 {{{
 msgid "Yes, I'm sure"
 msgstr "Да, я уверен"
 }}}

 `contrib\admin\locale\be\LC_MESSAGES\django.po`
 {{{
 msgid "Yes, I’m sure"
 msgstr "Так, я ўпэўнены"
 }}}

 The locale files should be fixed to correspond the actual msgid that used
 in the source 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.b081c6bcf82009c841723faf7c004c12%40djangoproject.com.

Re: [Django] #31758: remove BytesToCharFieldConversionMixin

[Django]

#31758: remove BytesToCharFieldConversionMixin
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 GitHub ):

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


Comment:

 In [changeset:"37389ae99eb17ee8e2db39545d0e13f5ab8f006a" 37389ae9]:
 {{{
 #!CommitTicketReference repository=""
 revision="37389ae99eb17ee8e2db39545d0e13f5ab8f006a"
 Fixed #31758 -- Removed unneeded BytesToCharFieldConversionMixin.

 Bug was fixed in mysqlclient 1.3.13.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.685f2f53053726c149750692b7fc98f9%40djangoproject.com.

Re: [Django] #6903: Go back to old change_list view after hitting save

[Django]

#6903: Go back to old change_list view after hitting save
-+-
 Reporter:   |Owner:  Tomek
 |  Paczkowski
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"9e4f55757dcdb171c515d65a4d8e9ff5dc33a8f8" 9e4f5575]:
 {{{
 #!CommitTicketReference repository=""
 revision="9e4f55757dcdb171c515d65a4d8e9ff5dc33a8f8"
 [3.0.x] Refs #6903 -- Adjusted ModelAdmin.preserve_filters docs.

 Backport of b142bd4a1b83b77c5c81a8cf5a80a63608f96ad4 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.9a8445914d42b9994d490e103bf2b796%40djangoproject.com.

Re: [Django] #6903: Go back to old change_list view after hitting save

[Django]

#6903: Go back to old change_list view after hitting save
-+-
 Reporter:   |Owner:  Tomek
 |  Paczkowski
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"268ba2db8e0b94359f19c3f387a2af701154" 268ba2d]:
 {{{
 #!CommitTicketReference repository=""
 revision="268ba2db8e0b94359f19c3f387a2af701154"
 [3.1.x] Refs #6903 -- Adjusted ModelAdmin.preserve_filters docs.

 Backport of b142bd4a1b83b77c5c81a8cf5a80a63608f96ad4 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.b537be49112a3f7c4f1bc0751aa78158%40djangoproject.com.

Re: [Django] #6903: Go back to old change_list view after hitting save

[Django]

#6903: Go back to old change_list view after hitting save
-+-
 Reporter:   |Owner:  Tomek
 |  Paczkowski
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b142bd4a1b83b77c5c81a8cf5a80a63608f96ad4" b142bd4a]:
 {{{
 #!CommitTicketReference repository=""
 revision="b142bd4a1b83b77c5c81a8cf5a80a63608f96ad4"
 Refs #6903 -- Adjusted ModelAdmin.preserve_filters docs.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.5a005924dedf16d2fcc7cef5c6a254f4%40djangoproject.com.

[Django] #31759: Why do instance hints in ForwardManyToOneDescriptor use the related object?

[Django]

#31759: Why do instance hints in ForwardManyToOneDescriptor use the related 
object?
-+-
   Reporter:  Daniel |  Owner:  nobody
  Miller |
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  3.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Why do the `instance` hints in `ForwardManyToOneDescriptor` use the
 related object rather than the instance of the class being routed?

 
[https://github.com/django/django/blob/d36413a2eb5678dda35559a48769703acd784898/django/db/models/fields/related_descriptors.py#L223-L226
 django/db/models/fields/related_descriptors.py:223]
 {{{
 if instance._state.db is None:
 instance._state.db = router.db_for_write(instance.__class__,
 instance=value)
 if value._state.db is None:
 value._state.db = router.db_for_write(value.__class__,
 instance=instance)
 }}}

 I would expect that to read like so
 {{{
 if instance._state.db is None:
 instance._state.db = router.db_for_write(instance.__class__,
 instance=instance)
 if value._state.db is None:
 value._state.db = router.db_for_write(value.__class__, instance=value)
 }}}

 It looks like it may be a historical artifact from
 
[https://github.com/django/django/blob/acc095c333213eb1d978866ae5852cefe00ce4ef/django/db/models/fields/related.py#L285-L288
 long ago], which was
 
[https://github.com/django/django/commit/1b3dc8ad9a28486542f766ff93318aa6b4f5999b
 later converted] to what we see today.

 The [https://docs.djangoproject.com/en/3.0/topics/db/multi-db/#topics-db-
 multi-db-hints documentation on multi-db hints] is vague, it says the
 instance is "an object instance that is related to the read or write
 operation that is underway." While this is technically not inaccurate, it
 seems non-intuitive to pass a related object rather than the object being
 routed.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.28835a349789d9091408fa5cf7f40431%40djangoproject.com.

Re: [Django] #31758: remove BytesToCharFieldConversionMixin

[Django]

#31758: remove BytesToCharFieldConversionMixin
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Simon Charette):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.fb21eb9a223cebc70403b6f984910495%40djangoproject.com.

Re: [Django] #31758: remove BytesToCharFieldConversionMixin

[Django]

#31758: remove BytesToCharFieldConversionMixin
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 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 Sergey Fedoseev):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/13138 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.61af43de1d77fa7ab4d0409489e709a6%40djangoproject.com.

Re: [Django] #31758: remove BytesToCharFieldConversionMixin

[Django]

#31758: remove BytesToCharFieldConversionMixin
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Sergey Fedoseev):

 * owner:  nobody => Sergey Fedoseev
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.9e284a158dd06bf9172d0734caf9fb65%40djangoproject.com.

[Django] #31758: remove BytesToCharFieldConversionMixin

[Django]

#31758: remove BytesToCharFieldConversionMixin
-+-
   Reporter:  Sergey |  Owner:  nobody
  Fedoseev   |
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 `BytesToCharFieldConversionMixin` was added in
 6141c752fe7091d2197f5ac061300a9e0a36b09b in order to fix #29251. It looks
 like the issue was caused by bug in mysqlclient and was fixed in
 [https://github.com/PyMySQL/mysqlclient-
 python/commit/73ccdcdddf2dd8e193e8af4a2362727c601b40ac 1.3.13]. Since we
 support mysqlclient >= 1.4, `BytesToCharFieldConversionMixin` could be
 removed.

 This makes `Repeat` faster. Benchmarked on postgres with 1 rows.
 Before:

 {{{
 In [8]: %timeit
 list(TestModel.objects.values_list(models.functions.Repeat(models.Value('a'),
 2)))
 18.1 ms ± 170 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)
 }}}

 After:
 {{{
 In [3]: %timeit
 list(TestModel.objects.values_list(models.functions.Repeat(models.Value('a'),
 2)))
 3.18 ms ± 28.5 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.56599dff142956ed622d55eb7a81b3e5%40djangoproject.com.

Re: [Django] #31757: Adjust default SECRET_KEY to use `dj::insecure` prefix and add matching deployment system check.

[Django]

#31757: Adjust default SECRET_KEY to use `dj::insecure` prefix and add matching
deployment system check.
--+
 Reporter:  Carlton Gibson|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (System checks)  |  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 René Fleschenberg):

 * cc: René Fleschenberg (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.0ff99d2230e08fff8452721bb9f19968%40djangoproject.com.

Re: [Django] #31757: Adjust default SECRET_KEY to use `dj::insecure` prefix and add matching deployment system check.

[Django]

#31757: Adjust default SECRET_KEY to use `dj::insecure` prefix and add matching
deployment system check.
--+
 Reporter:  Carlton Gibson|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (System checks)  |  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
--+

Comment (by René Fleschenberg):

 Shai Berger suggested an alternative approach: Marking the string as
 insecure by making it an instance of a custom str subclass
 (https://groups.google.com/d/msg/django-developers/CIPgeTetYpk/3a0lkAu-
 BgAJ). I am not sure which of the two approaches we prefer.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.e76e07b23b9095c0c8bf9a8b097b12e5%40djangoproject.com.

Re: [Django] #26761: Add 'help_text' property to methods in ModelAdmin.list_display

[Django]

#26761: Add 'help_text' property to methods in ModelAdmin.list_display
---+--
 Reporter:  Derek Hohls|Owner:  Hasan Ramezani
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 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 Carlton Gibson):

 * cc: Carlton Gibson (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.7104f98c72686883d6e619e83cd35ebe%40djangoproject.com.

Re: [Django] #28342: Make PyLibMCCache backend catch exceptions when memcached server is down

[Django]

#28342: Make PyLibMCCache backend catch exceptions when memcached server is down
-+-
 Reporter:  Julian Andrews   |Owner:  Joel
 Type:   |  Andrews
  Cleanup/optimization   |   Status:  closed
Component:  Core (Cache system)  |  Version:  3.0
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  memcached cache  | Triage Stage:  Accepted
  pylibmc|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

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


Comment:

 I'm not sure about catching all kind of exceptions or even
 `pylibmc.ConnectionError` or `pylibmc.ServerDown`. Consistency between
 different backends for the same serves is not a strong argument for me.
 `pylibmc` policy is strongly expressed in the
 [http://sendapatch.se/projects/pylibmc/misc.html#exceptions docs]. Folks
 using different libraries can expect different behaviors, and you can
 always change your stack.

 I think we should go back to the DevelopersMailingList and reach a strong
 consensus to move it forward.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.740c94a8534e7f71a21cb02e722d6043%40djangoproject.com.

Re: [Django] #31757: Adjust default SECRET_KEY to use `dj::insecure` prefix and add matching deployment system check.

[Django]

#31757: Adjust default SECRET_KEY to use `dj::insecure` prefix and add matching
deployment system check.
--+
 Reporter:  Carlton Gibson|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (System checks)  |  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 felixxm):

 * version:  3.0 => 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.23d57aedb013b2814b0ab2c7cea9e2c3%40djangoproject.com.

Re: [Django] #24141: contains() method for QuerySets

[Django]

#24141: contains() method for QuerySets
-+-
 Reporter:  gormster |Owner:  Johan
 |  Schiff
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * owner:  (none) => Johan Schiff
 * needs_better_patch:  0 => 1
 * status:  new => assigned
 * needs_docs:  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.0f7c6350758a9aa096922a30b19c44c4%40djangoproject.com.

Re: [Django] #29403: Make PyLibMCCache backend handle TooBig exception from pylibmc

[Django]

#29403: Make PyLibMCCache backend handle TooBig exception from pylibmc
-+-
 Reporter:  SKisContent  |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  memcached, TooBig| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Hasan Ramezani):

 * owner:  nobody => Hasan Ramezani
 * status:  new => assigned
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.8d6f777278a6766483014307ddcf13e7%40djangoproject.com.

[Django] #31757: Adjust default SECRET_KEY to use `dj::insecure` prefix and add matching deployment system check.

[Django]

#31757: Adjust default SECRET_KEY to use `dj::insecure` prefix and add matching
deployment system check.
+
   Reporter:  Carlton Gibson|  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  Core (System checks)  |Version:  3.0
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 [https://groups.google.com/d/topic/django-
 developers/CIPgeTetYpk/discussion Recent thread on the mailing list about
 making the default settings more 12 factor friendly]. (Related to similar
 discussions in say #20081.)

 Conclusion there was that environment variables are only one way to go.
 (...)

 In the discussion it came up that we could prefix the generated SECRET_KEY
 with say, `dj::insecure` and then add a deployment system check to ensure
 that wasn't used in production. (Paraphrasing various points: might not be
 100% robust but would capture most cases.)

 So:

 * Prefix secret key in project template.
 * Add system check to ensure secret key does not have prefix.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/056.097fcd49381c7a656d01fda837dc522f%40djangoproject.com.

Re: [Django] #20081: Minimize the risk of SECRET_KEY leaks

[Django]

#20081: Minimize the risk of SECRET_KEY leaks
--+-
 Reporter:  Jacob |Owner:  aj7may
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  needsinfo
 Keywords:  nlsprint14| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by Carlton Gibson):

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


Comment:

 So [https://groups.google.com/d/topic/django-
 developers/CIPgeTetYpk/discussion the idea of making the settings file
 more "12 factor friendly" came up again on the mailing list] — a quite
 long thread raising many different points, and approaches.

 One key point was, Paul's one from above, that environment variables only
 suit a subset of projects. Then there was multiple settings files, and
 secrets files, and better deployment docs and...

 I have the impression that this ticket was based on a quite specific idea
 from a conversion but it's grown quite amorphous, such that I'm not sure
 any longer it's actionable. I'm going to close it as needsinfo. Can I ask
 that if there's a concrete proposal based on it, that we start a fresh
 ticket, perhaps referencing this one if necessary.
 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.ba6fe6311e96e854fb22445f248a6fc4%40djangoproject.com.