date:20160909

Re: [Django] #27205: Django Postgres ArrayField __contain lookup does not behave expectedly

2016-09-09 Thread Django

#27205: Django Postgres ArrayField __contain lookup does not behave expectedly
-+-
 Reporter:  Dean-Christian-  |Owner:  nobody
  Armada |
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql,  | Triage Stage:
  arrayfield |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by charettes):

 > I guess may be similar to #26511.

 It's the same underlying issue as #26511.

 What we'd need here is a way to express we want the text value of a key
 (using the `->>` operator instead of `->`). Ideally the `__contains`
 lookup wouldn't be overloaded for containment (`@>`) for the `JSONField`
 and we'd define a special lookup that takes care of using the correct
 operator but it's too late now.

 #26511 suggests introducing a
 [https://github.com/django/django/compare/master...charettes:jsonb-fts
 #diff-57ceaae67721b3f8d5729222c032af8eR88 transform] to deal with this
 issue but at this point I can't think of a way to expose it as a lookup
 (e.g `data__breed__text__contains='collie'`) since these fields are
 completely unstructured and could include a key conflicting with the
 chosen lookup name (e.g. `{'data': {'breed': {'text': 'terrier'}}}`).

 If we were to introduce this transform the reported queryset could be
 rewritten as:

 {{{#!python
 Dog.objects.annotate(breed=KeyTextTransform('breed',
 'data')).filter(breed__contains='l')
 }}}

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

Re: [Django] #27204: Clashing m2m intermediate table validation should ignore unmanaged models

2016-09-09 Thread Django

#27204: Clashing m2m intermediate table validation should ignore unmanaged 
models
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (System |  Version:  1.10
  checks)|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e7abb5ba8608f90ce97c6edb031ae877195616f5" e7abb5ba]:
 {{{
 #!CommitTicketReference repository=""
 revision="e7abb5ba8608f90ce97c6edb031ae877195616f5"
 Fixed #27204 -- Made clashing m2m intermediary table checks ignore
 unmanaged models.
 }}}

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

Re: [Django] #27204: Clashing m2m intermediate table validation should ignore unmanaged models

2016-09-09 Thread Django

#27204: Clashing m2m intermediate table validation should ignore unmanaged 
models
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (System |  Version:  1.10
  checks)|
 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 berkerpeksag):

 * stage:  Accepted => Ready for checkin


Comment:

 [https://github.com/django/django/pull/7224/ PR #7224] looks good to me
 and tests passed on my system. Just left a comment about a potential typo
 on GitHub.

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

Re: [Django] #27204: Clashing m2m intermediate table validation should ignore unmanaged models

2016-09-09 Thread Django

#27204: Clashing m2m intermediate table validation should ignore unmanaged 
models
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (System checks)  |  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):

 * needs_tests:  1 => 0


Comment:

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

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

2016-09-09 Thread Django

#27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with
double slash
--+
 Reporter:  andrewbadr|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.staticfiles   |  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 andrewbadr):

 That's a complicated question. :) The spec is at
 https://www.ietf.org/rfc/rfc3986.txt but Django shouldn't be in the
 business of trying to make sense of it. Hoping aaugustin will chime in
 here.

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

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

Re: [Django] #27205: Django Postgres ArrayField __contain lookup does not behave expectedly

2016-09-09 Thread Django

#27205: Django Postgres ArrayField __contain lookup does not behave expectedly
-+-
 Reporter:  Dean-Christian-  |Owner:  nobody
  Armada |
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql,  | Triage Stage:
  arrayfield |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I guess may be similar to #26511.

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

Re: [Django] #25415: Make DiscoverRunner run system checks

2016-09-09 Thread Django

#25415: Make DiscoverRunner run system checks
---+
 Reporter:  adamchainz |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  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 Tim Graham ):

 In [changeset:"652bcc6f5fa9084768890488fec5208e082c2add" 652bcc6f]:
 {{{
 #!CommitTicketReference repository=""
 revision="652bcc6f5fa9084768890488fec5208e082c2add"
 Refs #25415 -- Fixed invalid models in the test suite.
 }}}

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

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

[Django] #27205: Django Postgres ArrayField __contain lookup does not behave expectedly

2016-09-09 Thread Django

