Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2016-12-29 Thread Django 
#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  Germano Gabbianelli  |Owner:  Johannes
 |  Hoppe
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by James Pic):

 Ok so I was wrong, here's the new ticket for this issue:
 https://github.com/select2/select2/issues/4733

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

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2016-12-29 Thread Django 
#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  Germano Gabbianelli  |Owner:  Johannes
 |  Hoppe
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by James Pic):

 This is the code that does the trick for me: https://github.com/yourlabs
 /django-autocomplete-
 light/blob/master/src/dal_select2/static/autocomplete_light/select2.js#L91-L97

 {{{
 // Remove this block when this is merged upstream:
 // https://github.com/select2/select2/pull/4249
 $(document).on('DOMSubtreeModified', '[data-autocomplete-light-
 function=select2] option', function() {
 $(this).parents('select').next().find(
 '.select2-selection--single .select2-selection__rendered'
 ).text($(this).text());
 });
 }}}


 Just replace `[data-autocomplete-light-function=select2]` by your own
 select tag selector and you should be good to go.

 However, it was meant as a temporary fix even for DAL, so I'm not sure if
 this is of any help to you. I would suggest to add a breakpoint somewhere
 in the code that Kevin's patch adds or changes and hopefully if it's
 executed at all then the solution should be easy to find.

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

Re: [Django] #27615: Use native interval type on Oracle

2016-12-29 Thread Django 
#27615: Use native interval type on Oracle
-+-
 Reporter:  Tim Graham   |Owner:  felixxm
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  oracle   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"7d14889aa3b0897a902034d1d11b8195463da32c" 7d14889]:
 {{{
 #!CommitTicketReference repository=""
 revision="7d14889aa3b0897a902034d1d11b8195463da32c"
 Fixed #27615 -- Used timedeltas as arguments to Oracle database driver.

 Removed unused DatabaseFeatures.driver_supports_timedeltas 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/067.6eeea2f3a69160839c8480d3df641286%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #8500: Allow overriding of default adminsite.

2016-12-29 Thread Django 
#8500: Allow overriding of default adminsite.
+
 Reporter:  oyvind  |Owner:  oyvind
 Type:  New feature |   Status:  new
Component:  contrib.admin   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  override adminsite  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+

Comment (by Raffaele Salmaso):

 Added a PR => https://github.com/django/django/pull/7765

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

Re: [Django] #27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL parameters as well

2016-12-29 Thread Django 
#27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL
parameters as well
-+-
 Reporter:  Markus Holtermann|Owner:  Markus
 Type:   |  Holtermann
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Markus Holtermann):

 * has_patch:  0 => 1


Comment:

 PR: https://github.com/django/django/pull/7764

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

Re: [Django] #27652: Humanize docs should clarify: Floats OK too!

2016-12-29 Thread Django 
#27652: Humanize docs should clarify: Floats OK too!
--+
 Reporter:  Mike Lissner  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


Comment:

 I forgot to say there are only tests for floats for `intcomma`. In my
 testing, `intword` doesn't support floats. '100.1' gives the same
 value back rather than "1 million". This seems fine to me but the PR must
 be corrected.

--
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.24fb34461e730ef35b2a06ebc889267b%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-12-29 Thread Django 
#9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string
+
 Reporter:  Malcolm Tredinnick  |Owner:  (none)
 Type:  Bug |   Status:  new
Component:  Core (Other)|  Version:  1.0
 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 Tim Graham):

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

Re: [Django] #27665: More than one instance of Chrome locks up LiveServerTestCase

2016-12-29 Thread Django 
#27665: More than one instance of Chrome locks up LiveServerTestCase
---+--
 Reporter:  Luke Plant |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.10
 Severity:  Normal |   Resolution:  duplicate
 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 Luke Plant):

 That sounds good - thanks (assuming my guess about the cause is correct).

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

Re: [Django] #20238: Support multiple open connections in LiveServerTestCase

2016-12-29 Thread Django 
#20238: Support multiple open connections in LiveServerTestCase
---+
 Reporter:  jwxiao@…   |Owner:  Nadege
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  1.4
 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):

 Support for multiple open connections is also needed if you want to write
 a test that uses multiple browser instances as demonstrated in #27665
 (closed as duplicate).

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

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

Re: [Django] #27665: More than one instance of Chrome locks up LiveServerTestCase

