date:20170627

Re: [Django] #28297: Same queryset result in two different queries on ORM

2017-06-27 Thread Django

#28297: Same queryset result in two different queries on ORM
-+-
 Reporter:  Marcus Renno |Owner:  Marcus
 |  Renno
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  join, annotation, F  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by holvianssi):

 To me it seems that pre
 
https://code.djangoproject.com/changeset/ab89414f40db1598364a7fe4cfac1766cacd2668
 we always used the *first* join, not the last join possible in join(). I
 believe this has been that way for a long time, so changing that should be
 considered carefully.

 I'm not exactly sure why do we get random order for self.alias_map in
 join. It's an OrderedDict, so that shouldn't be 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/069.c031adf17d2c48989c33585c749ab949%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28343: Documentation for Windows users can be simpler now that we only support Python >= 3.5

2017-06-27 Thread Django

#28343: Documentation for Windows users can be simpler now that we only support
Python >= 3.5
-+-
 Reporter:  Ramiro Morales   |Owner:  Ramiro
 Type:   |  Morales
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 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 Ramiro Morales):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/8684 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/064.1d6d880677161357b94532f17ee4fb31%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28343: Documentation for Windows users can be simpler now that we only support Python >= 3.5

2017-06-27 Thread Django

#28343: Documentation for Windows users can be simpler now that we only support
Python >= 3.5
-+-
Reporter: Ramiro | Owner: Ramiro Morales
Morales|
Type: | Status: assigned
Cleanup/optimization |
Component: |Version: master
Documentation |
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 |
-+-
Python installations on WIndows now
* Ship the PEP397 `py` launcher which reduces the need to either having to
add `python.exe` directory to PATH or having to always aspecify its full
path. OIt also cand detect your Python's `python.exe` even when its
invoked from inside a virtualenv.
* Have a better ''"Execute manage.py or runtest.py by simply running
them"'' story when compared to previous Python versions, thanks partially
to the above mentioned launcher.

This would allow us to reduce special casing of Windows when describing
command line interactions. In particular IMHO the suggestion to use the
Git for Windows Bash shell can be dropped from the contributing tutorial
as it doesn't actually make things easier.

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

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

2017-06-27 Thread Django

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

 * needs_better_patch:  0 => 1
 * 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/071.68736fa2f26a077753b1728fd5a46de7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28336: Extra `:` in MIDDLEWARE settings documentation

2017-06-27 Thread Django

