Re: [Django] #28164: Properly convert floats in DecimalField.to_python

[Django]

#28164: Properly convert floats in DecimalField.to_python
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"a87189fc5e2e874219d20700cf811345138dd365" a87189fc]:
 {{{
 #!CommitTicketReference repository=""
 revision="a87189fc5e2e874219d20700cf811345138dd365"
 Fixed #28164 -- Improved float conversions in DecimalField.to_python

 Thanks Tim Graham and Adam Johnson for the reviews.
 }}}

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

Re: [Django] #27931: Clarify the meaning of "django catch-all logger"

[Django]

#27931: Clarify the meaning of "django catch-all logger"
-+-
 Reporter:  Jesse|Owner:  Barry
 Type:   |  Martin
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.10
 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 Barry Martin):

 * owner:  (none) => Barry Martin
 * status:  new => assigned


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

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

Re: [Django] #28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' object has no attribute 'is_relation'

[Django]

#28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' 
object
has no attribute 'is_relation'
-+-
 Reporter:  Logan Gunthorpe  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Closing as "needsinfo" absent 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/065.da44ef8e7b064fcdfe30dd7d105b828f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28164: Properly convert floats in DecimalField.to_python

[Django]

#28164: Properly convert floats in DecimalField.to_python
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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):

 * stage:  Accepted => Ready for checkin


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

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

[Django] #28184: FileField storages param should allow a callable

[Django]

#28184: FileField storages param should allow a callable
-+-
   Reporter:  miigotu|  Owner:  miigotu
   Type:  New| Status:  assigned
  feature|
  Component:  File   |Version:  1.11
  uploads/storage|   Keywords:  callable storage
   Severity:  Normal |  filefield
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 For example, when using S3 I may have a field that I want to use private
 acl, while other fields are not using private storage.  Locally or in
 different deployments I may not be using S3, and the storage is different.

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

Re: [Django] #28104: conditional view processing decorator adds stale ETag

[Django]

#28104: conditional view processing decorator adds stale ETag
+
 Reporter:  Syed Safi Ali Shah  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  HTTP handling   |  Version:  1.11
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Josh Schneier):

 Given it's a bugfix I agree that it should be backported to 1.11 (an LTS
 no less) but I'll leave that up to the maintainers. Thanks for working
 through documentation changes with me.

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

Re: [Django] #28104: conditional view processing decorator adds stale ETag

[Django]

#28104: conditional view processing decorator adds stale ETag
+
 Reporter:  Syed Safi Ali Shah  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  HTTP handling   |  Version:  1.11
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Kevin Christopher Henry):

 I added some comments to the PR.

 On your `versionchanged` question, my opinion is that it's not necessary.
 The current behavior isn't documented, and is wrong enough that no one can
 be successfully relying on it. So I think a line in the release notes is
 enough. (But should it be 1.11.2 rather than 2.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/069.5484b8881c3dc9bd339535b6ea6b0f85%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28144: Add allow_overwrite kwarg to FileSystemStorage._save

[Django]

#28144: Add allow_overwrite kwarg to FileSystemStorage._save
-+-
 Reporter:  Jon Prindiville  |Owner:  Jon
 |  Prindiville
 Type:  New feature  |   Status:  assigned
Component:  File |  Version:  1.11
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  file storage | Triage Stage:  Accepted
  overwrite  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jon Prindiville):

 * owner:  nobody => Jon Prindiville
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

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

 I'm not too sure about adding to the release notes or AUTHORS file, so I'm
 leaving that alone for the time being.

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

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

Re: [Django] #28183: objects.create(**dictionary, key=value) regression in 1.11

[Django]

#28183: objects.create(**dictionary, key=value) regression in 1.11
-+-
 Reporter:  MMeent   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  objects.create   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MMeent):

 OK, I didn't expect the issue to come from that direction. Thanks for
 pointing out my oversight!

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

Re: [Django] #27795: Audit force_text invocations

[Django]

#27795: Audit force_text invocations
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  assigned
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
-+-

