date:20160829

Re: [Django] #27142: makemigrations fails on special database connections

2016-08-29 Thread Django

#27142: makemigrations fails on special database connections
-+
 Reporter:  gerricom |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.10
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by timgraham):

 Consulting database routers might work. I think I had rejected that
 solution in mind my because I thought `model_name` was a required argument
 for `allow_migrate()` but now I see it's not. I'll see if this solution is
 feasible tomorrow, unless someone works on it or rejects the idea while
 I'm sleeping.

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

Re: [Django] #27148: Invalid input for UUIDField with ModelMultipleChoiceField throws ValueError, not ValidationError

2016-08-29 Thread Django

#27148: Invalid input for UUIDField with ModelMultipleChoiceField throws
ValueError, not ValidationError
-+
 Reporter:  blueyed  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.10
 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):

 * Attachment "27148.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/065.ee9540523d59a9de03c3e89502af8b77%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27148: Invalid input for UUIDField with ModelMultipleChoiceField throws ValueError, not ValidationError

2016-08-29 Thread Django

#27148: Invalid input for UUIDField with ModelMultipleChoiceField throws
ValueError, not ValidationError
-+
 Reporter:  blueyed  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.10
 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
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Something like the attached might be appropriate.

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

Re: [Django] #27147: Add support for defining bounds in postgres range fields

2016-08-29 Thread Django

Comment (by impala2):

Replying to [comment:3 timgraham]:
> Is this about form fields and/or model fields? How does it interact with
the fact that for some types, "PostgreSQL always returns a range in a
canonical form that includes the lower bound and excludes the upper bound;
that is `[)`." as the documentation ticket says. Accepting because the
idea seems sensible, however, I would like to see a patch to make a final
evaluation of the idea.

Ah, I saw that but misunderstood as "no matter how it was originally
inserted, django will always interpret incoming data as `[)` because it
doesn't know any better. I now see that postgres canonicalizes discrete
ranges but I'll see what I can do about it. The proposal still at least
makes sense for non-discrete ranges.

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

Re: [Django] #27147: Add support for defining bounds in postgres range fields

2016-08-29 Thread Django

#27147: Add support for defining bounds in postgres range fields
-+-
 Reporter:  impala2  |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgres range   | Triage Stage:  Accepted
  bounds |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 Is this about form fields and/or model fields? How does it interact with
 the fact that for some types, "PostgreSQL always returns a range in a
 canonical form that includes the lower bound and excludes the upper bound;
 that is `[)`." as the documentation ticket says. Accepting because the
 idea seems sensible, however, I would like to see a patch to make a final
 evaluation of the idea.

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

[Django] #27148: Invalid input for UUIDField with ModelMultipleChoiceField throws ValueError, not ValidationError

2016-08-29 Thread Django

#27148: Invalid input for UUIDField with ModelMultipleChoiceField throws
ValueError, not ValidationError
+
 Reporter:  blueyed |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  1.10
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I have added a test in https://github.com/django/django/pull/7180.

 This test shows that an invalid value for a UUIDField will bubble up as
 `ValueError`.  The problem here seems to be that `get_prep_value` just
 passes through the (invalid) string.

 Only when the queryset is evaluated just below via the following code,
 the ValueError from `UUIDField.get_db_prep_value` is raised and bubbles
 up:

 {{{
 self.queryset.filter(**{'%s__in' % key: value})
 pks = set(force_text(getattr(o, key)) for o in qs)
 }}}

 Explicitly evaluating the queryset above already would fix it, but that
 would get done for every selected value then.

 Needs `UUIDField` to be fixed for this, e.g. raising the `ValueError`
 from `get_prep_value` already?
 In this case other fields would need the same fix probably (from what I
 have seen while skimming the code).

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

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

Re: [Django] #27147: Add support for defining bounds in postgres range fields

2016-08-29 Thread Django

Comment (by impala2):

Replying to [comment:1 timgraham]:
> Can you give a use case to demonstrate exactly how this would work? See
also #26345.

That ticket only refers to the documentation, not adding ability to
override.

My use-case is for date ranges. It's often more natural to have inclusive
ranges (`[]`) than the default `[)`. For example it would make more sense
that is something active for a month to start on the first and end on the
last day of the month rather than the first of the next month, no?

I recently converted a model from a lower/upper bound pair of date fields
to a DateRange to take advantage of the gist index overlap exclusion but
had to give up this natural property. I was hoping to implement the
ability to do any type of bounds in django to bring the functionality
back. Of course even for dates this is not always most optimal - hotel
reservations make more sense with a `[)` range as people can check-in on
the same day that others check out in the same room.

Anyway that's my 2¢.

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

Re: [Django] #27142: makemigrations fails on special database connections

2016-08-29 Thread Django

Comment (by shaib):

The issue is that `makemigrations` does not have a target database, while
`migrate` does. So, in order to check for consistent history,
`makemigrations` checks all databases. After this didn't work, the fix was
"well, all databases which look like they have migrations", and this still
fails.

I see two possible solutions:

1. Use the DB routing mechanism to find the list of databases which can
actually be migrated (for the relevant app), and only check consistency in
these databases. Then, users with databases which shouldn't be migrated
will have an obvious way to protect them.

2. Claim that "makemigrations" shouldn't actually touch the database --
essentially, that it's an operation whose only arguments are the
migrations and models -- and accept Tim's suggestion.