#28336: Extra `:` in MIDDLEWARE settings documentation
--+
 Reporter:  Baptiste Mispelon |Owner:  Laura
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.11
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"a84b555eb5530c9276bcf3531c0d39669c0c5084" a84b555e]:
 {{{
 #!CommitTicketReference repository=""
 revision="a84b555eb5530c9276bcf3531c0d39669c0c5084"
 [1.11.x] Fixed #28336 -- Fixed typo in docs/ref/settings.txt.

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

Re: [Django] #28336: Extra `:` in MIDDLEWARE settings documentation

2017-06-27 Thread Django

#28336: Extra `:` in MIDDLEWARE settings documentation
--+
 Reporter:  Baptiste Mispelon |Owner:  Laura
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.11
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e58c87cb7042ba8ed1a33761ac2b6b4efed70b29" e58c87cb]:
 {{{
 #!CommitTicketReference repository=""
 revision="e58c87cb7042ba8ed1a33761ac2b6b4efed70b29"
 Fixed #28336 -- Fixed typo in docs/ref/settings.txt.
 }}}

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

Re: [Django] #27449: Make django.utils.translation.trans_real.get_supported_language_variant public API

2017-06-27 Thread Django

#27449: Make django.utils.translation.trans_real.get_supported_language_variant
public API
-+-
 Reporter:  Iacopo Spalletti |Owner:  Sebastian
 |  Sangervasi
 Type:  New feature  |   Status:  assigned
Component:   |  Version:  1.10
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Sebastian Sangervasi):

 * has_patch:  0 => 1


Comment:

 I have submitted a pull request:
 [https://github.com/django/django/pull/8682]

 I followed procedure for the creation of new tests and all tests pass.
 However, I had some questions about how tests are being done for
 translation. I'm going to ask these these questions on the pull request,
 but I can move them here if that is preferred.

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

Re: [Django] #27449: Make django.utils.translation.trans_real.get_supported_language_variant public API

2017-06-27 Thread Django

#27449: Make django.utils.translation.trans_real.get_supported_language_variant
public API
-+-
 Reporter:  Iacopo Spalletti |Owner:  Sebastian
 |  Sangervasi
 Type:  New feature  |   Status:  assigned
Component:   |  Version:  1.10
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Sebastian Sangervasi):

 * owner:  Iacopo Spalletti => Sebastian Sangervasi


Comment:

 This seems to have gone unattended for four months, so I worked on it as a
 first contribution. I have a pull request ready to go, so I'm going to
 claim this.

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

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

2017-06-27 Thread Django

Comment (by Julian Andrews):

I've written up a patch here: https://github.com/django/django/pull/8681.
I looked at the `django-pylibmc` code, and it was very similar to what I
was already doing, but there are a few differences.

First, `django-pylibmc` seems to be returning `False` to indicate failure
for a bunch of methods (and `None` to indicate success). Given that that
differs from the `MemcachedCache` behavior, and that the `False` vs.
`None` distinction is sort of confusing, I decided to stick with the
default behavior. I actually like the idea of a return value that
indicates if cache fetch was successful, but in that case, the relevant
methods should probably always return `True` or `False`, and that behavior
should be consistent across backends. I decided not to do that as part of
this PR.

Second, `django-pylibmc` includes logging of errors. I actually *really*
like that, but again, it's not consistent with the other backend behavior,
so I didn't include that. I could add logging though I'm not really that
familiar with the django logging conventions, so some pointers on that
would be helpful!

Third, `django-pylibmc` was never catching `ConnectionError`s. As far as I
can tell, when the memcached server goes down, the first error gets a
`ConnectionError` and then later ones throw `ServerDown` so I'm pretty
sure we need to catch both.

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

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

2017-06-27 Thread Django

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

 * owner:  nobody => Julian Andrews
 * 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/071.a2fcea29a5319b404705755a257501e2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28297: Same queryset result in two different queries on ORM

2017-06-27 Thread Django

#28297: Same queryset result in two different queries on ORM
-+-
 Reporter:  Marcus Renno |Owner:  Marcus
 |  Renno
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  join, annotation, F  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Marcus Renno):

 I updated the code in the PR. If someone has some time to check, please go
 ahead and share your comments.

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

Re: [Django] #28046: Add tablespace support to Index class

2017-06-27 Thread Django

#28046: Add tablespace support to Index class
-+-
 Reporter:  Markus Holtermann|Owner:  felixxm
 Type:  New feature  |   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:"3297dede7fce4b190f7b3bf0b0fc29a734151b61" 3297dede]:
 {{{
 #!CommitTicketReference repository=""
 revision="3297dede7fce4b190f7b3bf0b0fc29a734151b61"
 Fixed #28046 -- Added the db_tablespace parameter to class-based indexes.

 Thanks Markus Holtermann and Tim Graham for reviews.
 }}}

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

Re: [Django] #28046: Add tablespace support to Index class

2017-06-27 Thread Django

#28046: Add tablespace support to Index class
-+-
 Reporter:  Markus Holtermann|Owner:  felixxm
 Type:  New feature  |   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 felixxm):

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

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

2017-06-27 Thread Django

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

 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 It might be worth looking at [https://github.com/django-pylibmc/django-
 pylibmc/blob/master/django_pylibmc/memcached.py django_pylibmc] and
 emulating the behavior there.

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

Re: [Django] #28342: PyLibMCCache throwing exceptions when memcached server is down

