date:20170703

Re: [Django] #28076: parse_duration() doesn't work with PostgreSQL's format

2017-07-03 Thread Django

#28076: parse_duration() doesn't work with PostgreSQL's format
-+-
 Reporter:  Matthew Schinckel|Owner:  Matthew
 Type:   |  Schinckel
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"493f7e9e1ed7d68df102de6c5926a55521b145c9" 493f7e9e]:
 {{{
 #!CommitTicketReference repository=""
 revision="493f7e9e1ed7d68df102de6c5926a55521b145c9"
 Fixed #28076 -- Added support for PostgreSQL's interval format to
 parse_duration().
 }}}

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

Re: [Django] #28354: Add a "humanized" widget for DurationField (was: Human readable duration field.)

2017-07-03 Thread Django

#28354: Add a "humanized" widget for DurationField
-+-
 Reporter:  Nikita Levonovich|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  Duration field.  | Triage Stage:
  Forms. |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Tim Graham):

 * stage:  Unreviewed => Someday/Maybe


Comment:

 I'm uncertain if this is something that must be shipped with Django.
 Perhaps seeing a proposal will help evaluate the idea.

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

Re: [Django] #28358: LazyObject defines attribute that don't exist on wrapped object

2017-07-03 Thread Django

#28358: LazyObject defines attribute that don't exist on wrapped object
-+
 Reporter:  Andrey Fedoseev  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  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 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/072.062846bd0b37af6698d84cb3e2dc6e2d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28358: LazyObject defines attribute that don't exist on wrapped object

2017-07-03 Thread Django

#28358: LazyObject defines attribute that don't exist on wrapped object
---+
   Reporter:  Andrey Fedoseev  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Utilities|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|
---+
 `LazyObject` defines magic methods (`__getitem__`, `__iter__`) which may
 be missing from the wrapped object. This leads to the following errors:

 {{{#!python
 some_variable = request.user

 if hasattr(some_variable, "__getitem__"):
 foo = some_variable["foo"]  # raises TypeError: 'User' object has no
 attribute '__getitem__'

 if hasattr(some_variable, "__iter__"):
 for item in some_variable:  # raises TypeError: 'User' object is not
 iterable
 }}}

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

Re: [Django] #14204: Take advantage of SQLite support for FK constraints

2017-07-03 Thread Django

#14204: Take advantage of SQLite support for FK constraints
-+-
 Reporter:  Ramiro Morales   |Owner:  Claude
 |  Paroz
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite, foreign key  | 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):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0
 * needs_docs:  1 => 0


Comment:

 The PR linked in the previous comment is now ready for 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/064.32d2b030caceff081ebd631cdf7a718e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27804: Use unittest.subTest() in Django's test suite

2017-07-03 Thread Django

#27804: Use unittest.subTest() in Django's test suite
-+-
 Reporter:  Tim Graham   |Owner:  Bruno
 Type:   |  Alla
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"684c0a35f620a3754639b4cbadad16b7560b7c41" 684c0a35]:
 {{{
 #!CommitTicketReference repository=""
 revision="684c0a35f620a3754639b4cbadad16b7560b7c41"
 Refs #27804 -- Used subTest() in dateparse tests.
 }}}

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

Re: [Django] #28357: Prepopulated_fields doesn't work for admin.StackedInline

2017-07-03 Thread Django

#28357: Prepopulated_fields doesn't work for admin.StackedInline
-+-
 Reporter:  ChristosKon  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  admin,   |  worksforme
  stackedinline, | Triage Stage:
  prepopulated_fields|  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:   => worksforme


Comment:

 I tested with a a simple project and couldn't reproduce a problem. Please
 provide more details.

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

[Django] #28357: Prepopulated_fields doesn't work for admin.StackedInline

2017-07-03 Thread Django

#28357: Prepopulated_fields doesn't work for admin.StackedInline
-+-
   Reporter: |  Owner:  nobody
  ChristosKon|
   Type:  Bug| Status:  new
  Component: |Version:  1.11
  contrib.admin  |   Keywords:  admin,
   Severity:  Normal |  stackedinline, prepopulated_fields
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I think that I found a bug (new to Django)

 Prepopulated_fields doesn't work for StackedInline class while it works
 fine for TabularInline class.

 Please let me know if you need any more information.

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

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

Re: [Django] #28355: Widget rendering of non-ASCII date/time formats fails on Python 2 (was: Widget rendering of unicode values fails on Python 2)

2017-07-03 Thread Django

#28355: Widget rendering of non-ASCII date/time formats fails on Python 2
-+
 Reporter:  Samir Shah   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.11
 Severity:  Release blocker  |   Resolution:
 Keywords:  widget   | 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
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

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

Re: [Django] #28321: FormSet.full_clean() shouldn't validate deleted forms

2017-07-03 Thread Django

#28321: FormSet.full_clean() shouldn't validate deleted forms
-+-
 Reporter:  Peter Inglesby   |Owner:  Windson
 Type:   |  yang
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 [https://github.com/django/django/pull/8695 PR] (without a test)

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

Re: [Django] #28354: Human readable duration field.

2017-07-03 Thread Django

#28354: Human readable duration field.
-+-
 Reporter:  Nikita Levonovich|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  Duration field.  | Triage Stage:
  Forms. |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Nikita Levonovich):

 * owner:  Nikita Levonovich => (none)
 * status:  assigned => new


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

Re: [Django] #25367: Allow expressions in .filter() calls

2017-07-03 Thread Django

#25367: Allow expressions in .filter() calls
-+-
 Reporter:  Anssi Kääriäinen |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Matthew Schinckel):

 I have a [https://github.com/django/django/pull/8119 PR] that addresses
 part of this: being able to have an expression that returns a value with
 an `output_field` of `BooleanField` used in a `.filter()`, or a
 `Case(When(...))` situation.

 Does this address enough of this ticket? Or provide any other suggestions?

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

Re: [Django] #28076: parse_duration() doesn't work with PostgreSQL's format

Re: [Django] #28354: Add a "humanized" widget for DurationField (was: Human readable duration field.)

Re: [Django] #28358: LazyObject defines attribute that don't exist on wrapped object

[Django] #28358: LazyObject defines attribute that don't exist on wrapped object

Re: [Django] #14204: Take advantage of SQLite support for FK constraints

Re: [Django] #27804: Use unittest.subTest() in Django's test suite

Re: [Django] #28357: Prepopulated_fields doesn't work for admin.StackedInline

[Django] #28357: Prepopulated_fields doesn't work for admin.StackedInline

Re: [Django] #28355: Widget rendering of non-ASCII date/time formats fails on Python 2 (was: Widget rendering of unicode values fails on Python 2)

Re: [Django] #28321: FormSet.full_clean() shouldn't validate deleted forms

Re: [Django] #28354: Human readable duration field.

Re: [Django] #25367: Allow expressions in .filter() calls

12 matches

Site Navigation

Mail list logo

Footer information