[Django] #26218: You mention php for the date formatter. Do you mean Python?

2016-02-13 Thread Django 
#26218: You mention php for the date formatter.  Do you mean Python?
---+
 Reporter:  joeg816|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 In this document, line 287:

 https://github.com/django/django/blob/master/docs/intro/overview.txt

 The doc says, "In this case, the date filter formats a Python datetime
 object in
 the given format (as found in PHP's date function)."

 Why does it say PHP's date function?  Does you mean Python?

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

[Django] #26217: Docs for WeekArchiveView are misleading about %W

2016-02-13 Thread Django 
#26217: Docs for WeekArchiveView are misleading about %W
---+
 Reporter:  konk   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The [[https://docs.djangoproject.com/en/1.9/ref/class-based-views/generic-
 date-based/#weekarchiveview|docs]] state:

 > The `'%W'` format uses the ISO week format and its week begins on a
 Monday. The `'%W'` format is the same in both the `strftime()` and the
 `date`.

 However, as established in #7380, this is not true (another example is the
 week starting on 2015-11-16, which is week 47 according to `date`, but 46
 according to `strftime()`). This section of the docs should be rephrased
 into a warning that `'%W'` and `'W'` are not compatible with each other.

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

Re: [Django] #26140: BinaryField value must be declared "binary" in queries to avoid MySQL 5.7+ warning

2016-02-13 Thread Django 
#26140: BinaryField value must be declared "binary" in queries to avoid MySQL 
5.7+
warning
-+-
 Reporter:  timgraham|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:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * has_patch:  0 => 1


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

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

Re: [Django] #26140: BinaryField value must be declared "binary" in queries to avoid MySQL 5.7+ warning

2016-02-13 Thread Django 
#26140: BinaryField value must be declared "binary" in queries to avoid MySQL 
5.7+
warning
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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
-+-

Comment (by claudep):

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

Re: [Django] #26190: Return final management command result from call_command

2016-02-13 Thread Django 
#26190: Return final management command result from call_command
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 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 claudep):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #26215: if dumpdata FloatRangeField and IntegerRangeField values = "None" and post loaddata is ValidationError

2016-02-13 Thread Django 
#26215: if dumpdata FloatRangeField and IntegerRangeField values = "None" and 
post
loaddata is ValidationError
-+-
 Reporter:  bukin242 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by bukin242):

 Replying to [comment:3 timgraham]:
 > I tried to reproduce with the attached test but it works fine. Could you
 provide a failing test?

 Sorry.
 I do not write the test so far.


 I did everything manually via console.
 You test field DateRange and DateTimeTZRange

 But i used FloatRangeField and IntegerRangeField and xml format.
 Please try these

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

Re: [Django] #26126: Transient failure of requests.tests.RequestsTests.test_max_age_expiration

2016-02-13 Thread Django 
#26126: Transient failure of 
requests.tests.RequestsTests.test_max_age_expiration
-+-
 Reporter:  charettes|Owner:
 Type:   |  berkerpeksag
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  master
 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 timgraham):

 * needs_better_patch:  0 => 1


Comment:

 As noted on the PR, can `django.test.utils.freeze_time()` help?

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

Re: [Django] #25143: ArrayField should implement from_db_value()

2016-02-13 Thread Django 
#25143: ArrayField should implement from_db_value()
-+-
 Reporter:  Odahi|Owner:
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  1.8
 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 timgraham):

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

Re: [Django] #26193: urlize doesn't handle extra punctuation after the link properly

2016-02-13 Thread Django 
#26193: urlize doesn't handle extra punctuation after the link properly
---+-
 Reporter:  lsemel |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  1.8
 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 timgraham):

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

Re: [Django] #26212: Forms' FileField is not pickleable

2016-02-13 Thread Django 
#26212: Forms' FileField is not pickleable
-+-
 Reporter:  koterpillar  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.9
 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 timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 I'll add some release notes if we decide to backport this.

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

Re: [Django] #11665: django.test.TestCase should flush constraints

2016-02-13 Thread Django 
#11665: django.test.TestCase should flush constraints
-+-
 Reporter:  Glenn|Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  master
 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 Tim Graham ):

 * owner:   => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"fcd08c175787e909b3eb98f756317a07741c48dd" fcd08c1]:
 {{{
 #!CommitTicketReference repository=""
 revision="fcd08c175787e909b3eb98f756317a07741c48dd"
 Fixed #11665 -- Made TestCase check deferrable constraints after each
 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/063.30ce7c54cb853bd6578233122b7307c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25759: Add **kwargs to as_sql method of Expressions

2016-02-13 Thread Django 
#25759: Add **kwargs to as_sql method of Expressions
-+-
 Reporter:  jarshwah |Owner:  shekhar-
 |  singh
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  expressions  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by jarshwah):

 Some notes for completing this ticket:

 Start by adding **kwargs to the method signature of as_sql for all
 expression types, including transforms and lookups. There are quite a few
 places.

 For Func, get rid of the function and template key word arguments, and
 merge self.extra with **kwargs in a local variable (so you don't modify
 self.extra), using that to generate the sql string.

 Need to update docs to reference the new **kwargs argument and change any
 tests that override as_sql for vendor specific tests so that they no
 longer modify self.template or self.function.

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