date:20170502

Re: [Django] #28161: contrib.postgres: ArrayField(CITextField) returns string instead of list

2017-05-02 Thread Django

#28161: contrib.postgres: ArrayField(CITextField) returns string instead of list
-+-
 Reporter:  Hendrik Richter  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  1.11
 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 Simon Charette):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #27849: Add SQL 2003 FILTER syntax support with Case(When()) fallback to aggregates (was: Support Postgres FILTER WHERE conditions in ArrayAgg)

2017-05-02 Thread Django

#27849: Add SQL 2003 FILTER syntax support with Case(When()) fallback to 
aggregates
-+-
 Reporter:  Tom  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * owner:  (none) => nobody
 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * component:  contrib.postgres => Database layer (models, ORM)


Comment:

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

[Django] #28163: Make the default settings.py pass pep8

2017-05-02 Thread Django

#28163: Make the default settings.py pass pep8
+
   Reporter:  Yoni Lavi |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Uncategorized |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 |
+
 For most Django projects I see, everything passes pep8 checks except for
 migrations and the default settings.py file. Migrations aren't really
 source code, so I don't care about that, but it should be easy to make
 settings.py conform to all the rules.

 From what I checked, by changing the AUTH_PASSWORD_VALIDATORS to fit in
 under 80 cols, the entire default file should now pass validation, so I
 suggest the following comprehension for the validators (Pull Request -
 https://github.com/django/django/pull/8452):

 {{{#!python
 AUTH_PASSWORD_VALIDATORS = [
 {'NAME': 'django.contrib.auth.password_validation.%s' % validator}
 for validator in [
 'UserAttributeSimilarityValidator',
 'MinimumLengthValidator',
 'CommonPasswordValidator',
 'NumericPasswordValidator',
 ]
 ]
 }}}

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

Re: [Django] #28160: Prevent hiding GDAL errors (was: Can't start with django.contrib.gis.gdal.HAS_GDAL = False due to ImportError of GDALRaster)

2017-05-02 Thread Django

#28160: Prevent hiding GDAL errors
-+-
 Reporter:  Tom Kazimiers|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  GIS, GDAL, Contrib,  | Triage Stage:  Accepted
  Bug|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

 I think we can remove `HAS_GDAL` considering it's used only in tests and
 instead use `runtests.py` to skip `gis_tests` unless a spatial backend is
 being tested. Any other ideas or thoughts?

 [https://github.com/django/django/pull/8451 PR] (one test still needs
 fixing)

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

Re: [Django] #28153: Add a method to DiscoverRunner to allow populating a database with test data (was: patch: it's now easier to populate data in test databases that run code in parallel)

2017-05-02 Thread Django

#28153: Add a method to DiscoverRunner to allow populating a database with test
data
---+--
 Reporter:  Marcos Diez|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Tim Graham):

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


Comment:

 The [https://groups.google.com/d/topic/django-developers/qjQgcsDT-
 Ig/discussion django-developers discussion] hasn't yielded consensus about
 this (we can reopen the ticket if that consensus changes). A suggested
 alternative is to use the `post_migrate` handler during testing that loads
 the 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/068.b966b7739c16099b8abf8b47cb929589%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28161: contrib.postgres: ArrayField(CITextField) returns string instead of list

2017-05-02 Thread Django

#28161: contrib.postgres: ArrayField(CITextField) returns string instead of list
-+-
 Reporter:  Hendrik Richter  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  1.11
 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 Simon Charette):

 * status:  new => assigned
 * owner:  (none) => Simon Charette


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