2017-06-27 Thread Django

#28342: PyLibMCCache throwing exceptions when memcached server is down
-+-
 Reporter:  Julian Andrews   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  memcached cache  | Triage Stage:
  pylibmc|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Julian Andrews):

 My current workaround is subclass of `PyLibMCCache` which catches
 `pylibmc.ConnectionError` or `pylibmc.ServerDown` for each operation, and
 then does whatever `MemcachedCache` is doing in each case. I'd be happy to
 turn that into a PR for a change to `PyLibMCCache` if that approach is
 good. I'm not sure if there are other sorts of exceptions that `pylibmc`
 raises that should also be handled, but I think it would be a good start.

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

Re: [Django] #28330: Prevent passing positional arguments to an Index.

2017-06-27 Thread Django

#28330: Prevent passing positional arguments to an Index.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"617505ca892fc84c7be1c224ebca2c27f93e8f50" 617505ca]:
 {{{
 #!CommitTicketReference repository=""
 revision="617505ca892fc84c7be1c224ebca2c27f93e8f50"
 Fixed #28330 -- Prevented passing positional arguments to an Index.

 Thanks Tim Graham for the review.
 }}}

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

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

[Django] #28342: PyLibMCCache throwing exceptions when memcached server is down

2017-06-27 Thread Django

#28342: PyLibMCCache throwing exceptions when memcached server is down
-+-
   Reporter:  Julian |  Owner:  nobody
  Andrews|
   Type:  Bug| Status:  new
  Component:  Core   |Version:  1.11
  (Cache system) |   Keywords:  memcached cache
   Severity:  Normal |  pylibmc
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 If your memcached server is down, pylibmc will raise a
 `pylibmc.ConnectionError` or `pylibmc.ServerDown` exception for all
 operations. This is different from the behavior of the `python-memcached`
 package (see http://sendapatch.se/projects/pylibmc/misc.html). However,
 the `PyLibMCCache` cache backend does nothing to catch these errors. As a
 result, the behavior is different from the `MemcachedCache` backend which
 fails silently.

 This behavior is particularly problematic for fragment caches which
 obviously shouldn't raise an exception. In any case, it seems pretty clear
 that both backends should have the same behavior.

 

 Steps to reproduce:

 1. Setup a Django app `CACHES` set to use `PyLibMCCache`:

 {{{
 CACHES = {
 'default': {
 'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache',
 'LOCATION': '127.0.0.1:11211',
 }
 }
 }}}

 2. With no active memcached server open a shell and run:

 {{{
 from django.core.cache import cache
 cache.get('foo')
 }}}

 `pylibmc` will raise an exception. Using `MemcachedCache`, `cache.get`
 will instead return `None`.

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

Re: [Django] #28331: Add an extra_context attribute to class-based generic views that use ContextMixin (e.g. TemplateView)

2017-06-27 Thread Django

#28331: Add an extra_context attribute to class-based generic views that use
ContextMixin (e.g. TemplateView)
-+-
 Reporter:  Jeremy   |Owner:  Bruno
 Type:   |  Alla
  Cleanup/optimization   |   Status:  assigned
Component:  Generic views|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham):

 Looks good. ref/class-based-views/flattened-index/ also.

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

Re: [Django] #27670: Genuine ImportError masked by exception handling code when loading shell

2017-06-27 Thread Django

#27670: Genuine ImportError masked by exception handling code when loading shell
-+-
 Reporter:  Peter Inglesby   |Owner:  Peter
 |  Inglesby
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.10
  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 Tim Graham):

 Peter, are you still planning to provide a patch here?

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

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

Re: [Django] #28339: Expand the docs around how sqlmigrate works with regards to constraint and index names (was: Setting db_index=False on a field doesn't actually remove the index)

2017-06-27 Thread Django