2016-12-29 Thread Django 
#27665: More than one instance of Chrome locks up LiveServerTestCase
---+--
 Reporter:  Luke Plant |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.10
 Severity:  Normal |   Resolution:  duplicate
 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 Tim Graham):

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


Comment:

 #20238 is open to support multiple open connections in
 `LiveServerTestCase`. Can we consider this a duplicate of that?

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

[Django] #27665: More than one instance of Chrome locks up LiveServerTestCase

2016-12-29 Thread Django 
#27665: More than one instance of Chrome locks up LiveServerTestCase
-+
   Reporter:  Luke Plant |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing framework  |Version:  1.10
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Example code:
 {{{
 from django.test import LiveServerTestCase
 from selenium import webdriver

 class TestChrome(LiveServerTestCase):

 def test(self):
 url = self.live_server_url
 driver1 = webdriver.Chrome()
 driver1.get(url)
 driver1.get(url)  # This 2nd get seems to be needed to trigger the
 bug

 driver2 = webdriver.Chrome()
 driver2.get(url)

 driver1.quit()
 driver2.quit()
 }}}
 This code was added to `tests.py` in an otherwise blank project (no views
 or anything necessary), and run using `./manage.py test`

 Result: the second Chrome window simply hangs trying to load the URL.

 Tested with:
 * Django 1.10.4
 * Selenium 2.53.6
 * Chrome 55.0.2883.87 (Official Build) (64-bit)
 * ChromeDriver 2.27.440175 (9bc1d90b8bfa4dd181fbbf769a5eb5e575574320)

 Upgrading to Selenium 3 is not an option - so many things are broken (like
 any half-decent Firefox support, as far as I can tell).

 I'm guessing this might be to do with Chrome holding open connections. If
 I close the first Chrome window, the second one then succeeds to load the
 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/054.022d1055bf6dacd117a0f1e557d87f94%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27649: Increase minimum supported cx_Oracle version to 5.2

2016-12-29 Thread Django 
#27649: Increase minimum supported cx_Oracle version to 5.2
-+-
 Reporter:  Tim Graham   |Owner:  Tim
 Type:   |  Graham
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  oracle cx_oracle | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"fae56427e1987ff8c8bd24d6331007f9c53e7abc" fae56427]:
 {{{
 #!CommitTicketReference repository=""
 revision="fae56427e1987ff8c8bd24d6331007f9c53e7abc"
 Fixed #27649 -- Bumped required cx_Oracle to 5.2.

 Removed obsolete workarounds from 1aa48898085ea16915877cc139e238a74e3f554b
 and dcf3be7a621f011a918453527406216a738acf68.
 }}}

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

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

2016-12-29 Thread Django 
#25415: Make DiscoverRunner run system checks
---+
 Reporter:  Adam Chainz|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"5eff8a77838540b27b6bef024dfccfd76008fd4c" 5eff8a77]:
 {{{
 #!CommitTicketReference repository=""
 revision="5eff8a77838540b27b6bef024dfccfd76008fd4c"
 Fixed #25415 -- Made DiscoverRunner run system checks.
 }}}

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

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2016-12-29 Thread Django 
#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  Germano Gabbianelli  |Owner:  Johannes
 |  Hoppe
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Johannes Hoppe):

 @James

 yes, but that only works for actual option tags doesn't it? In this case
 the we are only using a JSON API and the dynamic options.
 I haven't looked into that yet. You are a better JS coder than me. I would
 greatly appreciate a patch or suggestion form your side.

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

Re: [Django] #27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL parameters as well

2016-12-29 Thread Django 
#27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL
parameters as well
-+-
 Reporter:  Markus Holtermann|Owner:  Markus
 Type:   |  Holtermann
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * severity:  Normal => Release blocker
 * 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/065.0857382a6e2738a29a669d3449b31497%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2016-12-29 Thread Django 
#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  Germano Gabbianelli  |Owner:  Johannes
 |  Hoppe
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by James Pic):

 I thought this was supported upstream:
 
https://github.com/select2/select2/commit/ea79a197e0ffe55aa600eed6d18cbd1c804c3176

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

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