Comment (by Claude Paroz ):

 In [changeset:"d842ada30524abf410a4de3fc1e539450173800f" d842ada]:
 {{{
 #!CommitTicketReference repository=""
 revision="d842ada30524abf410a4de3fc1e539450173800f"
 Refs #27795 -- Stopped converting integer format settings to str in
 JS/JSON i18n views

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

Re: [Django] #28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' object has no attribute 'is_relation'

[Django]

#28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' 
object
has no attribute 'is_relation'
-+
 Reporter:  Logan Gunthorpe  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  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
-+

Comment (by Logan Gunthorpe):

 I'm not exactly sure how I got the exact migrations I have.  I'm pretty
 sure I created the model with the onetoonefield, then set it as
 primary_key in a second migration (thus removing the id field).

 However, trying to reproduce this with a minimal setup always seems to
 work. I wonder if I did something really stupid and remove the id field
 from the initial migration. It was so long ago I can't really say for
 sure. Adding it back in seems to fix my problem.

 If you want to assume that's what happened close this report I'm fine with
 that as I have a reasonable fix.

 Thanks,

 Logan

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

Re: [Django] #28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' object has no attribute 'is_relation'

[Django]

#28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' 
object
has no attribute 'is_relation'
-+
 Reporter:  Logan Gunthorpe  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  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 Logan Gunthorpe):

 * Attachment "bisect.log" added.


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

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

Re: [Django] #28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' object has no attribute 'is_relation'

[Django]

#28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' 
object
has no attribute 'is_relation'
-+
 Reporter:  Logan Gunthorpe  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  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
-+

Comment (by Logan Gunthorpe):

 Sorry for the delay, the bug tracker didn't pick up my email address so it
 never sent me any emails.

 I've bisected to find this is the first bad commit:

 45ded053b1f4 Fixed #27666 -- Delayed rendering of recursivly related
 models in migration operations.

 I'll attach a bisect log.

 So far, I have not been able to produce a minimal example. I'm not sure
 why that is.

 Thanks,

 Logan

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

Re: [Django] #28182: Introduce django code migrations

[Django]

#28182: Introduce django code migrations
-+-
 Reporter:  Artur Barseghyan |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  code migration   | Triage Stage:
  proposal   |  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:   => wontfix


Comment:

 The place to propose a big idea like this is the DevelopersMailingList. I
 think you would need to provide a proof of concept to show that it's
 feasible. Personally, I don't think automated code changes could be done
 very effectively. Also, this idea could likely be done as a third-party
 app rather than in Django itself.

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

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

Re: [Django] #28183: objects.create(**dictionary, key=value) regression in 1.11

[Django]

#28183: objects.create(**dictionary, key=value) regression in 1.11
-+-
 Reporter:  MMeent   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  objects.create   | 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:   => invalid


Comment:

 The `SyntaxError` (not from Django) is because that syntax is introduced
 in Python 3.5 and your deployment is using Python 3.4.

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

Re: [Django] #28178: Allow applications that make optional use of contrib.gis to better silence the lack of a GDAL install

[Django]

#28178: Allow applications that make optional use of contrib.gis to better 
silence
the lack of a GDAL install
--+
 Reporter:  Bas ten Berge |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  GIS   |  Version:  1.11
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:  update 1.11.1 | 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:"b3e56da05061c75755475651fd57a10314e952a7" b3e56da0]:
 {{{
 #!CommitTicketReference repository=""
 revision="b3e56da05061c75755475651fd57a10314e952a7"
 [1.11.x] Fixed #28178 -- Changed contrib.gis to raise ImproperlyConfigured
 if gdal isn't installed.

 Backport of c2975910a5bc2729c2de01eb5b84777fa59551e1 from master
 }}}

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

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

Re: [Django] #27118: Make QuerySet.get_or_create()/update_or_create() error for a non-field in defaults

[Django]

#27118: Make QuerySet.get_or_create()/update_or_create() error for a non-field 
in
defaults
-+-
 Reporter:  Tom Brightwell   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  1.11 | 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):

 I'm not sure if we'd fix that, but please open a new ticket with details
 rather than commenting on a closed ticket.

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

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