It's been a while since I looked at the migration generator, but I suspect
that it does ask the database some questions about features etc, which
would somewhat violate route 2.

I think `makemigrations` is a place where we should check consistency,
because one of the two possible reasons for inconsistent history is
erroneous editing of migration files; creating the next migration on top
of an error is something we should prevent if we can, IMO.

I also think just removing the check because of "too many problems", with
no principled reasoning behind it, is not a good option, but I won't argue
too hard for that; practicality beats purity.

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

Re: [Django] #27147: Add support for defining bounds in postgres range fields

2016-08-29 Thread Django

#27147: Add support for defining bounds in postgres range fields
-+-
 Reporter:  impala2  |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgres range   | Triage Stage:
  bounds |  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:

 Can you give a use case to demonstrate exactly how this would work? See
 also #26345.

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

[Django] #27147: Add support for defining bounds in postgres range fields

2016-08-29 Thread Django

#27147: Add support for defining bounds in postgres range fields
--+---
Reporter: impala2 | Owner:
Type: New feature | Status: new
Component: contrib.postgres |Version: master
Severity: Normal| Keywords: postgres range bounds
Triage Stage: Unreviewed| Has patch: 0
Easy pickings: 0 | UI/UX: 0
--+---
Django supports postgres range types in the contrib package, but the
bounds are restricted to the default value of "[)" (inclusive low value,
exclusive high value) in psycopg2. I propose that django add support for
all bounds types - "[]", "(]", "[)" and "()".

Psycopg2 documentation on the matter:
http://initd.org/psycopg/docs/extras.html?highlight=range#range-data-types
Postgres documentation on the syntax:
https://www.postgresql.org/docs/9.2/static/rangetypes.html#RANGETYPES-IO

I think this could easily be implemented via another argument to the range
field type contructor which could be passed down to the psycogp2 range
type whenever it's created. Everything else should be automatic after
that. Some validation is probably a good idea too.

If people think this is a useful feature, I'll try to write a patch.

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

Re: [Django] #27113: Add tests for setting HttpRequest.encoding

2016-08-29 Thread Django

#27113: Add tests for setting HttpRequest.encoding
--+
 Reporter:  timgraham |Owner:  PREM1980
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  HTTP handling |  Version:  1.10
 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 PREM1980):

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

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

Re: [Django] #27113: Add tests for setting HttpRequest.encoding

2016-08-29 Thread Django

#27113: Add tests for setting HttpRequest.encoding
--+
 Reporter:  timgraham |Owner:  PREM1980
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  HTTP handling |  Version:  1.10
 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 PREM1980):

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

Re: [Django] #27141: makemigrations fails with PermissionDenied on django_migrations

2016-08-29 Thread Django

#27141: makemigrations fails with PermissionDenied on django_migrations
--+
 Reporter:  sjoerdjob |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.10
 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 timgraham):

 In ticket:27142#comment:3 I asked whether or not we should even keep this
 check in `makemigrations`. It's getting tedious to deal with all the edge
 cases, with questionable benefit in my view.

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

Re: [Django] #27142: makemigrations fails on special database connections

2016-08-29 Thread Django

* cc: shaib, MarkusH (added)
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted

Comment:

I'm beginning to think that `makemigrations` shouldn't have this check in
the first place due to the many issues that have been reported (#27054,
#27110, #27141) and the more and more complexity that seems needed to add
to fix it. Other opinions welcome. In my view, the most natural thing to
do after creating a migration is to apply it, so it doesn't seem like
delaying the check from `makemigrations` to `migrate` would have a huge
drawback.

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

Re: [Django] #27145: Discrepenacy between documentation and docstring for Storage.save method

2016-08-29 Thread Django

#27145: Discrepenacy between documentation and docstring for Storage.save method
-+-
 Reporter:  pacahon  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   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 bmispelon):

 * stage:  Accepted => Ready for checkin


Comment:

 The proposed patch seems good to me.

 Thanks.

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

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

Re: [Django] #27146: template shows empty string instead of actual content when it contains characters like \x93 and \x94

2016-08-29 Thread Django

#27146: template shows empty string instead of actual content when it contains
characters like \x93 and \x94
-+--
Reporter: bricas |Owner: nobody
Type: Bug | Status: new
Component: Template system | 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:

It would be quite nice if you could do some investigation yourself and
tell us where the bug is. Or even write a test for Django's test suite
(django/tests/template_tests) so we at least have an easy way to reproduce
it. In general, you should ask "is it a bug?" questions on our
[wiki:TicketClosingReasons/UseSupportChannels our support channels] rather
than creating a Trac ticket.

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

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

[Django] #27146: template shows empty string instead of actual content when it contains characters like \x93 and \x94

2016-08-29 Thread Django

#27146: template shows empty string instead of actual content when it contains
characters like \x93 and \x94
-+
 Reporter:  bricas   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.8
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I believe \x93 and \x94 are quote characters from CP-1252.

 I can use `{{string|pprint}}` and see the data in variable, i can use
 `{{string|length}}` and gets its length, but i cannot just print it via
 `{{string}}` -- no error is thrown, but the output is empty.

 This seems like a bug to me, but I can convinced otherwise. :)

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

Re: [Django] #27095: Queries involving postgres Array fields can't include expressions as elements

2016-08-29 Thread Django

