Re: [Django] #29500: SQLite functions crashes on NULL values

[Django]

#29500: SQLite functions crashes on NULL values
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Srinivas
 |  Reddy Thatiparthy
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 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 Srinivas Reddy Thatiparthy):

 * owner:  nobody => Srinivas Reddy Thatiparthy
 * 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/068.5b3c7ee46bf78109e9eca34025a137cb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29523: Remove DateTimeShortcuts.js dependency on jQuery

[Django]

#29523: Remove DateTimeShortcuts.js dependency on jQuery
--+
 Reporter:  Claude Paroz  |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  master
 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 Srinivas Reddy Thatiparthy):

 * status:  assigned => new
 * owner:  Srinivas Reddy Thatiparthy => (none)


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

Re: [Django] #11927: Allow manage.py dumpdata to dump YAML in block style

[Django]

#11927: Allow manage.py dumpdata to dump YAML in block style
-+-
 Reporter:  sampablokuper|Owner:  Matthijs
 |  Kooijman
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Matthijs Kooijman):

 * cc: Matthijs Kooijman (added)
 * needs_better_patch:  1 => 0
 * component:  Core (Serialization) => Core (Management commands)
 * needs_tests:  1 => 0
 * owner:  Xiao Hanyu => Matthijs Kooijman
 * stage:  Accepted => Unreviewed


Comment:

 I've taken the time time to redo this patch and address the comments on
 the previous patch. The patch now also adds tests and documentation.

 The PyYAML docs say the following:

 > By default, PyYAML chooses the style of a collection depending on
 whether it has nested collections. If a collection has nested collections,
 it will be assigned the block style. Otherwise it will have the flow
 style.
 >
 > If you want collections to be always serialized in the block style, set
 the parameter default_flow_style of dump() to False. For instance,

 In other words, this option configures the style for collections, and
 there are three options: Always use the flow style, always use the block
 style, or the default of automatically selecting. To match that, I've
 added a `--yaml-collection-style` option that takes `auto`, `flow` or
 `block` option.

 Some uncertainties / notes when reviewing the patch:
  - The option name is a lot more verbose than the `--style` option Russel
 [[https://code.djangoproject.com/ticket/11927#comment:10|proposed]].
 However, since it is only relevant to the yaml formatter, I've made the
 option name more verbose.
  - The code in django/core/management/commands/dumpdata.py only passes the
 option on to the serializer when the current formatter is 'yaml'. This
 might be a bit hardcoded, but I didn't see an easy and elegant way to do
 this otherwise?
  - I've left the default at "`auto`" as before, but I suspect that a
 default of "`block`" might be more appropriate for loaddata. The current
 mixed style likely produces more user surprise that the more verbose block
 style would, as well as being more appropriate for version control. Would
 it make sense to change the default? If so, should the default of the
 serializer class be changed as well, or just the dumpdata command?

 Given this is a new feature, I've targeted the docs at 2.2.

 The patch is available on github:
 https://github.com/django/django/pull/10117

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

Re: [Django] #20581: Support DEFERRABLE INITIALLY DEFERRED for UNIQUE constraints

[Django]

#20581: Support DEFERRABLE INITIALLY DEFERRED for UNIQUE constraints
-+-
 Reporter:  dmadeley@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db-indexes   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ian Foote):

 * cc: Ian Foote (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/085.141d2f754914f8acb93c2de2dfb07ae3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29523: Remove DateTimeShortcuts.js dependency on jQuery

[Django]

#29523: Remove DateTimeShortcuts.js dependency on jQuery
-+-
 Reporter:  Claude Paroz |Owner:  Srinivas
 Type:   |  Reddy Thatiparthy
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  master
 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 Claude Paroz):

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

Re: [Django] #28540: Document changes to file upload permissions in Django 1.11

[Django]

#28540: Document changes to file upload permissions in Django 1.11
-+-
 Reporter:  Yaroslav Demidenko   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  ImageField, save,| Triage Stage:  Accepted
  permissions|
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:

 See [https://github.com/django/django/pull/10116 this PR] as a possible
 approach.

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

Re: [Django] #29528: Invalid URLs passing validation by URLValidator

[Django]

#29528: Invalid URLs passing validation by URLValidator
--+
 Reporter:  Tim Bell  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 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 Claude Paroz):

 * stage:  Unreviewed => Accepted


Comment:

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