#27205: Django Postgres ArrayField __contain lookup does not behave expectedly
--+
 Reporter:  Dean-Christian-Armada |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.10
 Severity:  Normal|   Keywords:  postgresql,
  |  arrayfield
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 This is my models.py:


 {{{
 class Dog(models.Model):
 name = models.CharField(max_length=200)
 data = JSONField()

 def __unicode__(self):
 return self.name
 }}}

 I did this in the django shell:



 {{{
 Dog.objects.create(name='Rufus', data={ 'breed': 'labrador', 'owner': {
 'name': 'Bob', 'other_pets': [{  'name': 'Fishy',  }], }, })
 Dog.objects.create(name='Meg', data={'breed': 'collie'})
 Dog.objects.filter(data__breed__contains='l')

 }}}


 However when I did the last command it gave me an empy queryset return:


 {{{
 

 }}}


 The two objects (Meg and Rufus) should have both returned because they
 both contain l

 This is the query of the ORM:


 {{{
 SELECT "post_tagging_dog"."id", "post_tagging_dog"."name",
 "post_tagging_dog"."data" FROM "post_tagging_dog" WHERE
 "post_tagging_dog"."data" -> 'breed' @> '"l"'

 }}}

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

Re: [Django] #27204: Clashing m2m intermediate table validation should ignore unmanaged models

2016-09-09 Thread Django

#27204: Clashing m2m intermediate table validation should ignore unmanaged 
models
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (System checks)  |  Version:  1.10
 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
--+
Changes (by timgraham):

 * Attachment "27204.diff" added.

 patch without tests

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

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

[Django] #27204: Clashing m2m intermediate table validation should ignore unmanaged models

2016-09-09 Thread Django

#27204: Clashing m2m intermediate table validation should ignore unmanaged
models
+
Reporter: timgraham | Owner: nobody
Type: Bug | Status: new
Component: Core (System checks) |Version: 1.10
Severity: Normal| Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 |Needs tests: 1
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
+
The check added in #12810 currently triggers on some unmanaged models in
Django's test suite that intentionally use clashing names. I think the
correct solution is to ignore unmanaged models.

ERRORS:
model_options.Article.authors: (fields.E340) The field's intermediary
table 'model_options_articleref_authors' clashes with the table name of
'model_options.ArticleRef.authors'.
model_options.Article.reviewers: (fields.E340) The field's intermediary
table 'model_options_articleref_reviewers' clashes with the table name of
'model_options.ArticleRef.reviewers'.
model_options.ArticleRef.authors: (fields.E340) The field's intermediary
table 'model_options_articleref_authors' clashes with the table name of
'model_options.Article.authors'.
model_options.ArticleRef.reviewers: (fields.E340) The field's intermediary
table 'model_options_articleref_reviewers' clashes with the table name of
'model_options.Article.reviewers'.
unmanaged_models.C01.mm_a: (fields.E340) The field's intermediary table
'd01' clashes with the table name of 'unmanaged_models.Intermediate'.
unmanaged_models.C02.mm_a: (fields.E340) The field's intermediary table
'd01' clashes with the table name of 'unmanaged_models.C01.mm_a'.

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

Re: [Django] #18763: Shortcut to get users by permission

2016-09-09 Thread Django

#18763: Shortcut to get users by permission
--+
 Reporter:  shelldweller  |Owner:  berkerpeksag
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #27063: Regex url routing + Localization (prefix_default_language)

2016-09-09 Thread Django

#27063: Regex url routing + Localization (prefix_default_language)
--+
 Reporter:  keithhackbarth|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  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 jayk140):

 @urbaniak - As discussed, I added a test for the case in which the
 language code is prefixed with a `-` (i.e de-test-parking). With your
 updated code and new language_code_prefix_re, the test passes now as
 expected results of 200 with language code of 'en'. The case of stacking
 language prefixes now returns the expected 404 as well.

 Thanks for the help!

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

[Django] #27203: Update tests that use assertQuerysetEqual lambda o: o to use assertSequenceEqual

2016-09-09 Thread Django

#27203: Update tests that use assertQuerysetEqual lambda o: o to use
assertSequenceEqual
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  1.10
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 For example:
 {{{ #!diff
 diff --git a/tests/expressions/tests.py b/tests/expressions/tests.py
 index 27929c9..459d317 100644
 --- a/tests/expressions/tests.py
 +++ b/tests/expressions/tests.py
 @@ -94,7 +94,7 @@ class BasicExpressionsTests(TestCase):
  # We can set one field to have the value of another field
  # Make sure we have enough chairs
  self.company_query.update(num_chairs=F("num_employees"))
 -self.assertQuerysetEqual(
 +self.assertSequenceEqual(
  self.company_query, [
  {
  "num_chairs": 2300,
 @@ -112,7 +112,6 @@ class BasicExpressionsTests(TestCase):
  "num_employees": 32
  }
  ],
 -lambda o: o
  )

  def test_arithmetic(self):
 }}}
 When searching for cases to replace, there might be other letters besides
 'o' in `lambda o: o`.

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

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

2016-09-09 Thread Django

#27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with
double slash
--+
 Reporter:  andrewbadr|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.staticfiles   |  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):

 I'm not aware of what the rules are for valid file paths. Could you cite a
 spec or something so we know what cases to support?

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

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

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

2016-09-09 Thread Django