#27095: Queries involving postgres Array fields can't include expressions as
elements
--+
 Reporter:  MatthewWilkes |Owner:  PREM1980
 Type:  Bug   |   Status:  assigned
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
--+

Comment (by timgraham):

 
https://github.com/django/django/blob/674e3fe13e5156344bfafbea59018b8837eb3044/tests/postgres_tests/test_array.py#L176-L208

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

Re: [Django] #27097: Add introspection for index type

2016-08-29 Thread Django

#27097: Add introspection for index type
-+-
 Reporter:  akki |Owner:  akki
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  introspection db-| Triage Stage:  Accepted
  indexes 1.11   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akki):

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

Re: [Django] #27113: Add tests for setting HttpRequest.encoding

2016-08-29 Thread Django

#27113: Add tests for setting HttpRequest.encoding
--+
 Reporter:  timgraham |Owner:  PREM1980
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  HTTP handling |  Version:  1.10
 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 PREM1980):

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


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

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

Re: [Django] #27095: Queries involving postgres Array fields can't include expressions as elements

2016-08-29 Thread Django

#27095: Queries involving postgres Array fields can't include expressions as
elements
--+
 Reporter:  MatthewWilkes |Owner:  PREM1980
 Type:  Bug   |   Status:  assigned
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
--+

Comment (by PREM1980):

 Im unable to locate the postgres_tests.test_array:
 test_in_including_F_object and test_contained_by_including_F_object in the
 master branch.

 Can you please point me to the correct location?

 It would be great if you can build an example, so we both are on the same
 page.

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

Re: [Django] #27145: Discrepenacy between documentation and docstring for Storage.save method (was: Misunderstanding beetween documentation and docstring for Storage.save method)

2016-08-29 Thread Django

#27145: Discrepenacy between documentation and docstring for Storage.save method
--+
 Reporter:  pacahon   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 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 timgraham):

 * has_patch:  0 => 1


Comment:

 Looks like 664855b74e1f417384dc7aef35a3df5f86db52d6 added the option to
 use a file-like object but the docs weren't updated. Does this look like
 enough?
 {{{ #!diff
 diff --git a/docs/ref/files/storage.txt b/docs/ref/files/storage.txt
 index dd06701..38f0135 100644
 --- a/docs/ref/files/storage.txt
 +++ b/docs/ref/files/storage.txt
 @@ -221,8 +221,7 @@ The ``Storage`` class
  :meth:`get_available_name`.

  The ``content`` argument must be an instance of
 -:class:`django.core.files.File` or of a subclass of
 -:class:`~django.core.files.File`.
 +:class:`django.core.files.File` or a file-like object.

  .. method:: size(name)
 }}}

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

Re: [Django] #27132: Allowed testing MemcachedCache and PyLibMCCache during the same test run

2016-08-29 Thread Django

#27132: Allowed testing MemcachedCache and PyLibMCCache during the same test run
--+
 Reporter:  edmorley  |Owner:  edmorley
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Cache system)   |  Version:  master
 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
--+