#28339: Expand the docs around how sqlmigrate works with regards to constraint 
and
index names
--+
 Reporter:  Craig de Stigter  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.11
 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 Tim Graham):

 * component:  Migrations => Documentation
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I think the constraint and index names generated by Django aren't
 necessarily the same across different versions -- that's probably why
 introspection is used. [https://docs.djangoproject.com/en/dev/ref/django-
 admin/#django-admin-sqlmigrate As the documentation for sqlmigrate] says,

  "This requires an active database connection, which it will use to
 resolve constraint names; this means you must generate the SQL against a
 copy of the database you wish to later apply it on."

 See also bugs like #23577 which cause names to get out of sync with that
 Django initially generated (and #27064).

 I'm not sure if anything can be done besides improving the documentation
 of these limitations.

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

Re: [Django] #28341: GeometryField doesn't create GEOSGeometry objects lazily anymore

2017-06-27 Thread Django

#28341: GeometryField doesn't create GEOSGeometry objects lazily anymore
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  1.8
 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 Tim Graham):

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

Re: [Django] #28277: Validate that annotate() and aggregate() args and kwarg values are expressions

2017-06-27 Thread Django

#28277: Validate that annotate() and aggregate() args and kwarg values are
expressions
-+-
 Reporter:  Tim Graham   |Owner:  felixxm
 Type:   |   Status:  assigned
  Cleanup/optimization   |
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 felixxm):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/8680 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/067.15771acbed6869c88ceed2da3381e367%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28277: Validate that annotate() and aggregate() args and kwarg values are expressions

2017-06-27 Thread Django

#28277: Validate that annotate() and aggregate() args and kwarg values are
expressions
-+-
 Reporter:  Tim Graham   |Owner:  felixxm
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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 felixxm):

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


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

Re: [Django] #28341: GeometryField doesn't create GEOSGeometry objects lazily anymore

2017-06-27 Thread Django

#28341: GeometryField doesn't create GEOSGeometry objects lazily anymore
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  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 Sergey Fedoseev:

Old description:

> Bisected to e9103402c0fa873aea58a6a11dba510cd308cb84 on test project with
> this script:
>
> {{{
> import mock
> import sys
>
> with mock.patch('django.utils.six.moves.html_parser'):
> import django
> from django.test import TestCase
> from django.contrib.gis.geos import Point
>
> from test_app.models import City
>

> def side_effect(*args, **kwargs):
> sys.exit(1)
>

> django.setup()
>

> with mock.patch('django.contrib.gis.db.models.fields.Geometry.__init__',
> side_effect=side_effect):
> City.objects.first()
> }}}

New description:

 Bisected to e9103402c0fa873aea58a6a11dba510cd308cb84 on test project with
 this script:

 {{{
 import mock
 import sys

 with mock.patch('django.utils.six.moves.html_parser'):
 import django
 from django.test import TestCase
 from django.contrib.gis.geos import Point

 from test_app.models import City


 def side_effect(*args, **kwargs):
 sys.exit(1)


 django.setup()


 with mock.patch('django.contrib.gis.db.models.fields.Geometry.__init__',
 side_effect=side_effect):
 City.objects.first()
 }}}

 This laziness is declared in
 [https://docs.djangoproject.com/en/dev/ref/contrib/gis/tutorial/#lazy-
 geometries GeoDjango Tutorial].

--

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

Re: [Django] #28341: GeometryField doesn't create GEOSGeometry objects lazily anymore

2017-06-27 Thread Django

#28341: GeometryField doesn't create GEOSGeometry objects lazily anymore
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  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 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 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.af3edbaa91c9d87f14ca133992c3f147%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28341: GeometryField doesn't create GEOSGeometry objects lazily anymore

2017-06-27 Thread Django

#28341: GeometryField doesn't create GEOSGeometry objects lazily anymore
---+
   Reporter:  Sergey Fedoseev  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  GIS  |Version:  1.8
   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|