Re: [Django] #28178: Allow applications that make optional use of contrib.gis to better silence the lack of a GDAL install

[Django]

#28178: Allow applications that make optional use of contrib.gis to better 
silence
the lack of a GDAL install
--+
 Reporter:  Bas ten Berge |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  GIS   |  Version:  1.11
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:  update 1.11.1 | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"c2975910a5bc2729c2de01eb5b84777fa59551e1" c2975910]:
 {{{
 #!CommitTicketReference repository=""
 revision="c2975910a5bc2729c2de01eb5b84777fa59551e1"
 Fixed #28178 -- Changed contrib.gis to raise ImproperlyConfigured if gdal
 isn't installed.
 }}}

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

Re: [Django] #28183: objects.create(**dictionary, key=value) regression in 1.11

[Django]

#28183: objects.create(**dictionary, key=value) regression in 1.11
-+-
 Reporter:  MMeent   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  objects.create   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MMeent):

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

[Django] #28183: objects.create(**dictionary, key=value) regression in 1.11

[Django]

#28183: objects.create(**dictionary, key=value) regression in 1.11
-+-
   Reporter:  MMeent |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.11
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  objects.create
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Hi,

 We recently tried to move to django 1.11.x on python 3.4, and were
 suprised that our tests failed on the following:

 {{{
 [16:37:37] : [Step 1/4] --- Environment information:
 [16:37:37] : [Step 1/4] 
 [16:37:37] : [Step 1/4] --- Python version:
 [16:37:37] : [Step 1/4] Python 3.4.2
 [16:37:37] : [Step 1/4] --- Pip version:
 [16:37:37] : [Step 1/4] pip 9.0.1 from /<...>/lib/python3.4/site-
 packages (python 3.4)
 [16:37:37] : [Step 1/4] --- Environment packages:
 [16:37:38] : [Step 1/4] appdirs (1.4.3)
 [16:37:38] : [Step 1/4] Django (1.11.1)
 [16:37:38] : [Step 1/4] django-cors-headers (1.3.1)
 [16:37:38] : [Step 1/4] django-gravatar2 (1.4.0)
 [16:37:38] : [Step 1/4] djangorestframework (3.6.2)
 [16:37:38] : [Step 1/4] docutils (0.13.1)
 [16:37:38] : [Step 1/4] olefile (0.44)
 [16:37:38] : [Step 1/4] packaging (16.8)
 [16:37:38] : [Step 1/4] Pillow (4.1.1)
 [16:37:38] : [Step 1/4] pip (9.0.1)
 [16:37:38] : [Step 1/4] pyparsing (2.2.0)
 [16:37:38] : [Step 1/4] pytz (2017.2)
 [16:37:38] : [Step 1/4] reportlab (3.4.0)
 [16:37:38] : [Step 1/4] setuptools (35.0.2)
 [16:37:38] : [Step 1/4] six (1.10.0)
 [16:37:38] : [Step 1/4] teamcity-messages (1.21)
 <...>
 [16:37:51]W: [Step 3/4]   File "/<...>/work/www/urls.py", line 16, in
 
 [16:37:51]W: [Step 3/4] url(r'^article/',
 include('article.urls')),
 [16:37:51]W: [Step 3/4]   File "/<...>/lib/python3.4/site-
 packages/django/conf/urls/__init__.py", line 50, in include
 [16:37:51]W: [Step 3/4] urlconf_module =
 import_module(urlconf_module)
 [16:37:51]W: [Step 3/4]   File
 "/<...>/lib/python3.4/importlib/__init__.py", line 109, in import_module
 [16:37:51]W: [Step 3/4] return
 _bootstrap._gcd_import(name[level:], package, level)
 [16:37:51]W: [Step 3/4]   File "", line
 2254, in _gcd_import
 [16:37:51]W: [Step 3/4]   File "", line
 2237, in _find_and_load
 [16:37:51]W: [Step 3/4]   File "", line
 2226, in _find_and_load_unlocked
 [16:37:51]W: [Step 3/4]   File "", line
 1200, in _load_unlocked
 [16:37:51]W: [Step 3/4]   File "", line
 1129, in _exec
 [16:37:51]W: [Step 3/4]   File "", line
 1471, in exec_module
 [16:37:51]W: [Step 3/4]   File "", line
 321, in _call_with_frames_removed
 [16:37:51]W: [Step 3/4]   File "/<...>/work/article/urls.py", line 3,
 in 
 [16:37:51]W: [Step 3/4] from article import views
 [16:37:51]W: [Step 3/4]   File "/<...>/work/article/views.py", line 5,
 in 
 [16:37:51]W: [Step 3/4] from article.serializers import
 ArticleTypeSerializer
 [16:37:51]W: [Step 3/4]   File "/<...>/work/article/serializers.py",
 line 6, in 
 [16:37:51]W: [Step 3/4] from money.serializers import
 MoneySerializerField
 [16:37:51]W: [Step 3/4]   File "/<...>/work/money/serializers.py",
 line 138
 [16:37:51]W: [Step 3/4] VATPeriod.objects.create(**vp_data,
 vat=vat)
 [16:37:51]W: [Step 3/4]   ^
 [16:37:51]W: [Step 3/4] SyntaxError: invalid syntax
 [16:37:52]W: [Step 3/4] Process exited with code 1
 }}}

 When I set the requirements.txt from >=1.10 to ~=1.10, our tests complete
 with the following dependencies:

 {{{
 [16:53:22] : [Step 1/4] --- Environment information:
 [16:53:22] : [Step 1/4] 
 [16:53:22] : [Step 1/4] --- Python version:
 [16:53:22] : [Step 1/4] Python 3.4.2
 [16:53:22] : [Step 1/4] --- Pip version:
 [16:53:22] : [Step 1/4] pip 9.0.1 from /<...>/lib/python3.4/site-
 packages (python 3.4)
 [16:53:22] : [Step 1/4] --- Environment packages:
 [16:53:23] : [Step 1/4] appdirs (1.4.3)
 [16:53:23] : [Step 1/4] Django (1.10.7)
 [16:53:23] : [Step 1/4] django-cors-headers (1.3.1)
 [16:53:23] : [Step 1/4] django-gravatar2 (1.4.0)
 [16:53:23] : [Step 1/4] djangorestframework (3.6.2)
 [16:53:23] : [Step 1/4] docutils (0.13.1)
 [16:53:23] : [Step 1/4] olefile (0.44)
 [16:53:23] : [Step 1/4] packaging (16.8)
 [16:53:23] : [Step 1/4] Pillow (4.1.1)
 [16:53:23] : [Step 1/4] pip (9.0.1)
 [16:53:23] : [Step 1/4] pyparsing (2.2.0)
 [16:53:2

Re: [Django] #28183: objects.create(**dictionary, key=value) regression in 1.11

[Django]

#28183: objects.create(**dictionary, key=value) regression in 1.11
-+-
 Reporter:  MMeent   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  objects.create   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MMeent):

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

Re: [Django] #28170: File upload to a CIFS mount fails with Permissions Denied (was: FileField Upload Permissions Denied)

[Django]

#28170: File upload to a CIFS mount fails with Permissions Denied
--+
 Reporter:  Derrick Jackson   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  File uploads/storage  |  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 Tim Graham):

 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the additional details. Can you offer a patch that fixes the
 issue for you? I guess a regression test might involve some mocking to
 simulate a CIFS mount.

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

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

[Django] #28182: Introduce django code migrations

[Django]

#28182: Introduce django code migrations
-+-
   Reporter:  Artur  |  Owner:  nobody
  Barseghyan |
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  master
  Uncategorized  |   Keywords:  code migration
   Severity:  Normal |  proposal
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Python has awesome introspection. `lib2to3` exists for a very long time.
 Third party libraries like `python-modernize`  seem to work fine.

 Within past 6 months I have migrated 3 sites from Django 1.6 to Django
 1.8. Next year, likely, all of them are supposed to be migrated further.

 Code migration costs a lot of time/funds/effort. Small companies can't
 always afford it (regularly). Even big companies (like Instagram) postpone
 code upgrades for a long time, due to (pick one) lack of human
 resources/funds, complexity, the hassle.

 I wonder, why would established frameworks like Django, not be willing to
 simplify code migration process (between versions) by providing code
 migration steps.

 Django could have a sub-module `codemigraiton` with sub-sub modules for
 each version update.

 For instance, Django 2.0 could contain migrations steps from 1.8 to 2.0

 /django/codemigration/django_2_0/
 /django/codemigration/django_1_11/
 /django/codemigration/django_1_10/
 /django/codemigration/django_1_9/

 Steps would be dependant.

 There could be a `django-migrate.py` command which would take care of the
 code migrations. It could accept a number of arguments, such as
 currentversion, sourcepath, etc.

 The whole upgrade process could look as follows:

 - Developers install the desired/target version of Django
 - Run the `django-migrate.py` commandto have their current code base
 upgraded.
 - Do the finishing touches by hand.

 Most of the work could have been automated, so that developers spend their
 creativity in a better way.

 I'm quite sure, this feature, it taken seriously, can bring Django to a
 new quality level and (why not?) raise more funds from companies
 interested in the future development of Django.

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

Re: [Django] #28181: Versions in GDAL lib_names are outdated

[Django]

#28181: Versions in GDAL lib_names are outdated
+--
 Reporter:  Tim Graham  |Owner:  Tim Graham
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.11
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Tim Graham ):

 In [changeset:"7fdbd253365f934d2910de3bfd756616c306bc14" 7fdbd25]:
 {{{
 #!CommitTicketReference repository=""
 revision="7fdbd253365f934d2910de3bfd756616c306bc14"
 [1.11.x] Fixed #28181 -- Added detection for GDAL 2.1 and 2.0.

 Follow up to:
 ffdf507ec0821f0520e315c2e8a6cf231ea3fd5a (adding GDAL 2.0 support)
 ebaa2fef27644430e2b9dfa912f02e39582bfc05 (confirming GDAL 2.1 support)
 8c7778884bced3e756ce139da781b0c8c8b2395c (removing GDAL 1.8, 1.7 support)

 Backport of a404f75f92971634c76330f3742261d33ccecca1 from master
 }}}

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

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

Re: [Django] #28181: Versions in GDAL lib_names are outdated

[Django]

#28181: Versions in GDAL lib_names are outdated
+--
 Reporter:  Tim Graham  |Owner:  Tim Graham
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.11
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by GitHub ):

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