Comment (by Ed Morley ):

 In [changeset:"306545d80508a0d6d70c329667640e7b183c30f0" 306545d8]:
 {{{
 #!CommitTicketReference repository=""
 revision="306545d80508a0d6d70c329667640e7b183c30f0"
 [1.10.x] Fixed #27132 -- Allowed testing MemcachedCache and PyLibMCCache
 during the same test run.

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

Re: [Django] #19914: MemcachedCacheTests failing on pylibmc

2016-08-29 Thread Django

#19914: MemcachedCacheTests failing on pylibmc
-+
 Reporter:  bpeschier|Owner:  edmorley
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Ed Morley ):

 In [changeset:"255456becdf1435ce685faea5f3b58d34993e8a8" 255456be]:
 {{{
 #!CommitTicketReference repository=""
 revision="255456becdf1435ce685faea5f3b58d34993e8a8"
 [1.10.x] Fixed #19914 -- Fixed test failures with pylibmc.

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

Re: [Django] #27132: Allowed testing MemcachedCache and PyLibMCCache during the same test run

2016-08-29 Thread Django

#27132: Allowed testing MemcachedCache and PyLibMCCache during the same test run
--+
 Reporter:  edmorley  |Owner:  edmorley
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Cache system)   |  Version:  master
 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
--+

Comment (by Ed Morley ):

 In [changeset:"547c7e67569b2a0c323b8b64c1ce835206c23e3a" 547c7e6]:
 {{{
 #!CommitTicketReference repository=""
 revision="547c7e67569b2a0c323b8b64c1ce835206c23e3a"
 [1.10.x] Refs #27132 -- Added pylibmc to test requirements.

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

Re: [Django] #27029: Make EmailValidator accept non-ASCII characters

2016-08-29 Thread Django

#27029: Make EmailValidator accept non-ASCII characters
-+-
 Reporter:  RaminFP  |Owner:  Ramin
 Type:   |  Farajpour Cami
  Cleanup/optimization   |   Status:  new
Component:  Core (Other) |  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 timgraham):

 Yes, we add to AUTHORS based on code contributions not bug reports.

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

Re: [Django] #27145: Misunderstanding beetween documentation and docstring for Storage.save method

2016-08-29 Thread Django

#27145: Misunderstanding beetween documentation and docstring for Storage.save
method
--+
 Reporter:  pacahon   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 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 bmispelon):

 * needs_better_patch:   => 0
 * component:  File uploads/storage => Documentation
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Hi,

 I agree with you, there is a discrepancy here between the docstring and
 the documentation and we should correct that.

 I have a feeling that the docstring might be the one that needs fixing but
 I am not sure. This will have to be determined.

 Thanks.

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

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

[Django] #27145: Misunderstanding beetween documentation and docstring for Storage.save method

2016-08-29 Thread Django

#27145: Misunderstanding beetween documentation and docstring for Storage.save
method
--+
Reporter: pacahon | Owner: nobody
Type: Uncategorized | Status: new
Component: File uploads/storage |Version: 1.9
Severity: Normal| Keywords:
Triage Stage: Unreviewed| Has patch: 0
Easy pickings: 0 | UI/UX: 0
--+
Docstring for `django.core.files.storage.Storage.save` method says:

{{{
"""
Saves new content to the file specified by name. The content
should be
a proper File object or any python file-like object, ready to be
read
from the beginning.
"""
}}}

But in

[https://docs.djangoproject.com/en/1.9/ref/files/storage/#django.core.files.storage.Storage.save
docs] provided next description for `content` attribute

{{{
The content argument must be an instance of django.core.files.File or of a
subclass of File.
}}}

What about to update docs or add additional check in `save` method?

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

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

Re: [Django] #27029: Make EmailValidator accept non-ASCII characters

2016-08-29 Thread Django

#27029: Make EmailValidator accept non-ASCII characters
-+-
 Reporter:  RaminFP  |Owner:  Ramin
 Type:   |  Farajpour Cami
  Cleanup/optimization   |   Status:  new
Component:  Core (Other) |  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 RaminFP):

 Hi,
 I see here way Contributing to Django
 https://docs.djangoproject.com/en/dev/internals/contributing/
 You write PR for patch issue ,this means my name not 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/065.8c795b91fca82dffea7955f937244239%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27132: Allowed testing MemcachedCache and PyLibMCCache during the same test run (was: Test PyLibMCCache on Jenkins)

2016-08-29 Thread Django

#27132: Allowed testing MemcachedCache and PyLibMCCache during the same test run
--+
 Reporter:  edmorley  |Owner:  edmorley
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Cache system)   |  Version:  master
 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
--+

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

Re: [Django] #27132: Test PyLibMCCache on Jenkins

2016-08-29 Thread Django

#27132: Test PyLibMCCache on Jenkins
--+
 Reporter:  edmorley  |Owner:  edmorley
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Cache system)   |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"047c1d48a613cc2a16f078a9094cc799f06e6b0c" 047c1d4]:
 {{{
 #!CommitTicketReference repository=""
 revision="047c1d48a613cc2a16f078a9094cc799f06e6b0c"
 Fixed #27132 -- Allowed testing MemcachedCache and PyLibMCCache during the
 same test run.
 }}}

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

Re: [Django] #19914: MemcachedCacheTests failing on pylibmc

2016-08-29 Thread Django

#19914: MemcachedCacheTests failing on pylibmc
-+
 Reporter:  bpeschier|Owner:  edmorley
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"674e3fe13e5156344bfafbea59018b8837eb3044" 674e3fe1]:
 {{{
 #!CommitTicketReference repository=""
 revision="674e3fe13e5156344bfafbea59018b8837eb3044"
 Fixed #19914 -- Fixed test failures with pylibmc.
 }}}

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

Re: [Django] #19914: MemcachedCacheTests failing on pylibmc

2016-08-29 Thread Django