2016-12-29 Thread Django 
#25415: Make DiscoverRunner run system checks
---+
 Reporter:  Adam Chainz|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:"391c450fbae8c3301954563288147578a1ae4a6d" 391c450]:
 {{{
 #!CommitTicketReference repository=""
 revision="391c450fbae8c3301954563288147578a1ae4a6d"
 Refs #25415 -- Made MySQL backend skip field validation of unsupported
 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/068.4ce7a8b4acacd0ad6ffd7f757cdef291%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27664: Manager.contribute_to_class() is called with abstract model rather than concrete model

2016-12-29 Thread Django 
#27664: Manager.contribute_to_class() is called with abstract model rather than
concrete model
-+-
 Reporter:  Johannes Hoppe   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Johannes Hoppe):

 Hi Tim,

 I agree, it is not documented, but I guess it's not to uncommon for third
 party libraries to make use of `contribute_to_class` be it on `Managers`
 or `Fields`.

 Regardless, the documentation says, that the manager will be inherited. So
 I would presume the having the attribute on a super class is the same than
 having the attribute on the sub class.

 This is not the case.

 I'm not sure if this is just a matter of documentation or if it should be
 changed. My first guess would be to change it. It seems more intuitive to
 me. But I really like the that the new Manager design is less complex. If
 there isn't an easy solution. This shouldn't be changed.

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

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2016-12-29 Thread Django 
#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  Germano Gabbianelli  |Owner:  Johannes
 |  Hoppe
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


Comment:

 As Florian noted on the PR, "Using the "edit"-icon next to a FK does not
 update the autocomplete widget."

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

Re: [Django] #27649: Increase minimum supported cx_Oracle version to 5.2

2016-12-29 Thread Django 
#27649: Increase minimum supported cx_Oracle version to 5.2
-+-
 Reporter:  Tim Graham   |Owner:  Tim
 Type:   |  Graham
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle cx_oracle | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * keywords:   => oracle cx_oracle
 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #27664: Manager.contribute_to_class() is called with abstract model rather than concrete model (was: contribute_to_class is called with wrong model class)

2016-12-29 Thread Django 
#27664: Manager.contribute_to_class() is called with abstract model rather than
concrete model
-+-
 Reporter:  Johannes Hoppe   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

Re: [Django] #27664: contribute_to_class is called with wrong model class

2016-12-29 Thread Django 
#27664: contribute_to_class is called with wrong model class
-+-
 Reporter:  Johannes Hoppe   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * cc: Loic Bistuer (added)


Comment:

 This changed in 3a47d42fa33012b2156bf04058d933df6b3082d2 - Fixed #20932,
 #25897 -- Streamlined manager inheritance.

 I'm uncertain if the new behavior is intended or if it needs clarification
 in the release notes, however, as far as I know `contribute_to_class()` is
 a private API so backwards compatibility and documentation changes there
 isn't a high priority.

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

[Django] #27664: contribute_to_class is called with wrong model class

2016-12-29 Thread Django 
#27664: contribute_to_class is called with wrong model class
-+-
   Reporter:  Johannes   |  Owner:  nobody
  Hoppe  |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.10
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Since 1.10 `Manager.contribute_to_class` gets called with the model on
 which the manager is defined instead of the subclass.
 Before that it used to be called for all sub models with the proper class.

 You can easily reproduce that by running this in both version 1.9 and
 1.10. `model` will be different.

 {{{
 class MyManager(models.Manager):

  def contribute_to_class(self, model, name):
  super().contribute_to_class(model, name)
  print(model)

 class AbstractModel(models.Model):
 objects = MyManager()
 class Meta:
 abstract = True

 class ContcreteModel(AbstractModel):
 pass
 }}}

 This change has not been documented in the release notes and also seems
 counter intuitive. Contribute to class should be called with the concrete
 model.

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

Re: [Django] #27656: Fix comment verb style according to PEP 257

2016-12-29 Thread Django 
#27656: Fix comment verb style according to PEP 257
-+-
 Reporter:  Anton Samarchyan |Owner:  Anton
 Type:   |  Samarchyan
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Anton Samarchyan):

 Here's a [https://github.com/django/django/pull/7763 PR] with work in
 progress. Made changes to one file.

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

Re: [Django] #26478: Prohibit quotes and vertical bar in {% for %} unpacking variable names (was: Template Context should validate names)

2016-12-29 Thread Django 
#26478: Prohibit quotes and vertical bar in {% for %} unpacking variable names
-+-
 Reporter:  Stephen Kelly|Owner:  Tim
 Type:   |  Martin
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  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 Tim Graham):

 * type:  New feature => Cleanup/optimization
 * stage:  Accepted => Ready for checkin


Comment:

 I'm unsure about further changes, I think we can go with your patch for
 now.

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