Comment:

 In [changeset:"a404f75f92971634c76330f3742261d33ccecca1" a404f75f]:
 {{{
 #!CommitTicketReference repository=""
 revision="a404f75f92971634c76330f3742261d33ccecca1"
 Fixed #28181 -- Added detection for GDAL 2.1 and 2.0.

 Follow up to:
 ffdf507ec0821f0520e315c2e8a6cf231ea3fd5a (adding GDAL 2.0 support)
 ebaa2fef27644430e2b9dfa912f02e39582bfc05 (confirming GDAL 2.1 support)
 8c7778884bced3e756ce139da781b0c8c8b2395c (removing GDAL 1.8, 1.7 support)
 }}}

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

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

Re: [Django] #28170: FileField Upload Permissions Denied

[Django]

#28170: FileField Upload Permissions Denied
-+-
 Reporter:  Derrick Jackson  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  1.11
  uploads/storage|
 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 Derrick Jackson):

 Additional Details:  In my case, the files are larger than 2.5 MB. The tmp
 directory is on a local linux file system and the final location is a
 mounted CIFS drive.  This [http://stackoverflow.com/questions/26654097
 /move-from-local-linux-folder-to-a-windows-share-mounted-with-cifs Stack
 Overflow] post covers exactly my exact situation.

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

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