#19914: MemcachedCacheTests failing on pylibmc
-+
 Reporter:  bpeschier|Owner:  edmorley
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  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 Tim Graham ):

 In [changeset:"5756edd46dfad87a0ab9856489887ed5bc2914b5" 5756edd4]:
 {{{
 #!CommitTicketReference repository=""
 revision="5756edd46dfad87a0ab9856489887ed5bc2914b5"
 [1.10.x] Refs #19914 -- Split the test_invalid_keys cache test into two.

 The first half of the test fails when using pylibmc (so will need
 to be skipped).

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

Re: [Django] #27124: caches_setting_for_tests passes cull related options to memcached tests

2016-08-29 Thread Django

#27124: caches_setting_for_tests passes cull related options to memcached tests
--+
Reporter: edmorley |Owner: edmorley
Type: Cleanup/optimization | Status: closed
Component: Core (Cache system) | Version: master
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
--+

Comment (by Tim Graham ):

In [changeset:"fb8eea5680f20d3df50eb6a7d972645a388cb196" fb8eea56]:
{{{
#!CommitTicketReference repository=""
revision="fb8eea5680f20d3df50eb6a7d972645a388cb196"
[1.10.x] Fixed #27124 -- Excluded cull-related cache configs from
memcached tests.

Since the `cull` and `zero_cull` test cache configs set `MAX_ENTRIES`
and `CULL_FREQUENCY` in `OPTIONS`, which are only intended for use with
the locmem, filesystem, and database backends. This prevents test
failures once refs #20892 is fixed.

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

Re: [Django] #27142: makemigrations fails on special database connections

2016-08-29 Thread Django

#27142: makemigrations fails on special database connections
+--
 Reporter:  gerricom|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.10
 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 gerricom):

 Replying to [comment:1 claudep]:
 > Could you please provide the full traceback of the error? Did you test
 the patch proposed for #27110, did it help in your use case?

 This is the full traceback:


 {{{
 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/usr/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 367, in
 execute_from_command_line
 utility.execute()
   File "/usr/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 359, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/usr/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 305, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/usr/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 356, in execute
 output = self.handle(*args, **options)
   File "/usr/local/lib/python2.7/site-
 packages/django/core/management/commands/makemigrations.py", line 100, in
 handle
 loader.check_consistent_history(connection)
   File "/usr/local/lib/python2.7/site-
 packages/django/db/migrations/loader.py", line 278, in
 check_consistent_history
 applied = recorder.applied_migrations()
   File "/usr/local/lib/python2.7/site-
 packages/django/db/migrations/recorder.py", line 65, in applied_migrations
 self.ensure_schema()
   File "/usr/local/lib/python2.7/site-
 packages/django/db/migrations/recorder.py", line 52, in ensure_schema
 if self.Migration._meta.db_table in
 self.connection.introspection.table_names(self.connection.cursor()):
   File "/usr/local/lib/python2.7/site-
 packages/django/db/backends/base/introspection.py", line 57, in
 table_names
 return get_names(cursor)
   File "/usr/local/lib/python2.7/site-
 packages/django/db/backends/base/introspection.py", line 52, in get_names
 return sorted(ti.name for ti in self.get_table_list(cursor)
   File "/usr/local/lib/python2.7/site-
 packages/django/db/backends/mysql/introspection.py", line 53, in
 get_table_list
 cursor.execute("SHOW FULL TABLES")
   File "/usr/local/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 79, in execute
 return super(CursorDebugWrapper, self).execute(sql, params)
   File "/usr/local/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
   File "/usr/local/lib/python2.7/site-packages/django/db/utils.py", line
 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/usr/local/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 62, in execute
 return self.cursor.execute(sql)
   File "/usr/local/lib/python2.7/site-
 packages/django/db/backends/mysql/base.py", line 112, in execute
 return self.cursor.execute(query, args)
   File "/usr/local/lib/python2.7/site-packages/MySQLdb/cursors.py", line
 226, in execute
 self.errorhandler(self, exc, value)
   File "/usr/local/lib/python2.7/site-packages/MySQLdb/connections.py",
 line 36, in defaulterrorhandler
 raise errorvalue
 django.db.utils.ProgrammingError: (1064, "sphinxql: syntax error,
 unexpected IDENT, expecting VARIABLES near 'FULL TABLES'")
 }}}

 The patch in #27110 did not help in this case as the error raises in the
 database introspection.

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

Re: [Django] #20892: Allow configuring the memcached Client with CACHES 'OPTIONS'

2016-08-29 Thread Django

#20892: Allow configuring the memcached Client with CACHES 'OPTIONS'
-+
 Reporter:  alex@…   |Owner:  edmorley
 Type:  New feature  |   Status:  assigned
Component:  Core (Cache system)  |  Version:  1.5
 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 Tim Graham ):

 In [changeset:"fb8eea5680f20d3df50eb6a7d972645a388cb196" fb8eea56]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb8eea5680f20d3df50eb6a7d972645a388cb196"
 [1.10.x] Fixed #27124 -- Excluded cull-related cache configs from
 memcached tests.

 Since the `cull` and `zero_cull` test cache configs set `MAX_ENTRIES`
 and `CULL_FREQUENCY` in `OPTIONS`, which are only intended for use with
 the locmem, filesystem, and database backends. This prevents test
 failures once refs #20892 is fixed.

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

Re: [Django] #19914: MemcachedCacheTests failing on pylibmc

2016-08-29 Thread Django

#19914: MemcachedCacheTests failing on pylibmc
-+
 Reporter:  bpeschier|Owner:  edmorley
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  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 Tim Graham ):

 In [changeset:"cfd1f93d55d3b9317bdf26b426fe21d935ab3399" cfd1f93d]:
 {{{
 #!CommitTicketReference repository=""
 revision="cfd1f93d55d3b9317bdf26b426fe21d935ab3399"
 Refs #19914 -- Split the test_invalid_keys cache test into two.

 The first half of the test fails when using pylibmc (so will need
 to be skipped).
 }}}

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

Re: [Django] #27141: makemigrations fails with PermissionDenied on django_migrations

2016-08-29 Thread Django

#27141: makemigrations fails with PermissionDenied on django_migrations
--+
 Reporter:  sjoerdjob |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.10
 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):

 * has_patch:  1 => 0


Comment:

 Feel free to send a pull request to my branch or give my PR a review so we
 can merge it and continue this ticket in a new 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.5b952af43a24d4081aa0a47324fd662e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26487: Use EHLO after smtplib.SMTP_SSL too.

2016-08-29 Thread Django

#26487: Use EHLO after smtplib.SMTP_SSL too.
--+
 Reporter:  kchmiela  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Mail)   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 In my opinion, both `ehlo()` calls could be deleted, and nothing should be
 added. `starttls`, `login` and other connection methods are caring for
 that themselves. However, they should not be harmful either.

 If there is a real problem with `EmailBackend` not calling `ehlo()`,
 please provide more details.

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

Re: [Django] #27144: annotating across a ManyToManyField returns duplicate results

2016-08-29 Thread Django

#27144: annotating across a ManyToManyField returns duplicate results
-+-
 Reporter:  setivolkylany|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by setivolkylany):

 Replying to [comment:2 shaib]:
 > Hi,
 >
 > We value your interest in the Django project. However, you are asking
 questions in the wrong place and in the wrong way.
 >
 > Please don't open an issue unless you are fairly convinced that you
 found a problem with Django.
 >
 > With respect to how to ask questions -- it is not about the English
 language, it is about the content of the tickets you open. Please see e.g.
 [http://www.catb.org/esr/faqs/smart-questions.html#translations How to ask
 smart questions] -- the link points directly to the list of translations,
 so you can hopefully read it in your language.
 >
 > For the specific matter you raised here -- yes, I believe this is the
 result one should expect. It is not a bug. For what you are trying to
 achieve, try to use `prefetch_related`.

 Please, delete this ticket

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

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

Re: [Django] #27143: SearchQuery is not combinable using more than one `&` or `|` operators

2016-08-29 Thread Django

#27143: SearchQuery is not combinable using more than one `&` or `|` operators
--+
 Reporter:  hixi  |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  Search| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by jarshwah):

 More detail here: https://groups.google.com/forum/#!topic/django-
 developers/hTj7NLXu2xw

 Copying the likely fix:

 SearchQuery defines its own operators to work around the limitation in
 Combinable, but fails to take into account that when two SearchQuery
 instances are combined, you're returned a CombinedExpression (containing
 SearchQueries). SearchVector *does* take this into consideration
 though.The fix would be to define a SearchQueryCombinable Mixin that looks
 very similar to SearchVectorCombinable, and override the various __or__
 and __and__ methods, as the SearchQuery type does itself.

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