Re: [Django] #27656: Fix comment verb style according to PEP 257

2016-12-29 Thread Django 
#27656: Fix comment verb style according to PEP 257
-+-
 Reporter:  Anton Samarchyan |Owner:  Anton
 Type:   |  Samarchyan
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Anton Samarchyan):

 * owner:  nobody => Anton Samarchyan
 * 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/065.c08d8a7ab5e517fbdf0b6292836b5605%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL parameters as well

2016-12-29 Thread Django 
#27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL
parameters as well
-+-
 Reporter:  Markus Holtermann|Owner:  Markus
 Type:   |  Holtermann
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 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 Markus Holtermann):

 * status:  new => assigned
 * owner:  nobody => Markus Holtermann


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

[Django] #27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL parameters as well

2016-12-29 Thread Django 
#27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL
parameters as well
+
   Reporter:  Markus Holtermann |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Migrations|Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Looking into #26167, I noticed that, in order to eventually have something
 like `FunctionalIndex(Concat(Lower(Ref('some_field', None)),
 Value('x')))`, Django needs to return the params for the SQL query and
 pass them to the SchemaEditor's `execute()` method.

 When constructing the SQL for the expression
 `Concat(Lower(Ref('some_field', None)), Value('x')).as_sql(...)`, Django
 returns the SQL with placeholders for the values:
 {{{#!python
 >>> Concat(Lower(Ref('some_field', None)), Value('x')).as_sql(compiler,
 connection)
 ('CONCAT(LOWER("some_field"), %s)', ['x'])
 }}}

 Since the whole API for `Index.create_sql()` and
 `SchemaEditor.add_index()` etc. API is new in Django 1.11 let's try to get
 ahead of a necessary deprecation at a later time by passing the SQL
 statement and empty params by default, for now.

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

Re: [Django] #27661: Move FileSystemFinder ImproperlyConfigured errors to system checks

2016-12-29 Thread Django 
#27661: Move FileSystemFinder ImproperlyConfigured errors to system checks
--+
 Reporter:  Jerome Leclanche  |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:  1 |UI/UX:  0
--+
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #26355: Add support for PostgreSQL's array_append to ArrayField

2016-12-29 Thread Django 
#26355: Add support for PostgreSQL's array_append to ArrayField
--+
 Reporter:  Paul Grau |Owner:  khorne
 Type:  New feature   |   Status:  assigned
Component:  contrib.postgres  |  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 Tim Graham):

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

Re: [Django] #27332: Specifying additional ON arguments, and more flexibility with joins

2016-12-29 Thread Django 
#27332: Specifying additional ON arguments, and more flexibility with joins
-+-
 Reporter:  MikiSoft |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 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 Tim Graham):

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

Re: [Django] #27662: test suite fails in the last week of a leap year

2016-12-29 Thread Django 
#27662: test suite fails in the last week of a leap year
+--
 Reporter:  Hartmut Goebel  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Utilities   |  Version:  1.10
 Severity:  Normal  |   Resolution:  duplicate
 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 Tim Graham):

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


Comment:

 Duplicate of #27637 (already fixed in master, stable/1.10.x, and
 stable/1.9.x branches).

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

[Django] #27662: test suite fails in the last week of a leap year

2016-12-29 Thread Django 
#27662: test suite fails in the last week of a leap year
--+
   Reporter:  Hartmut Goebel  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Utilities   |Version:  1.10
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 When running the test suite in the last week of a leap year, some tests
 fail. This is due to a subtle bug in timesince().

 This bug **only** occurs if "now" is in a leap year and "d" (the date to
 be compared with now) is not. The test suite contains tests for comparing
 "now" with "now+oneweek", which is why this test fails only in the last
 week of a lead year.

 This test-case test for this bug. Just add it to
 "tests/utils_tests/test_timesince.py":
 {{{
 def test_year_boundry_current_is_leapyear(self):
 "Current year is a leap year, and next week is in next year"
 today = datetime.date(2016, 12, 28) # within the last week of a
 leap year
 self.assertEqual(timeuntil(today + self.oneweek, today),
 '1\xa0week')
 }}}

 "today" (2016) is in a leap year, while "today+oneweek" will be 2017-01-05
 which is not in a leap year.

 The bug is caused by django/utils/timesince.py, line 46:
 {{{
delta -= datetime.timedelta(calendar.leapdays(d.year, now.year))
 }}}

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