Re: [Django] #28170: FileField Upload Permissions Denied

[Django]

#28170: FileField Upload Permissions Denied
-+-
 Reporter:  Derrick Jackson  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  1.11
  uploads/storage|
 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 Derrick Jackson):

 * cc: derrick.jackson73@… (added)
 * status:  closed => new
 * resolution:  needsinfo =>


Comment:

 meant to re-open this ticket once I added my comment.

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

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

Re: [Django] #28170: FileField Upload Permissions Denied

[Django]

#28170: FileField Upload Permissions Denied
-+-
 Reporter:  Derrick Jackson  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  1.11
  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
-+-

Comment (by Derrick Jackson):

 Tim,

 After chatting with a colleague of mine we were able to determine that
 this commit
 
[https://github.com/django/django/commit/f734e2d4b2fc4391a4d097b80357724815c1d414
 f734e2d] is where the issue I reported started.  Specifically changing
 {{{file.save(file.name, file, save=False) to file.save(file.name,
 file.save, save=False)}}} in files.py causes the copystat error.

 Please let me know if you need additional details regarding this issue.
 Thanks,
 Derrick

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

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

Re: [Django] #28181: Versions in GDAL lib_names are outdated

[Django]

#28181: Versions in GDAL lib_names are outdated
+--
 Reporter:  Tim Graham  |Owner:  Tim Graham
 Type:  Bug |   Status:  assigned