---+
 Bisected to e9103402c0fa873aea58a6a11dba510cd308cb84 on test project with
 this script:

 {{{
 import mock
 import sys

 with mock.patch('django.utils.six.moves.html_parser'):
 import django
 from django.test import TestCase
 from django.contrib.gis.geos import Point

 from test_app.models import City


 def side_effect(*args, **kwargs):
 sys.exit(1)


 django.setup()


 with mock.patch('django.contrib.gis.db.models.fields.Geometry.__init__',
 side_effect=side_effect):
 City.objects.first()
 }}}

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

Re: [Django] #28331: Add an extra_context attribute to class-based generic views that use ContextMixin (e.g. TemplateView)

2017-06-27 Thread Django

#28331: Add an extra_context attribute to class-based generic views that use
ContextMixin (e.g. TemplateView)
-+-
 Reporter:  Jeremy   |Owner:  Bruno
 Type:   |  Alla
  Cleanup/optimization   |   Status:  assigned
Component:  Generic views|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Bruno Alla):

 I assume a good place to document that is here:
 https://docs.djangoproject.com/en/dev/ref/class-based-views/mixins-
 simple/#contextmixin

 As well as adding an entry in the release notes:
 https://docs.djangoproject.com/en/dev/releases/2.0/

 And maybe mention it in the TemplateView, under the context section as
 well?
 https://docs.djangoproject.com/en/dev/ref/class-based-
 views/base/#templateview

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

Re: [Django] #28201: Make CharField form field prohibit null characters

2017-06-27 Thread Django

#28201: Make CharField form field prohibit null characters
-+-
 Reporter:  CM Lubinski  |Owner:  Alejandro
 Type:   |  Zamora Fonseca
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  1.11
 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 Claude Paroz):

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

Re: [Django] #28297: Same queryset result in two different queries on ORM

Re: [Django] #28343: Documentation for Windows users can be simpler now that we only support Python >= 3.5

[Django] #28343: Documentation for Windows users can be simpler now that we only support Python >= 3.5

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

Re: [Django] #28336: Extra `:` in MIDDLEWARE settings documentation

Re: [Django] #28336: Extra `:` in MIDDLEWARE settings documentation

Re: [Django] #27449: Make django.utils.translation.trans_real.get_supported_language_variant public API

Re: [Django] #27449: Make django.utils.translation.trans_real.get_supported_language_variant public API

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

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

Re: [Django] #28297: Same queryset result in two different queries on ORM

Re: [Django] #28046: Add tablespace support to Index class

Re: [Django] #28046: Add tablespace support to Index class

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

Re: [Django] #28342: PyLibMCCache throwing exceptions when memcached server is down

Re: [Django] #28330: Prevent passing positional arguments to an Index.

[Django] #28342: PyLibMCCache throwing exceptions when memcached server is down

Re: [Django] #28331: Add an extra_context attribute to class-based generic views that use ContextMixin (e.g. TemplateView)

Re: [Django] #27670: Genuine ImportError masked by exception handling code when loading shell

Re: [Django] #28339: Expand the docs around how sqlmigrate works with regards to constraint and index names (was: Setting db_index=False on a field doesn't actually remove the index)

Re: [Django] #28341: GeometryField doesn't create GEOSGeometry objects lazily anymore

Re: [Django] #28277: Validate that annotate() and aggregate() args and kwarg values are expressions

Re: [Django] #28277: Validate that annotate() and aggregate() args and kwarg values are expressions

Re: [Django] #28341: GeometryField doesn't create GEOSGeometry objects lazily anymore

Re: [Django] #28341: GeometryField doesn't create GEOSGeometry objects lazily anymore

[Django] #28341: GeometryField doesn't create GEOSGeometry objects lazily anymore

Re: [Django] #28331: Add an extra_context attribute to class-based generic views that use ContextMixin (e.g. TemplateView)

Re: [Django] #28201: Make CharField form field prohibit null characters

28 matches

Site Navigation

Mail list logo

Footer information