date:20170523

Re: [Django] #28231: bulk_create: avoid iterating `objs` more than necessary when `batch_size` is provided

2017-05-23 Thread Django

#28231: bulk_create: avoid iterating `objs` more than necessary when 
`batch_size`
is provided
-+-
 Reporter:  Nir Izraeli  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.11
  (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 Nir Izraeli):

 PR created and passing tests: https://github.com/django/django/pull/8540

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

Re: [Django] #27860: Changing a CharField to a ForeignKey crashes when migrating in PostgreSQL

2017-05-23 Thread Django

#27860: Changing a CharField to a ForeignKey crashes when migrating in 
PostgreSQL
--+
 Reporter:  Daniel Quinn  |Owner:  felixxm
 Type:  Bug   |   Status:  closed
Component:  Migrations|  Version:  1.10
 Severity:  Normal|   Resolution:  fixed
 Keywords:  PostgreSQL| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by GitHub ):

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


Comment:

 In [changeset:"91b2bc3e70be2632baad86488fb03cf02848b5b6" 91b2bc3]:
 {{{
 #!CommitTicketReference repository=""
 revision="91b2bc3e70be2632baad86488fb03cf02848b5b6"
 Fixed #27860 -- Dropped varchar_pattern_ops/text_pattern_ops index before
 altering char/text field in PostgreSQL.

 Thanks Tim Graham for the review.
 }}}

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

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

Re: [Django] #28171: Raise an exception if Form's empty_permitted and use_required_attribute arguments conflict

2017-05-23 Thread Django

#28171: Raise an exception if Form's empty_permitted and use_required_attribute
arguments conflict
-+-
 Reporter:  Vlastimil Zíma   |Owner:  Naveen
 Type:   |  Yadav
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Naveen Yadav):

 Thanks for suggestion Tim.


 I tried raising {{{ ValueError }}} which causes lot of tests to fail
 because of this
 
line[https://github.com/django/django/blob/master/django/forms/formsets.py#L172]
 all related to formset. I guess when forms are created through formset
 both values `empty_permitted` and `use_required_attribute` are same.

 Should i place check if form(s) is created via {{{formset}}} then error
 should not be raised ?

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

Re: [Django] #28235: LiveServerTestCase crashes because it got a ParseResultBytes instance

2017-05-23 Thread Django

#28235: LiveServerTestCase crashes because it got a ParseResultBytes instance
---+--
 Reporter:  Curtis Maloney |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.11
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Curtis Maloney):

 Setting STATIC_URL in settings fixed 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/066.44414f76711ae541c0e2f991e0cd550b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28235: LiveServerTestCase crashes because it got a ParseResultBytes instance

2017-05-23 Thread Django

#28235: LiveServerTestCase crashes because it got a ParseResultBytes instance
---+--
 Reporter:  Curtis Maloney |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.11
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Curtis Maloney):

 As can be seen here the error happens on 1.8 to 1.11.2, and py 3.3 - 3.6

 https://travis-ci.org/funkybob/django-nap/builds/235472369

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

[Django] #28235: LiveServerTestCase crashes because it got a ParseResultBytes instance

2017-05-23 Thread Django