[Django] #27661: Move FileSystemFinder ImproperlyConfigured errors to system checks

2016-12-29 Thread Django 
#27661: Move FileSystemFinder ImproperlyConfigured errors to system checks
+
   Reporter:  Jerome Leclanche  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.staticfiles   |Version:  1.10
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 FileSystemFinder currently checks for the following on `__init__`:

 - Whether STATICFILES_DIRS is a list or tuple, failing if it's not
 - Whether STATICFILES_DIRS contains a directory equivalent to STATIC_ROOT

 I'd like to suggest moving both of those checks to the Django system
 checks framework. As it is, they happen at runtime which delays when the
 error shows up.

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

Re: [Django] #27622: Test client should accept vendor tree json variants

2016-12-29 Thread Django 
#27622: Test client should accept vendor tree json variants
-+-
 Reporter:  John Gresty  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  json vendor  | Triage Stage:  Ready for
  testing_client |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"0b5d4c49d652ba7156b8998cec142ea4f4c55d58" 0b5d4c49]:
 {{{
 #!CommitTicketReference repository=""
 revision="0b5d4c49d652ba7156b8998cec142ea4f4c55d58"
 Fixed #27622 -- Allowed test client to accept vendor tree JSON content
 types.
 }}}

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

Re: [Django] #27622: Test client should accept vendor tree json variants (was: Testing client should accept vendor tree json variants)

2016-12-29 Thread Django 
#27622: Test client should accept vendor tree json variants
-+-
 Reporter:  John Gresty  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  json vendor  | Triage Stage:  Ready for
  testing_client |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #27657: Getting crash when using the runserver command on Windows 10 in PowerShell following update to Python 3.6

2016-12-29 Thread Django 
#27657: Getting crash when using the runserver command on Windows 10 in 
PowerShell
following update to Python 3.6
+--
 Reporter:  horatius83  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Utilities   |  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 Tim Graham):

 So `sys.argv` is the tuple, I guess? It doesn't seem that Django is
 necessarily at fault. Could you investigate the issue a bit more to
 determine what's causing it to be a tuple rather than a list?

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

Re: [Django] #27653: Improvement of Ukrainian locale formats

2016-12-29 Thread Django 
#27653: Improvement of Ukrainian locale formats
-+-
 Reporter:  Illia Volochii   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:   |  Version:
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  local, formats,  | Triage Stage:  Accepted
  Ukrainian  |
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:"d20e046bbd7417c043f40d5fb8ebab863595b3eb" d20e046]:
 {{{
 #!CommitTicketReference repository=""
 revision="d20e046bbd7417c043f40d5fb8ebab863595b3eb"
 Fixed #27653 -- Added Ukrainian locale formats.
 }}}

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

Re: [Django] #25192: Can't Squash Migration that uses migrations.RunPython.noop in Python 2

2016-12-29 Thread Django 
#25192: Can't Squash Migration that uses migrations.RunPython.noop in Python 2
-+
 Reporter:  James Pulec  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  py2  | 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:  new => closed
 * resolution:   => wontfix


Comment:

 Closing due to the end of Python 2 support in master in a couple weeks.

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

Re: [Django] #26731: UnicodeDecodeError when writing unicode to stdout of management command

2016-12-29 Thread Django 
#26731: UnicodeDecodeError when writing unicode to stdout of management command
-+-
 Reporter:  Darren Hobbs |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8
  commands)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  py2  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Closing due to the end of Python 2 support in master in a couple weeks.

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

Re: [Django] #24949: Force to_field and probably other fields to unicode during migration deconstruction

2016-12-29 Thread Django 
#24949: Force to_field and probably other fields to unicode during migration
deconstruction
---+
 Reporter:  Markus Holtermann  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.7
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  py2| 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:  new => closed
 * resolution:   => wontfix


Comment:

 Closing due to the end of Python 2 support in master in a couple weeks.

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

Re: [Django] #23222: Empty BinaryField != b'' on Python 2

2016-12-29 Thread Django 
#23222: Empty BinaryField != b'' on Python 2
-+-
 Reporter:  wkschwartz@… |Owner:  Grzegorz
 |  Ślusarek
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  py2  | 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:   => wontfix


Comment:

 Closing due to the end of Python 2 support in master in a couple weeks.

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

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

Re: [Django] #27635: django.utils.crypto should use secrets on Python 3.6+