#27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with
double slash
--+
 Reporter:  andrewbadr|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.staticfiles   |  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 andrewbadr):

 @timgraham, I don't think "break on completely valid file paths" is an
 acceptable answer here. Something in Django is failing to handle valid
 paths correctly—that thing should be fixed, either by normalizing the
 paths so it can understand them, or making it smart enough to handle non-
 normalized paths.

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

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

Re: [Django] #27062: Add support for for_update for MSSQL

2016-09-09 Thread Django

#27062: Add support for for_update for MSSQL
-+-
 Reporter:  denisenkom   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  mssql for_update | Triage Stage:  Ready for
  database orm   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"bae64dd0f13ba247448197ecf83cdc7a80691bb4" bae64dd0]:
 {{{
 #!CommitTicketReference repository=""
 revision="bae64dd0f13ba247448197ecf83cdc7a80691bb4"
 Fixed #27062 -- Eased implementing select_for_update() on MSSQL.
 }}}

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

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

Re: [Django] #26149: Invalid migration generated when using order_with_respect_to and a unique_together constraint

2016-09-09 Thread Django

#26149: Invalid migration generated when using order_with_respect_to and a
unique_together constraint
+--
 Reporter:  richardxia  |Owner:  anabelensc
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+--
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * needs_tests:  1 => 0


Comment:

 [https://github.com/django/django/pull/7053 PR] with the attached patch,
 but there's no discussion about why that solution is preferred despite the
 previous comment.

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

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

Re: [Django] #9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string

2016-09-09 Thread Django

#9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string
--+
 Reporter:  mtredinnick   |Owner:
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.0
 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):

 A [https://github.com/django/django/pull/6978 PR] with some discussion of
 this issue.

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

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

Re: [Django] #25251: Inconsistent availability of data migrations in TransactionTestCase when using --keepdb

2016-09-09 Thread Django

#25251: Inconsistent availability of data migrations in TransactionTestCase when
using --keepdb
---+
 Reporter:  davidszotten   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 The test isn't passing.

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

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

Re: [Django] #27159: Pickling query from queryset causes unintended queryset evaluation

2016-09-09 Thread Django

#27159: Pickling query from queryset causes unintended queryset evaluation
-+-
 Reporter:  jtiai|Owner:  DavidFozo
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #27098: Deprecate DatabaseIntrospection.get_indexes

2016-09-09 Thread Django

#27098: Deprecate DatabaseIntrospection.get_indexes
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  introspection db-| Triage Stage:  Ready for
  indexes|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

Re: [Django] #27197: Document how blank=True affects the migrations questioner

2016-09-09 Thread Django

#27197: Document how blank=True affects the migrations questioner
-+-
 Reporter:  jarekwg  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  CharField blank  | Triage Stage:
  emptystring|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Discussion to continue on [https://groups.google.com/d/topic/django-
 developers/upbDlFgtCHs/discussion django-developers].

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

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

2016-09-09 Thread Django

#27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with
double slash
--+
 Reporter:  andrewbadr|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.staticfiles   |  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):

 * cc: aaugustin (added)
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I don't see a compelling reason to restore support for typos like this,
 but a more helpful error message could be nice, so I'd go with option (c)
 absent other arguments.

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

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

Re: [Django] #27199: Integer inputs marked as type="text" instead of type="number"

2016-09-09 Thread Django

#27199: Integer inputs marked as type="text" instead of type="number"
-+-
 Reporter:  renskiy  |Owner:  renskiy
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ca9c69a9682141bc102ad6751f2feecc3d0d9d21" ca9c69a9]:
 {{{
 #!CommitTicketReference repository=""
 revision="ca9c69a9682141bc102ad6751f2feecc3d0d9d21"
 Fixed #27199 -- Made AdminIntegerFieldWidget use NumberInput.
 }}}

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

Re: [Django] #27202: Investigate RenameMethodsBase effect on yaml serialization (was: yaml dump for django.forms.Field crashes with "TypeError: can't pickle int objects")

2016-09-09 Thread Django

#27202: Investigate RenameMethodsBase effect on yaml serialization
---+
 Reporter:  semenov|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords:  yaml   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Utilities
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Fixed in Django 1.10 by a3fe4addcb9063fc327c8609c7ebba4d531da4ce.
 Unfortunately, Django 1.8 and 1.9 are only receiving security and data
 loss fixes by now. Perhaps it's worth investigating the cause of this
 (`RenameMethodsBase`, possibly) to try to prevent future regressions.

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

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

2016-09-09 Thread Django

#27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with
double slash
-+-
 Reporter:  andrewbadr   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  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 edmorley):

 As part of #26249, a `posixpath.normpath()` was removed:
 