#28235: LiveServerTestCase crashes because it got a ParseResultBytes instance
-+
   Reporter:  Curtis Maloney |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing framework  |Version:  1.11
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I'm not sure why urllib.parse.urlparse is returning a Bytes result in this
 case, but the result is the following error:

 {{{
 Traceback (most recent call last):
   File "/opt/python/3.3.5/lib/python3.3/wsgiref/handlers.py", line 137, in
 run
 self.result = application(self.environ, self.start_response)
   File "/home/travis/virtualenv/python3.3.5/lib/python3.3/site-
 packages/django/test/testcases.py", line 1106, in __call__
 if not self._should_handle(get_path_info(environ)):
   File "/home/travis/virtualenv/python3.3.5/lib/python3.3/site-
 packages/django/test/testcases.py", line 1077, in _should_handle
 return path.startswith(self.base_url[2]) and not self.base_url[1]
 TypeError: startswith first arg must be str or a tuple of str, not bytes
 }}}

 It's caused by a simple test case:

 {{{
 class RPCClientTest(LiveServerTestCase):

 def setUp(self):
 self.rpc = client.RPCClient(self.live_server_url + '/rpc/')

 def test_echo(self):
 resp = self.rpc.echo(foo='bar')
 self.assertEqual(resp, {'foo': 'bar'})
 }}}

 Where RPCClient uses a requests Session to post to the url.

 I've kludged the following patch to make it work:

 {{{
 diff -urw django/test/testcases.py /home/curtis/src/git/django-
 nap/venv/lib/python3.5/site-packages/django/test/testcases.py
 --- django/test/testcases.py2017-05-24 12:08:14.870948448 +1000
 +++ /home/curtis/src/git/django-nap/venv/lib/python3.5/site-
 packages/django/test/testcases.py   2017-05-24 11:07:53.967738745 +1000
 @@ -41,6 +41,11 @@
  from django.utils.six.moves.urllib.parse import (
  unquote, urljoin, urlparse, urlsplit, urlunsplit,
  )
 +try:
 +from urllib.parse import ParseResultBytes
 +except ImportError:
 +class ParseResultBytes:
 +pass
  from django.utils.six.moves.urllib.request import url2pathname
  from django.views.static import serve

 @@ -1183,6 +1188,8 @@
  def __init__(self, application):
  self.application = application
  self.base_url = urlparse(self.get_base_url())
 +if isinstance(self.base_url, ParseResultBytes):
 +self.base_url = self.base_url.decode('utf-8')
  super(FSFilesHandler, self).__init__()

  def _should_handle(self, path):
 }}}

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

Re: [Django] #28234: SimpleSearchTest failures with postgresql

2017-05-23 Thread Django

#28234: SimpleSearchTest failures with postgresql
--+--
 Reporter:  André Ericson |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  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 Tim Graham):

 * component:  Uncategorized => contrib.postgres


Comment:

 Tests are passing on PostgreSQL 9.6.3 for me (Ubuntu 14.04).

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

[Django] #28234: SimpleSearchTest failures with postgresql

2017-05-23 Thread Django

#28234: SimpleSearchTest failures with postgresql
-+
   Reporter:  André Ericson  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Uncategorized  |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  |