Re: [Django] #27141: makemigrations fails with PermissionDenied on django_migrations

2016-08-29 Thread Django

#27141: makemigrations fails with PermissionDenied on django_migrations
--+
 Reporter:  sjoerdjob |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.10
 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 sjoerdjob):

 Responding to Tim Graham his remark on the pull request:

 > Sure, you could let us know how inspectdb currently works with this
 situation. I guess it might hit that exception block. I guess if that's
 better than silently skipping such tables then that solution may not be
 ideal, or at least we'd need a new parameter to
 introspection.table_names() to skip unowned tables.

 Yes, I'm indeed hitting the exception handler there. Based on results from
 Django==1.9.7, it comes from `get_table_description` which has a `SELECT *
 FROM %s LIMIT 1`.

 So I think what would make the most sense would be to add a `try`/`except
 DatabaseError` around the part where the applied migrations are obtained,
 and then (re-)raise a `MigrationSchemaMissing` instead. The error message
 is after all correct: "\nNot checking migrations as it is not possible to
 access/create the django_migrations table.".

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

Re: [Django] #27143: SearchQuery is not combinable using more than one `&` or `|` operators

2016-08-29 Thread Django

#27143: SearchQuery is not combinable using more than one `&` or `|` operators
--+
 Reporter:  hixi  |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  Search| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jarshwah):

 * cc: josh.smeaton@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * version:  1.10 => master
 * needs_docs:   => 0
 * 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/062.0b16324b3942d3cb98a72c0e084aac35%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27144: annotating across a ManyToManyField returns duplicate results (was: It is may be bug the Django ORM, may be I bad know SQL may I badly read the Django docs and made googling.)

2016-08-29 Thread Django

#27144: annotating across a ManyToManyField returns duplicate results
-+-
 Reporter:  setivolkylany|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * component:  Uncategorized => Database layer (models, ORM)
 * type:  Uncategorized => Bug


Comment:

 #10060 might be relevant.

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

Re: [Django] #27144: It is may be bug the Django ORM, may be I bad know SQL may I badly read the Django docs and made googling.

2016-08-29 Thread Django

#27144: It is may be bug the Django ORM, may be I bad know SQL may I badly read
the
Django docs and made googling.
---+--
Reporter: setivolkylany |Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.9
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
---+--
Changes (by shaib):

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

Comment:

Hi,

We value your interest in the Django project. However, you are asking
questions in the wrong place and in the wrong way.

Please don't open an issue unless you are fairly convinced that you found
a problem with Django.

With respect to how to ask questions -- it is not about the English
language, it is about the content of the tickets you open. Please see e.g.
[http://www.catb.org/esr/faqs/smart-questions.html#translations How to ask
smart questions] -- the link points directly to the list of translations,
so you can hopefully read it in your language.

For the specific matter you raised here -- yes, I believe this is the
result one should expect. It is not a bug. For what you are trying to
achieve, try to use `prefetch_related`.

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

Re: [Django] #27131: send_mail error if smtp server uses CRAM-MD5 auth method

2016-08-29 Thread Django

#27131: send_mail error if smtp server uses CRAM-MD5 auth method
-+
 Reporter:  slavugan |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  send_mail| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by claudep):

 * has_patch:  0 => 1
 * version:  1.8 => master
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

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

Re: [Django] #27140: Prevent template rendering from hiding a property's TypeError (was: TypeError not reported from a template)

2016-08-29 Thread Django

#27140: Prevent template rendering from hiding a property's TypeError
-+
 Reporter:  azmeuk   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.10
 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 timgraham):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

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

Re: [Django] #27144: It is may be bug the Django ORM, may be I bad know SQL may I badly read the Django docs and made googling. (was: It is may be bug the Django ORM, may be I bad know SQL may it badl