Re: [Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

2017-05-02 Thread Django

#28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't 
work
in MySQL 5.5
+--
 Reporter:  Robert Rollins  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Documentation   |  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:  1   |UI/UX:  0
+--

Comment (by Robert Rollins):

 My project uses mysqlclient 1.3.9.

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

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

Re: [Django] #28147: Saving parent object after setting on child leads to unexpected data loss

2017-05-02 Thread Django

#28147: Saving parent object after setting on child leads to unexpected data 
loss
-+-
 Reporter:  Erwin Junge  |Owner:  Erwin
 |  Junge
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

2017-05-02 Thread Django

#28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't 
work
in MySQL 5.5
+--
 Reporter:  Robert Rollins  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Documentation   |  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:  1   |UI/UX:  0
+--

Comment (by Simon Charette):

 Robert, which Python library are you using to connect to MySQL?

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

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

Re: [Django] #28132: File upload crash with "TemporaryFileUploadHandler object has no attribute 'file'" error (was: Error on file upload)

2017-05-02 Thread Django

#28132: File upload crash with "TemporaryFileUploadHandler object has no 
attribute
'file'" error
-+-
 Reporter:  Michal Čihař |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  1.10
  uploads/storage|
 Severity:  Normal   |   Resolution:  needsinfo
 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
 * component:  Uncategorized => File uploads/storage
 * resolution:   => needsinfo


Comment:

 Closing as "needsinfo" until we have steps to reproduce.

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

Re: [Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

2017-05-02 Thread Django

#28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't 
work
in MySQL 5.5
+--
 Reporter:  Robert Rollins  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Documentation   |  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:  1   |UI/UX:  0
+--

Comment (by Robert Rollins):

 When I run `manage.py migrate`, I still get the big yellow warning when
 using `init_command`. The warning does not trigger when using `OPTIONS`.

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

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

Re: [Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

2017-05-02 Thread Django

#28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't 
work
in MySQL 5.5
+--
 Reporter:  Robert Rollins  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Documentation   |  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:  1   |UI/UX:  0
+--

Comment (by Tim Graham):

 I'm not able to reproduce that problem with MySQL 5.5.55. Can you explain
 why the command wouldn't 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/071.dc83c7e986e886f8d6bfcaa939322162%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28159: Using InlineFormset.save_as_new crashes in Django 1.11

2017-05-02 Thread Django

#28159: Using InlineFormset.save_as_new crashes in Django 1.11
-+-
 Reporter:  Alexander Kavanaugh  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.11
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  inlineformset,save_as_new  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_tests:  1 => 0


Comment:

 I added a test to the PR.

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

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

Re: [Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

2017-05-02 Thread Django

#28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't 
work
in MySQL 5.5
+--
 Reporter:  Robert Rollins  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Documentation   |  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:  1   |UI/UX:  0
+--
Changes (by Robert Rollins):

 * type:  Uncategorized => Bug
 * version:  1.11 => 1.10
 * component:  Uncategorized => Documentation


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

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

Re: [Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

2017-05-02 Thread Django

#28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't 
work
in MySQL 5.5
+--
 Reporter:  Robert Rollins  |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Uncategorized   |  Version:  1.11
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--

Comment (by Robert Rollins):

 Forgot to mention that I'm having this problem in Django 1.10.7.

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

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

[Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

2017-05-02 Thread Django

#28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't 
work
in MySQL 5.5
--+
   Reporter:  Robert Rollins  |  Owner:  nobody
   Type:  Uncategorized   | Status:  new
  Component:  Uncategorized   |Version:  1.11
   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   |
--+
 The Django docs claim that you can get rid of this warning by adding the
 following to your `DATABASES` setting:

 {{{
 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'"
 }}}

 This does not work in MySQL 5.5.47. The warning doesn't go away.

 However, adding ''this'' to `DATABASES` does get rid of the warning:

 {{{
 'OPTIONS': {
 'sql_mode': 'STRICT_TRANS_TABLES',
 }
 }}}

 I found this solution [http://stackoverflow.com/a/23023015/464318 here],
 but it seems like it really should be in the docs. Unless this doesn't
 work in newer MySQLs?

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

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

Re: [Django] #28157: Options order is lost in choicefields when mixing grouped and non-grouped options.

2017-05-02 Thread Django

#28157: Options order is lost in choicefields when mixing grouped and 
non-grouped
options.
-+--
 Reporter:  Paul Antropius   |Owner:  Tim Graham
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.11
 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:  1
-+--
Changes (by Tim Graham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/8450 PR]

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

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

Re: [Django] #28157: Options order is lost in choicefields when mixing grouped and non-grouped options.

2017-05-02 Thread Django

#28157: Options order is lost in choicefields when mixing grouped and 
non-grouped
options.
-+--
 Reporter:  Paul Antropius   |Owner:  Tim Graham
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.11
 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:  1
-+--
Changes (by Tim Graham):

 * status:  new => assigned
 * owner:  nobody => Tim Graham


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

Re: [Django] #28161: contrib.postgres: ArrayField(CITextField) returns string instead of list

2017-05-02 Thread Django

#28161: contrib.postgres: ArrayField(CITextField) returns string instead of list
--+
 Reporter:  Hendrik Richter   |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.11
 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 Simon Charette):

 * type:  Uncategorized => Bug
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 We'll have to do
 
[https://github.com/django/django/blob/d0e43f225f59145903c72c650eeef1f80e12f9ed/django/contrib/postgres/apps.py#L19-L20
 the same thing we do for hstore].

 Marking as release blocker because it's a bug in a newly introduced
 feature.

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

Re: [Django] #28160: Can't start with django.contrib.gis.gdal.HAS_GDAL = False due to ImportError of GDALRaster

2017-05-02 Thread Django

#28160: Can't start with django.contrib.gis.gdal.HAS_GDAL = False due to
ImportError of GDALRaster
-+-
 Reporter:  Tom Kazimiers|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  GIS, GDAL, Contrib,  | Triage Stage:  Accepted
  Bug|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tom Kazimiers):

 I see, thanks for the pointer to the Django 1.11 release notes that make
 clear GDAL is required from 1.11 on to use `django.contrib.gis`. This
 makes fixing the `HAS_GDAL = False` issue maybe not really worth it (given
 that one can work around it) and I better figure out why using GDAL breaks
 TIFF support in `pgmagick` (at least for me on Ubuntu). Fixing the
 swallowed exception would be nice though.

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

Re: [Django] #28157: Options order is lost in choicefields when mixing grouped and non-grouped options.

2017-05-02 Thread Django

#28157: Options order is lost in choicefields when mixing grouped and 
non-grouped
options.
-+
 Reporter:  Paul Antropius   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.11
 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:  1
-+
Changes (by Tim Graham):

 * severity:  Normal => Release blocker
 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 Regression bisected to b52c73008a9d67e9ddbb841872dc15cdd3d6ee01 (template-
 based widget rendering).

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

Re: [Django] #28157: Options order is lost in choicefields when mixing grouped and non-grouped options.

2017-05-02 Thread Django

#28157: Options order is lost in choicefields when mixing grouped and 
non-grouped
options.
+--
 Reporter:  Paul Antropius  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.11
 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:  1
+--
Changes (by Tim Graham):

 * easy:  1 => 0


Comment:

 I can't reproduce the behavior you describe using this model in the admin:
 {{{
 class Record(models.Model):
 media = models.CharField(max_length=25, choices=MEDIA_CHOICES)
 }}}
 Can you add more details about how to reproduce the 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/064.4f8aae54ebabffbedace3e647e35147d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24632: PostgreSQL table inheritance

2017-05-02 Thread Django

#24632: PostgreSQL table inheritance
-+-
 Reporter:  Yennick Schepers |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  orm postgresql   | Triage Stage:  Accepted
  table-inheritance inheritance  |
  object-relational  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Thomas Güttler):

 Just for the records. There is a third party app which gives you single-
 table-inheritance: https://github.com/craigds/django-typed-models

 This works for all database engines, not just PostgreSQL.

 Maybe this is a solution if the other two types of inheritance (abstract
 or multi-table) don't fit your needs.

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

[Django] #28161: contrib.postgres: ArrayField(CITextField) returns string instead of list

2017-05-02 Thread Django

#28161: contrib.postgres: ArrayField(CITextField) returns string instead of list
+
   Reporter:  Hendrik Richter   |  Owner:  (none)
   Type:  Uncategorized | Status:  new
  Component:  contrib.postgres  |Version:  1.11
   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 |
+
 The following code

 {{{
 from django.db import models
 from django.contrib.postgres.fields import ArrayField, CITextField

 class Foo(models.Model):
 bar = ArrayField(models.TextField)
 baz = ArrayField(CITextField())
 }}}

 has this wrong behaviour:

 {{{
 x = Foo.objects.get(id=1)
 x.bar #  => ["Foo", "Bar"]
 x.baz #  => "{Foo,Bar}"
 }}}

 This is due to https://github.com/psycopg/psycopg2/issues/268 which
 requires registering a new adapter for citext fields:

 Use

 {{{
 select typarray from pg_type where typname = 'citext';
 }}}

 to get the oid, then do

 {{{
 psycopg2.extensions.register_type(
 psycopg2.extensions.new_array_type(
 (the_returned_oid,), 'citext[]', psycopg2.STRING))
 }}}

 for the correct behaviour in plain psycopg2.

 Django should do that automatically if any of the CI*Fields is used.
 Alternatively, the ArrayField should convert the result string manually to
 the proper 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/048.096b8b091b175b2a01c5eae58cdb84ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28160: Can't start with django.contrib.gis.gdal.HAS_GDAL = False due to ImportError of GDALRaster

2017-05-02 Thread Django

#28160: Can't start with django.contrib.gis.gdal.HAS_GDAL = False due to
ImportError of GDALRaster
-+-
 Reporter:  Tom Kazimiers|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  GIS, GDAL, Contrib,  | Triage Stage:  Accepted
  Bug|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * stage:  Unreviewed => Accepted


Comment:

 In Django 1.11, GDAL is now mandatory in order to use `django.contrib.gis`
 (read https://docs.djangoproject.com/en/1.11/releases/1.11/#id1).
 However, somewhere in the code, the import exception is swallowed, which
 isn't nice at all. There should be at least a clear message that GDAL
 cannot be imported.

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

Re: [Django] #28161: contrib.postgres: ArrayField(CITextField) returns string instead of list

Re: [Django] #27849: Add SQL 2003 FILTER syntax support with Case(When()) fallback to aggregates (was: Support Postgres FILTER WHERE conditions in ArrayAgg)

[Django] #28163: Make the default settings.py pass pep8

Re: [Django] #28160: Prevent hiding GDAL errors (was: Can't start with django.contrib.gis.gdal.HAS_GDAL = False due to ImportError of GDALRaster)

Re: [Django] #28153: Add a method to DiscoverRunner to allow populating a database with test data (was: patch: it's now easier to populate data in test databases that run code in parallel)

Re: [Django] #28161: contrib.postgres: ArrayField(CITextField) returns string instead of list

Re: [Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

Re: [Django] #28147: Saving parent object after setting on child leads to unexpected data loss

Re: [Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

Re: [Django] #28132: File upload crash with "TemporaryFileUploadHandler object has no attribute 'file'" error (was: Error on file upload)

Re: [Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

Re: [Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

Re: [Django] #28159: Using InlineFormset.save_as_new crashes in Django 1.11

Re: [Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

Re: [Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

[Django] #28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't work in MySQL 5.5

Re: [Django] #28157: Options order is lost in choicefields when mixing grouped and non-grouped options.

Re: [Django] #28157: Options order is lost in choicefields when mixing grouped and non-grouped options.

Re: [Django] #28161: contrib.postgres: ArrayField(CITextField) returns string instead of list

Re: [Django] #28160: Can't start with django.contrib.gis.gdal.HAS_GDAL = False due to ImportError of GDALRaster

Re: [Django] #28157: Options order is lost in choicefields when mixing grouped and non-grouped options.

Re: [Django] #28157: Options order is lost in choicefields when mixing grouped and non-grouped options.

Re: [Django] #24632: PostgreSQL table inheritance

[Django] #28161: contrib.postgres: ArrayField(CITextField) returns string instead of list

Re: [Django] #28160: Can't start with django.contrib.gis.gdal.HAS_GDAL = False due to ImportError of GDALRaster

25 matches

Site Navigation

Mail list logo

Footer information