-+
 I'm having some trouble running SimpleSearchTest on postgresql 9.6.3.
 Works fine on 9.5.

 {{{
 # django/tests/test_postgresql.py
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.postgresql',
 'NAME': 'django_tests',
 },
 'other': {
 'ENGINE': 'django.db.backends.postgresql',
 'NAME': 'django_tests_other',
 }
 }

 SECRET_KEY = "django_tests_secret_key"

 # Use a fast hasher to speed up tests.
 PASSWORD_HASHERS = [
 'django.contrib.auth.hashers.MD5PasswordHasher',
 ]
 }}}
 {{{
 ➜ tests git:(master) ✗ python runtests.py postgres_tests --settings
 tests.test_postgresql
 Testing against Django installed in
 '/Users/aericson/projects/django/django' with up to 4 processes
 Creating test database for alias 'default'...
 Cloning test database for alias 'default'...
 Cloning test database for alias 'default'...
 Cloning test database for alias 'default'...
 Cloning test database for alias 'default'...
 Creating test database for alias 'other'...
 Cloning test database for alias 'other'...
 Cloning test database for alias 'other'...
 Cloning test database for alias 'other'...
 Cloning test database for alias 'other'...
 System check identified no issues (0 silenced).
 
.x.x...x...x...FF.
 ==
 FAIL: test_non_exact_match (postgres_tests.test_search.SimpleSearchTest)
 --
 Traceback (most recent call last):
   File
 "/Users/aericson/.pyenv/versions/3.6.1/lib/python3.6/unittest/case.py",
 line 59, in testPartExecutor
 yield
   File
 "/Users/aericson/.pyenv/versions/3.6.1/lib/python3.6/unittest/case.py",
 line 601, in run
 testMethod()
   File
 "/Users/aericson/projects/django/tests/postgres_tests/test_search.py",
 line 92, in test_non_exact_match
 self.assertSequenceEqual(searched, [self.verse2])
   File
 "/Users/aericson/.pyenv/versions/3.6.1/lib/python3.6/unittest/case.py",
 line 1001, in assertSequenceEqual
 self.fail(msg)
   File
 "/Users/aericson/.pyenv/versions/3.6.1/lib/python3.6/unittest/case.py",
 line 666, in fail
 raise self.failureException(msg)
 AssertionError: Sequences differ:  != []

 Second sequence contains 1 additional elements.
 First extra element 0:
 

 - 
 + []

 ==
 FAIL: test_search_two_terms (postgres_tests.test_search.SimpleSearchTest)
 --
 Traceback (most recent call last):
   File
 "/Users/aericson/.pyenv/versions/3.6.1/lib/python3.6/unittest/case.py",
 line 59, in testPartExecutor
 yield
   File
 "/Users/aericson/.pyenv/versions/3.6.1/lib/python3.6/unittest/case.py",
 line 601, in run
 testMethod()
   File
 "/Users/aericson/projects/django/tests/postgres_tests/test_search.py",
 line 96, in test_search_two_terms
 self.assertSequenceEqual(searched, [self.verse2])
   File
 "/Users/aericson/.pyenv/versions/3.6.1/lib/python3.6/unittest/case.py",
 line 1001, in assertSequenceEqual
 self.fail(msg)
   File
 "/Users/aericson/.pyenv/versions/3.6.1/lib/python3.6/unittest/case.py",
 line 666, in fail
 raise self.failureException(msg)
 AssertionError: Sequences differ:  != []

 Second sequence contains 1 additional elements.
 First extra element 0:
 

 - 
 + []

 --
 Ran 366 tests in 0.907s

 FAILED (failures=2, expected failures=4)
 Destroying test database for alias 'default'...
 Destroying test database for alias 'default'...
 Destroying test database for alias 'default'...
 Destroying test database for alias 'default'...
 Destroying test database for alias 'default'...
 Destroying test database for alias 'other'...
 Destroying test database for alias 'other'...
 Destroying test database for alias 'other'...
 Destroying test database for alias 'other'...
 Destroying

Re: [Django] #26028: Improve instructions for overriding Django templates

2017-05-23 Thread Django

#26028: Improve instructions for overriding Django templates
--+
 Reporter:  Daniel Greenfeld  |Owner:  Philip James
 Type:  New feature   |   Status:  assigned
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Philip James):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #28231: bulk_create: avoid iterating `objs` more than necessary when `batch_size` is provided

2017-05-23 Thread Django

#28231: bulk_create: avoid iterating `objs` more than necessary when 
`batch_size`
is provided
-+-
 Reporter:  Nir Izraeli  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.11
  (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 Simon Charette):

 > Also, if I am to create a patch should I post it here first or create a
 PR for it?

 Create a PR for it and link it back to this ticket, it will allow you to
 run CI against and gather feedback more easily.

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

Re: [Django] #28231: bulk_create: avoid iterating `objs` more than necessary when `batch_size` is provided

2017-05-23 Thread Django

Comment (by Nir Izraeli):

I'm thinking of creating a `chunks` generator method, similar to ones
implemented in, for example, the following Stack Overflow Answers:

1. https://stackoverflow.com/a/24527424/1146713
2. https://stackoverflow.com/a/8290514/1146713

And then iterate over it in `bulk_create` and essentially run the existing
`bulk_create` code for each `batch_size`-d chunks sequentially.

WDYT?

Also, if I am to create a patch should I post it here first or create a PR
for it?

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

Re: [Django] #27859: Migration to create TextField with db_index=True crashes on MySQL

2017-05-23 Thread Django

#27859: Migration to create TextField with db_index=True crashes on MySQL
+
 Reporter:  Daniel Quinn|Owner:  felixxm
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  mysql oracle index  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by GitHub ):

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


Comment:

 In [changeset:"538bf43458a147b7edeb7118c9f325c3f59ff6fb" 538bf434]:
 {{{
 #!CommitTicketReference repository=""
 revision="538bf43458a147b7edeb7118c9f325c3f59ff6fb"
 Fixed #27859 -- Ignored db_index for TextField/BinaryField on Oracle and
 MySQL.

 Thanks Zubair Alam for the initial patch and Tim Graham for the review.
 }}}

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

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

Re: [Django] #28223: Form not always picklable due to template renderer

2017-05-23 Thread Django

#28223: Form not always picklable due to template renderer
--+-
 Reporter:  Claude Paroz  |Owner:  Gaurav Sehgal
 Type:  Bug   |   Status:  assigned
Component:  Forms |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by Gaurav Sehgal):

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