https://github.com/django/django/commit/7f6fbc906a21e9f8db36e06ace2a9b687aa26130
 #diff-c7242dedd7c93b857a668acec1e310feL179

 ...which would have previously been fixing the path like so:
 {{{
 >>> import posixpath
 >>> posixpath.normpath('/static//fonts/crimson/CrimsonText-Bold.ttf')
 '/static/fonts/crimson/CrimsonText-Bold.ttf'
 }}}

 The argument made in that commit was that "it's mostly an aesthetic issue
 and it isn't Django's job to fix it".

 It would seem that either:
 (a) this commit should be reverted
 (b) `safe_join()`'s checks should perform a `normpath()` to avoid the
 `SuspiciousFileOperation` and continue supporting these kind of typos
 (c) the decision to fail in this case should be formalised and ideally a
 clearer exception given instead of `SuspiciousFileOperation`

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

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

[Django] #27202: yaml dump for django.forms.Field crashes with "TypeError: can't pickle int objects"

2016-09-09 Thread Django

#27202: yaml dump for django.forms.Field crashes with "TypeError: can't pickle 
int
objects"
---+
 Reporter:  semenov|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:  yaml
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Django 1.7.10, PyYAML 3.11 (Python 3.4):

 {{{
 >>> import yaml
 >>> from django import forms
 >>> yaml.dump(forms.ChoiceField)
 "!!python/name:django.forms.fields.ChoiceField ''\n"
 }}}

 Django 1.8.14, PyYAML 3.11 (Python 3.5):

 {{{
 >>> import yaml
 >>> from django import forms
 >>> yaml.dump(forms.ChoiceField)
 Traceback (most recent call last):
   File "", line 1, in 
   File "/Users/semenov/work/test/var/venv/lib/python3.5/site-
 packages/yaml/__init__.py", line 200, in dump
 return dump_all([data], stream, Dumper=Dumper, **kwds)
   File "/Users/semenov/work/test/var/venv/lib/python3.5/site-
 packages/yaml/__init__.py", line 188, in dump_all
 dumper.represent(data)
   File "/Users/semenov/work/test/var/venv/lib/python3.5/site-
 packages/yaml/representer.py", line 26, in represent
 node = self.represent_data(data)
   File "/Users/semenov/work/test/var/venv/lib/python3.5/site-
 packages/yaml/representer.py", line 51, in represent_data
 node = self.yaml_multi_representers[data_type](self, data)
   File "/Users/semenov/work/test/var/venv/lib/python3.5/site-
 packages/yaml/representer.py", line 313, in represent_object
 reduce = data.__reduce_ex__(2)
   File "/Users/semenov/work/test/var/venv/lib/python3.5/copyreg.py", line
 65, in _reduce_ex
 raise TypeError("can't pickle %s objects" % base.__name__)
 TypeError: can't pickle int objects
 }}}

 Anything we can do to have Django class types YAML-compatible again?

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

Re: [Django] #27205: Django Postgres ArrayField __contain lookup does not behave expectedly

Re: [Django] #27204: Clashing m2m intermediate table validation should ignore unmanaged models

Re: [Django] #27204: Clashing m2m intermediate table validation should ignore unmanaged models

Re: [Django] #27204: Clashing m2m intermediate table validation should ignore unmanaged models

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

Re: [Django] #27205: Django Postgres ArrayField __contain lookup does not behave expectedly

Re: [Django] #25415: Make DiscoverRunner run system checks

[Django] #27205: Django Postgres ArrayField __contain lookup does not behave expectedly

Re: [Django] #27204: Clashing m2m intermediate table validation should ignore unmanaged models

[Django] #27204: Clashing m2m intermediate table validation should ignore unmanaged models

Re: [Django] #18763: Shortcut to get users by permission

Re: [Django] #27063: Regex url routing + Localization (prefix_default_language)

[Django] #27203: Update tests that use assertQuerysetEqual lambda o: o to use assertSequenceEqual

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

Re: [Django] #27062: Add support for for_update for MSSQL

Re: [Django] #26149: Invalid migration generated when using order_with_respect_to and a unique_together constraint

Re: [Django] #9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string

Re: [Django] #25251: Inconsistent availability of data migrations in TransactionTestCase when using --keepdb

Re: [Django] #27159: Pickling query from queryset causes unintended queryset evaluation

Re: [Django] #27098: Deprecate DatabaseIntrospection.get_indexes

Re: [Django] #27197: Document how blank=True affects the migrations questioner

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

Re: [Django] #27199: Integer inputs marked as type="text" instead of type="number"

Re: [Django] #27202: Investigate RenameMethodsBase effect on yaml serialization (was: yaml dump for django.forms.Field crashes with "TypeError: can't pickle int objects")

Re: [Django] #27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with double slash

[Django] #27202: yaml dump for django.forms.Field crashes with "TypeError: can't pickle int objects"

27 matches

Site Navigation

Mail list logo

Footer information