2016-12-29 Thread Django 
#27635: django.utils.crypto should use secrets on Python 3.6+
-+-
 Reporter:  Adam Chainz  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  1 => 0
 * stage:  Accepted => Someday/Maybe


Comment:

 Python's `secrets.py` does `from random import SystemRandom` so this
 doesn't change any behavior or add security for now. Adam said,
 "Presumably the intention is that secrets might one day use a different
 PRNG's on some OS's." Let's make the change if the benefits become more
 than theoretical or when only Python 3.6+ is supported.

 Another possibility Aymeric mentioned, "In the long run I think we should
 deprecate get_random_string in favor of similar functions provided by the
 secrets module. I didn't check whether there was a sensible transition
 plan to make use of secrets on Python 3.6 while still supporting older
 versions."

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

Re: [Django] #27658: collectstatic overwrites newer files in remote storage

2016-12-29 Thread Django 
#27658: collectstatic overwrites newer files in remote storage
-+-
 Reporter:  pgcd |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  staticfiles  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * easy:  1 => 0


Comment:

 Could you be more specific about the steps to reproduce the issue (ideally
 without S3 involved since Django's test suite cannot rely on that)? If you
 could provide a test case for `tests/staticfiles_tests` that would be
 great.

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

Re: [Django] #27660: clean() not called on ModelForm for UpdateView

2016-12-29 Thread Django 
#27660: clean() not called on ModelForm for UpdateView
-+-
 Reporter:  Benjamin von |Owner:  nobody
  Deschwanden|
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.10
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  ModelForm,   | Triage Stage:
  UpdateView, clean()|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Benjamin von Deschwanden):

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


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

Re: [Django] #27652: Humanize docs should clarify: Floats OK too!

2016-12-29 Thread Django 
#27652: Humanize docs should clarify: Floats OK too!
--+
 Reporter:  Mike Lissner  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Mads Jensen):

 * has_patch:  0 => 1


Comment:

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

[Django] #27660: clean() not called on ModelForm for UpdateView

2016-12-29 Thread Django 
#27660: clean() not called on ModelForm for UpdateView
-+-
   Reporter:  Benjamin   |  Owner:  nobody
  von Deschwanden|
   Type:  Bug| Status:  new
  Component:  Forms  |Version:  1.10
   Severity:  Normal |   Keywords:  ModelForm,
   Triage Stage: |  UpdateView, clean()
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I am using a ModelForm as the 'form' attribute of an UpdateView.
 Overriding the clean() method of the ModelForm does not work; the method
 does not seem to be called. The undesired behavior can be reconstructed as
 follows:

 - Set up new django project
 - Create view and form:

 {{{
 class RouteUpdate(UpdateView):
 model = Route
 form_class = RouteForm

 class RouteForm(ModelForm):
 class Meta:
 model = Route
 fields = [...]

 def clean(self):
 cleaned_data = super(RouteForm, self).clean()
 print("This method will not be executed...")
 return cleaned_data
 }}}

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

Re: [Django] #27659: Arbritrary file overrides in startproject/app template extraction

2016-12-29 Thread Django 
#27659: Arbritrary file overrides in startproject/app template extraction
---+
 Reporter:  Florian Apolloner  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Florian Apolloner):

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

[Django] #27659: Arbritrary file overrides in startproject/app template extraction

2016-12-29 Thread Django 
#27659: Arbritrary file overrides in startproject/app template extraction
-+
   Reporter:  Florian Apolloner  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Utilities  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Note: This was reported as security issue intially by me, but we think
 that this is more hardening than an actual issue -- if you are downloading
 untrusted archives the content can be much worse anyways…

 The issue here is that tar files (and probably zip files too), can store
 full and/or relative paths and therefore escape out of the extraction
 root.

 Attached is an initial WIP to show the issue and possible solution.

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

[Django] #27658: collectstatic overwrites newer files in remote storage

2016-12-29 Thread Django 
#27658: collectstatic overwrites newer files in remote storage
-+-
   Reporter:  pgcd   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  1.10
  contrib.staticfiles|
   Severity:  Normal |   Keywords:  staticfiles
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 The change to
 django/contrib/staticfiles/management/commands/collectstatic.py in commit
 2cd2d188516475ddf256e6267cd82c495fb5c430 causes the command to overwrite
 all static files in remote storage (eg. S3), instead of only updatable
 ones.

 A quick workaround is to override the command and restore the previous
 Command.delete_file() in the subclass, but I suppose this should be fixed.

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