[Django] #28233: Improve the "price_per_page" example in the Documentation on Aggregation

2017-05-23 Thread Django

#28233: Improve the "price_per_page" example in the Documentation on Aggregation
-+-
   Reporter:  liushigit  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |
  Component: |Version:  1.11
  Documentation  |   Keywords:  Documentation,
   Severity:  Normal |  Aggregation, Code Example
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 This example is not very clear. There has been some talk about it:
 https://groups.google.com/forum/#!topic/django-users/CqEGJCI5aNs

 {{{
 # Cost per page
 >>> from django.db.models import F, FloatField, Sum
 >>> Book.objects.all().aggregate(
 ...price_per_page=Sum(F('price')/F('pages'),
 output_field=FloatField()))
 {'price_per_page': 0.4470664529184653}
 }}}

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

Re: [Django] #28232: Add metadata accessors and setters to GDALRaster and GDALBand objects

2017-05-23 Thread Django

#28232: Add metadata accessors and setters to GDALRaster and GDALBand objects
-+-
 Reporter:  Daniel Wiesmann  |Owner:  Daniel
 |  Wiesmann
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  raster gdal gis  | Triage Stage:  Accepted
  metadata   |
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
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #28231: bulk_create: avoid iterating `objs` more than necessary when `batch_size` is provided

2017-05-23 Thread Django

#28231: bulk_create: avoid iterating `objs` more than necessary when 
`batch_size`
is provided
-+-
 Reporter:  Nir Izraeli  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.11
  (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 Tim Graham):

 Feel free to offer a patch. Looking at the code of
 `QuerySet.bulk_create()`, I don't understand how your proposal would work.

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

Re: [Django] #28232: Add metadata accessors and setters to GDALRaster and GDALBand objects

2017-05-23 Thread Django

#28232: Add metadata accessors and setters to GDALRaster and GDALBand objects
-+-
 Reporter:  Daniel Wiesmann  |Owner:  Daniel
 |  Wiesmann
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  raster gdal gis  | Triage Stage:
  metadata   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Daniel Wiesmann):

 * status:  new => assigned
 * owner:  nobody => Daniel Wiesmann
 * has_patch:  0 => 1


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

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

[Django] #28232: Add metadata accessors and setters to GDALRaster and GDALBand objects

2017-05-23 Thread Django

#28232: Add metadata accessors and setters to GDALRaster and GDALBand objects
-+-
   Reporter:  Daniel |  Owner:  nobody
  Wiesmann   |
   Type:  New| Status:  new
  feature|
  Component:  GIS|Version:  master
   Severity:  Normal |   Keywords:  raster gdal gis
   Triage Stage: |  metadata
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The metadata can contain useful information about the structure of the
 raster. For instance, GDAL does not have a signed byte data type. Signed
 byte rasters are opened as unsigned 8bit rasters with a "is signed raster"
 flag in the metadata.

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