2016-08-29 Thread Django

#27144: It is may be bug the Django ORM, may be I bad know SQL may I badly read 
the
Django docs and made googling.
---+--
 Reporter:  setivolkylany  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.9
 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 setivolkylany):

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


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

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

[Django] #27144: It is may be bug the Django ORM, may be I bad know SQL may it badly read the Django docs and made googling.

2016-08-29 Thread Django

#27144: It is may be bug the Django ORM, may be I bad know SQL may it badly read
the Django docs and made googling.
---+
 Reporter:  setivolkylany  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Dublication objects, if using annotation with models.F() (not the
 models.Count - it is working properly) on ManyToManyField

 Code:

 {{{

 print('Real count books =\t', Book.objects.count())
 print('Total count tags in all books =\t',
 Book.objects.annotate(
 count_tags=models.Count('tags', distinct=True)
 ).aggregate(
 total_used_count_tags=models.Sum('count_tags')
 )['total_used_count_tags']
 )

 qs =
 Book.objects.values('tags').annotate(tags_names=models.F('tags__name'))
 print('Query:\n', qs.query)
 print('Count books after query =\t', qs.count())


 print('Raw query return next count books =\t', len([i for i in
 Book.objects.raw("""
 SELECT
 "books"."id",
 "books_tags"."tag_id",
 "tags"."name" AS "tags_names"
 FROM "books"
 LEFT OUTER JOIN
 "books_tags" ON ("books"."id" = "books_tags"."book_id")
 LEFT OUTER JOIN
 "tags" ON ("books_tags"."tag_id" = "tags"."id")
 ORDER BY
 "books"."date_added" ASC
 """
 )]))
 }}}


 Output

 Real count books =   5
 Total count tags in all books =  13
 Query: SELECT "books_tags"."tag_id", "tags"."name" AS "tags_names"
 FROM "books" LEFT OUTER JOIN "books_tags" ON ("books"."id" =
 "books_tags"."book_id") LEFT OUTER JOIN "tags" ON ("books_tags"."tag_id" =
 "tags"."id") ORDER BY "books"."date_added" ASC
 Count books after query =13
 Raw query return next count books =  13


 Models:


 {{{
 class Book(models.Model):
 """
 Model for books
 """

 id = models.UUIDField(primary_key=True, editable=False,
 default=uuid.uuid4)
 #other fields
 tags = models.ManyToManyField(
 Tag,
 verbose_name=_('Tags'),
 related_name='books',
 )


 class Tag(models.Model):
 """
 Model tags for another models
 """

 name = models.SlugField(
 _('name'),
 max_length=30,
 unique=True,
 allow_unicode=True,
 )
 }}}

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

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

Re: [Django] #27142: makemigrations fails on special database connections

2016-08-29 Thread Django

#27142: makemigrations fails on special database connections
+--
 Reporter:  gerricom|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.10
 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 claudep):

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


Comment:

 Could you please provide the full traceback of the error? Did you test the
 patch proposed for #27110, did it help in your use 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/066.55c826e234996fede6926e3464a759df%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27143: SearchQuery is not combinable using more than one `&` or `|` operators

2016-08-29 Thread Django

#27143: SearchQuery is not combinable using more than one `&` or `|` operators
--+
 Reporter:  hixi  |  Owner:
 Type:  Bug   | Status:  new
Component:  contrib.postgres  |Version:  1.10
 Severity:  Normal|   Keywords:  Search
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I think there is a bug/oversight on the SearchQuery implementation.

 Working examples:
 * `SearchQuery() & SearchQuery()`
 * `SearchQuery() | SearchQuery()`
 * `SearchQuery() | SearchQuery() & SearchQuery()`

 But using multiple of the same "concatenators" does not:
 * `SearchQuery() & SearchQuery() & SearchQuery()` -> Error
 * `SearchQuery() & SearchQuery() & SearchQuery()` -> Error

 Expected behaviour would be that these do work 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/047.0daa33a760cea086f47adb1cbf9f3f36%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27142: makemigrations fails on special database connections

2016-08-29 Thread Django

#27142: makemigrations fails on special database connections
+
 Reporter:  gerricom|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.10
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 As direx in #27110 I have a bunch of database connections defined in
 `settings.DATABASES` which I'm using only with raw queries. One of them is
 a sphinxsearch engine. You can use a subset of MySQL commands to query the
 indexes, but not all MySQL commands are implemented there. So
 `makemigrations` fails when checking for the database schema:


 {{{
 django.db.utils.ProgrammingError: (1064, "sphinxql: syntax error,
 unexpected IDENT, expecting VARIABLES near 'FULL TABLES'")
 }}}

 I know, this will be some kind of edge-case but it would be helpful to
 skip any migration-related tasks for selected databases.

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

Re: [Django] #27141: makemigrations fails with PermissionDenied on django_migrations

2016-08-29 Thread Django

#27141: makemigrations fails with PermissionDenied on django_migrations
--+
 Reporter:  sjoerdjob |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.10
 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 claudep):

 * component:  Uncategorized => Migrations
 * has_patch:  0 => 1
 * type:  Uncategorized => Cleanup/optimization
 * 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/067.5dd05538dd7247d45aad54e95703b897%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24112: Inconsistency in TestCase.assertInHTML

2016-08-29 Thread Django