Component:  GIS |  Version:  1.11
 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):

 * has_patch:  0 => 1


Comment:

 [https://code.djangoproject.com/ticket/28181 PR]

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

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

Re: [Django] #27118: Make QuerySet.get_or_create()/update_or_create() error for a non-field in defaults

[Django]

#27118: Make QuerySet.get_or_create()/update_or_create() error for a non-field 
in
defaults
-+-
 Reporter:  Tom Brightwell   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  1.11 | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Anthony King):

 I believe this has introduced a regression, where by if you pass into
 defaults a value that goes through a setter, a ValueError will be raised.

 The behaviour of `.create` is to create a new instance of a Model, and let
 the exception bubble up.

 This isn't behaviour we rely on in our system anymore, but we have used it
 in the past, and still do for `.create`

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

[Django] #28181: Versions in GDAL lib_names are outdated

[Django]

#28181: Versions in GDAL lib_names are outdated
--+
   Reporter:  Tim Graham  |  Owner:  Tim Graham
   Type:  Bug | Status:  assigned
  Component:  GIS |Version:  1.11
   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   |
--+
 The
 [https://docs.djangoproject.com/en/dev/ref/contrib/gis/install/geolibs/
 Django docs] say that GDAL 1.9-2.1 is supported, but
 
[https://github.com/django/django/blob/5df0ff4155d2ee3192768e8f7f75b546f98c3f77/django/contrib/gis/gdal/libgdal.py#L22-L27
 the code] searches for versions 1.7-1.11.

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

Re: [Django] #28178: Allow applications that make optional use of contrib.gis to better silence the lack of a GDAL install

[Django]

#28178: Allow applications that make optional use of contrib.gis to better 
silence
the lack of a GDAL install
--+
 Reporter:  Bas ten Berge |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  Version:  1.11
 Severity:  Release blocker   |   Resolution:
 Keywords:  update 1.11.1 | 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):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #28170: FileField Upload Permissions Denied

[Django]

#28170: FileField Upload Permissions Denied
-+-
 Reporter:  Derrick Jackson  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  1.11
  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 Peter J. Farrell):

 * cc: pjf@… (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/070.e85e4d1cce82d25e48d7c07137b892d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28180: Number queries in assertNumQueries failure output

[Django]

#28180: Number queries in assertNumQueries failure output
---+--
 Reporter:  Claude Paroz   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 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
---+--
Changes (by Claude Paroz):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/8472 PR]
 Should we add a test for 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/065.32cc1674aa36dcc1f8225a4fec198f59%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28180: Number queries in assertNumQueries failure output

[Django]

#28180: Number queries in assertNumQueries failure output
-+
   Reporter:  Claude Paroz   |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Testing framework  |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  |
-+
 Depending on the number of queries in assertNumQueries failure output, it
 may be nice to have the queries numbered.

--
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.57b6b803dae2109b5d4c7d32d0b86692%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

[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
+
Changes (by felixxm):

 * keywords:  mysql => mysql oracle index
 * needs_better_patch:  1 => 0


Comment:

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