Re: [Django] #27859: Migration to create TextField with db_index=True crashes on MySQL

2017-05-23 Thread Django

#27859: Migration to create TextField with db_index=True crashes on MySQL
+
 Reporter:  Daniel Quinn|Owner:  felixxm
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  mysql oracle index  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Tim Graham ):

 In [changeset:"b3eb6eaf1a197ff155faf333871da032c77ba855" b3eb6eaf]:
 {{{
 #!CommitTicketReference repository=""
 revision="b3eb6eaf1a197ff155faf333871da032c77ba855"
 Refs #27859 -- Added DatabaseWrapper.display_name.

 Thanks Tim Graham for the review.
 }}}

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

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

Re: [Django] #28217: nested calls to functions decorated with sensitive_post_parameters produces unexpected results which parameters are considered sensitive

2017-05-23 Thread Django

#28217: nested calls to functions decorated with sensitive_post_parameters 
produces
unexpected results which parameters are considered sensitive
-+--
 Reporter:  Peter Zsoldos|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Error reporting  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Peter Zsoldos):

 Replying to [comment:1 Tim Graham]:
 > I'm not sure if it's worth trying to support this use case. The
 `@sensitive_post_parameters` decorator is documented to be used on a view.
 Do you have a use case for nested views like this?

 The use case we ran into was extending the login view

 In https://github.com/PaesslerAG/django-act-as-
 auth/blob/master/djactasauth/views.py the public app only has a dumbed
 down custom view, but in the internal app we use there is more
 customization going on in the login page (request based varying extra
 context, custom redirects based on user rule, etc.). However, we didn't
 want to copypaste the login logic, so we just use the
 `django.contrib.auth.views.login` view function to deal with that - thus
 inside our own decorated view we call another decorated view (aside: in
 this case we actually would prefer overriding the django contrib sensitive
 params, as the username for djactasauth would be pretty helpful debug
 info).

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

Re: [Django] #28231: bulk_create: avoid iterating `objs` more than necessary when `batch_size` is provided

Re: [Django] #27860: Changing a CharField to a ForeignKey crashes when migrating in PostgreSQL

Re: [Django] #28171: Raise an exception if Form's empty_permitted and use_required_attribute arguments conflict

Re: [Django] #28235: LiveServerTestCase crashes because it got a ParseResultBytes instance

Re: [Django] #28235: LiveServerTestCase crashes because it got a ParseResultBytes instance

[Django] #28235: LiveServerTestCase crashes because it got a ParseResultBytes instance

Re: [Django] #28234: SimpleSearchTest failures with postgresql

[Django] #28234: SimpleSearchTest failures with postgresql

Re: [Django] #26028: Improve instructions for overriding Django templates

Re: [Django] #28231: bulk_create: avoid iterating `objs` more than necessary when `batch_size` is provided

Re: [Django] #28231: bulk_create: avoid iterating `objs` more than necessary when `batch_size` is provided

Re: [Django] #27859: Migration to create TextField with db_index=True crashes on MySQL

Re: [Django] #28223: Form not always picklable due to template renderer

[Django] #28233: Improve the "price_per_page" example in the Documentation on Aggregation

Re: [Django] #28232: Add metadata accessors and setters to GDALRaster and GDALBand objects

Re: [Django] #28231: bulk_create: avoid iterating `objs` more than necessary when `batch_size` is provided

Re: [Django] #28232: Add metadata accessors and setters to GDALRaster and GDALBand objects

[Django] #28232: Add metadata accessors and setters to GDALRaster and GDALBand objects

Re: [Django] #27859: Migration to create TextField with db_index=True crashes on MySQL

Re: [Django] #28217: nested calls to functions decorated with sensitive_post_parameters produces unexpected results which parameters are considered sensitive

20 matches

Site Navigation

Mail list logo

Footer information