#24112: Inconsistency in TestCase.assertInHTML
---+
 Reporter:  plumdog|Owner:  adamzap
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by claudep):

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

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

2016-08-29 Thread Django

#26401: Allow auth machinery to be used without installing auth app
--+
 Reporter:  satchamo  |Owner:  andkon
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  auth  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by claudep):

 * status:  closed => new
 * 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.74566a3785a1ab264fb04515ff320301%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27141: makemigrations fails with PermissionDenied on django_migrations

2016-08-29 Thread Django

#27141: makemigrations fails with PermissionDenied on django_migrations
---+--
 Reporter:  sjoerdjob  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.10
 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 sjoerdjob):

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


Comment:

 Pull request at https://github.com/django/django/pull/7172

 Let me know if I missed anything.

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

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

[Django] #27141: makemigrations fails with PermissionDenied on django_migrations

2016-08-29 Thread Django

#27141: makemigrations fails with PermissionDenied on django_migrations
---+
 Reporter:  sjoerdjob  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.10
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 On a project I'm currently working on, I have read-only access to 1 table
 on a database.

 Similar to #27054, except that the table `django_migrations` does exist, I
 just don't have read-access to it.

 Error message:

 django.db.utils.ProgrammingError: permission denied for relation
 django_migrations.

 The error occurs in `recorder.py:MigrationRecorder.applied_migrations`,
 specifically the line

 return set(tuple(x) for x in self.migration_qs.values_list("app",
 "name"))

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

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

Re: [Django] #27140: TypeError not reported from a template

2016-08-29 Thread Django

#27140: TypeError not reported from a template
-+--
 Reporter:  azmeuk   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.10
 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 azmeuk):

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


Old description:

> If you try to access an object property in a django template, and this
> property raises a TypeError, then nothing will be raised. If it is, let's
> say, a ZeroDivisionError, then the exception is raised.
>

> {{{
> from django.template import Context, Template
> class FooClassTypeError:
> @property
> def fooproperty(self):
> raise TypeError
> return "somevalue"
>
> class FooClass:
> @property
> def fooproperty(self):
> return 1/0
>
> t = Template("{{ obj.fooproperty }}")
>
> # This call does not raise anything
> t.render(Context(dict(obj=FooClassTypeError(
>
> # This call raises an exception
> t.render(Context(dict(obj=FooClass(
> }}}
>
> I think the expected behavior is that both exceptions should be raised.
> What do you think?

New description:

 If you try to access an object property in a django template, and this
 property raises a TypeError, then nothing will be raised. If it raises,
 let's say, a ZeroDivisionError, then the exception is raised.


 {{{#!python
 from django.template import Context, Template
 class FooClassTypeError:
 @property
 def fooproperty(self):
 raise TypeError
 return "somevalue"

 class FooClass:
 @property
 def fooproperty(self):
 return 1/0

 t = Template("{{ obj.fooproperty }}")

 # This call does not raise anything
 t.render(Context(dict(obj=FooClassTypeError(

 # This call raises an exception
 t.render(Context(dict(obj=FooClass(
 }}}

 I think the expected behavior is that both exceptions should be raised.
 What do you think?

--

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

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

[Django] #27140: TypeError not reported from a template

2016-08-29 Thread Django

#27140: TypeError not reported from a template
-+
 Reporter:  azmeuk   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.10
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 If you try to access an object property in a django template, and this
 property raises a TypeError, then nothing will be raised. If it is, let's
 say, a ZeroDivisionError, then the exception is raised.


 {{{
 from django.template import Context, Template
 class FooClassTypeError:
 @property
 def fooproperty(self):
 raise TypeError
 return "somevalue"

 class FooClass:
 @property
 def fooproperty(self):
 return 1/0

 t = Template("{{ obj.fooproperty }}")

 # This call does not raise anything
 t.render(Context(dict(obj=FooClassTypeError(

 # This call raises an exception
 t.render(Context(dict(obj=FooClass(
 }}}

 I think the expected behavior is that both exceptions should be raised.
 What do you think?

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

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

Re: [Django] #26762: Allow using parts of flatpages without install the app

2016-08-29 Thread Django

#26762: Allow using parts of flatpages without install the app
---+
 Reporter:  vzima  |Owner:  vzima
 Type:  Bug|   Status:  closed
Component:  contrib.flatpages  |  Version:  1.9
 Severity:  Normal |   Resolution:  wontfix
 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 vzima):

 I such case, it should be noted in documentation. When I search a solution
 of the above mentioned error, I should be able to find out the
 `MIGRATION_MODULES` workaround.

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

Re: [Django] #27139: ImportError: No module named 'polls.apps.PollsConfig'

2016-08-29 Thread Django

#27139: ImportError: No module named 'polls.apps.PollsConfig'
---+--
 Reporter:  pjime032   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.10
 Severity:  Normal |   Resolution:  worksforme
 Keywords:  apps   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by bmispelon):

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


Comment:

 Hi,

 Since Django 1.9, the `startapp` command will generate an `apps.py` file
 so the instructions should be correct.

 Is it possible that you're using an older version of Django (`python
 manage.py --version` will tell you)? If so, you either need to update
 Django (1.10 is the latest version) or follow the documentation that
 corresponds to the version of Django you're using (you can switch versions
 at the bottom-right hand corner).

 Thanks.

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

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

61 matches

Mail list logo