date:20160413

Re: [Django] #26500: Implement select_for_update(skip_locked=True) for Postgresql and Oracle

2016-04-13 Thread Django

#26500: Implement select_for_update(skip_locked=True) for Postgresql and Oracle
-+-
 Reporter:  charettes|Owner:  nobody
 Type:  New feature  |   Status:  new
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
-+-
Changes (by akaariai):

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

Re: [Django] #9025: Nested Inline Support in Admin

2016-04-13 Thread Django

Comment (by fdintino):

Our project at The Atlantic, [https://github.com/theatlantic/django-
nested-admin django-nested-admin], is another take on nested inlines, one
that also allows drag-and-drop sortable inlines à la Grappelli. I don't
imagine that a patch to Django would include sortable inlines, and it
certainly wouldn't include Grappelli support, which would make for a lot
less code. If my approach is interesting to any of the Django core
developers, I would be open to reworking it into a formal pull request /
patch.

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

Re: [Django] #5863: list_display does not allow functions of referenced objects

2016-04-13 Thread Django

#5863: list_display does not allow functions of referenced objects
-+-
 Reporter:  Beat Bolli   |Owner:  nobody
|
 Type:  Uncategorized|   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  list_display | Triage Stage:  Design
 |  decision needed
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by zachborboa):

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

Re: [Django] #10743: Support lookup separators in ModelAdmin.list_display

2016-04-13 Thread Django

#10743: Support lookup separators in ModelAdmin.list_display
-+-
 Reporter:  mrts |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  efficient-admin, | Triage Stage:  Accepted
  list_display   |
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by zachborboa):

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

[Django] #26500: Implement select_for_update(skip_locked=True) for Postgresql and Oracle

2016-04-13 Thread Django

#26500: Implement select_for_update(skip_locked=True) for Postgresql and Oracle
-+-
   Reporter:  charettes  |  Owner:  nobody
   Type:  New| Status:  new
  feature|
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 PostgreSQL supports this feature since 9.5.

 A `ValueError` should be raised if both `nowait` and `skip_locked` are
 `True`.

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

Re: [Django] #26499: AuthenticationMiddleware apparently accesses request.POST

2016-04-13 Thread Django

#26499: AuthenticationMiddleware apparently accesses request.POST
-+-
 Reporter:  ChristopherBrix  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.9
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  middleware   | Triage Stage:
  request.post   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => closed
 * component:  Uncategorized => contrib.auth
 * resolution:   => worksforme


Comment:

 I don't believe it does. Here's the source:
 https://github.com/django/django/blob/master/django/contrib/auth/middleware.py

 Please include complete steps to reproduce the issue when reporting a bug.
 Thanks.

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

Re: [Django] #26499: AuthenticationMiddleware apparently accesses request.POST

2016-04-13 Thread Django

#26499: AuthenticationMiddleware apparently accesses request.POST
-+-
 Reporter:  ChristopherBrix  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  middleware   | Triage Stage:
  request.post   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ChristopherBrix):

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


Old description:

> The middleware `AuthenticationMiddleware` apparently accesses
> `request.POST`, because if I include it I get the exception `You cannot
> access body after reading from request's data stream` once I try to read
> `request.body`.
>
> I wasn't able to find the source code of `AuthenticationMiddleware`, but
> if it indeed does so, this [https://code.djangoproject.com/ticket/16384
> should be considered a bug].
>
> I'm running Python 2 and the latest version of Django.

New description:

 The middleware `AuthenticationMiddleware` apparently accesses
 `request.POST`, because if I include it I get the exception `You cannot
 access body after reading from request's data stream` once I try to read
 `request.body`.
 Everything works fine if I remove it from the list of middlewares.

 I wasn't able to find the source code of `AuthenticationMiddleware`, but
 if it indeed does so, this [https://code.djangoproject.com/ticket/16384
 should be considered a bug].

 I'm running Python 2 and the latest version 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/073.691dbb672433e66ac24fec9e48e56c8d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26499: AuthenticationMiddleware apparently accesses request.POST

2016-04-13 Thread Django

#26499: AuthenticationMiddleware apparently accesses request.POST
-+-
 Reporter:  ChristopherBrix  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Uncategorized|Version:  1.9
 Severity:  Normal   |   Keywords:  middleware request.post
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 The middleware `AuthenticationMiddleware` apparently accesses
 `request.POST`, because if I include it I get the exception `You cannot
 access body after reading from request's data stream` once I try to read
 `request.body`.

 I wasn't able to find the source code of `AuthenticationMiddleware`, but
 if it indeed does so, this [https://code.djangoproject.com/ticket/16384
 should be considered a bug].

 I'm running Python 2 and the latest version 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.dacdc4f3a9e16bf1b4775f84ca0d826b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26497: No Capitalization of user-defined verbose_names of model fields

2016-04-13 Thread Django

#26497: No Capitalization of user-defined verbose_names of model fields
-+--
 Reporter:  srkunze  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:  duplicate
 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 srkunze):

 Interesting tone at the other ticket.

 Anyway, I think I will try to join that mailing list. I hope I get the
 registration right.

 I will post my thoughts there. Consider this ticket obsolete.

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

Re: [Django] #26484: Add a helpful message in manage.py when Django cannot be imported

2016-04-13 Thread Django

#26484: Add a helpful message in manage.py when Django cannot be imported
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  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 timgraham):

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


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

Re: [Django] #26005: uri_to_iri() perfoms percent decoding incorrectly

2016-04-13 Thread Django

#26005: uri_to_iri() perfoms percent decoding incorrectly
---+---
 Reporter:  Chronial   |Owner:  varunnaganathan
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  1.8
 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 timgraham):

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

Re: [Django] #26484: Add a helpful message in manage.py when Django cannot be imported

2016-04-13 Thread Django

#26484: Add a helpful message in manage.py when Django cannot be imported
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   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
--+

Comment (by timgraham):

 In 724a279849a5cd09cdb5ef201fe6958a4c26fe73:

 Raised a more helpful ImportError message in manage.py template.

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

Re: [Django] #26484: Add a helpful message in manage.py when Django cannot be imported

2016-04-13 Thread Django

#26484: Add a helpful message in manage.py when Django cannot be imported
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   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
--+

Comment (by Tim Graham ):

 In [changeset:"5c6d397956f405f5c3fee6dc42568386972b9fc2" 5c6d397]:
 {{{
 #!CommitTicketReference repository=""
 revision="5c6d397956f405f5c3fee6dc42568386972b9fc2"
 Refs #26484 -- Avoided masking useful exceptions in manage.py's
 ImportError.
 }}}

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

Re: [Django] #26497: No Capitalization of user-defined verbose_names of model fields

2016-04-13 Thread Django

#26497: No Capitalization of user-defined verbose_names of model fields
-+--
Reporter: srkunze |Owner: nobody
Type: New feature | Status: closed
Component: Forms| Version: 1.8
Severity: Normal | Resolution: duplicate
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 timgraham):

* resolution: invalid => duplicate

Comment:

It'll be better to raise your proposal on the linked mailing list
discussion.

In the absence of the other patch, I don't think it makes sense to remove
auto-capitalization of user-defined verbose names as the existing
convention is to define those as lower-cased strings and rely on Django to
do capitalization as necessary. Of course, sometimes this isn't desired,
but changing it will be backwards-incompatible.

Now that I understand your proposal, I see it's a duplicate of #18129.

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

Re: [Django] #26497: No Capitalization of user-defined verbose_names of model fields

2016-04-13 Thread Django

#26497: No Capitalization of user-defined verbose_names of model fields
-+--
 Reporter:  srkunze  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 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 srkunze):

 Do you think it would make sense to separate out these two concepts in
 Django?

 1) leave user-defined verbose_name of model fields alone
 2) let user specify a format string which defines how to auto-generate a
 verbose_name of a model field

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

Re: [Django] #26497: No Capitalization of user-defined verbose_names of model fields (was: No Capitalization of verbose_name of model fields when Rendered by BoundField)

2016-04-13 Thread Django

#26497: No Capitalization of user-defined verbose_names of model fields
-+--
 Reporter:  srkunze  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  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.57a4d7259ba288eb97a21f1e2136ebb3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

2016-04-13 Thread Django

Comment (by srkunze):

I did a quick review of the patch and opened PyCharm with a fresh Django
1.9.5 installation.

Maybe I am wrong, but it seems to me that he missed some usages of
capfirst with regards to field names. Not sure if that is intended.

AFAICS, the patch does not distinguish between auto-generated
verbose_name and user-defined verbose_name. So, the patch does not help in
this regard. However, given the patch is applied, we would need to add all
capitalized forms as explicit verbose_names. Not sure if I would like
that; especially when it works so conveniently for the German language but
it would solve the problem at hand.

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

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

2016-04-13 Thread Django

#26497: No Capitalization of verbose_name of model fields when Rendered by
BoundField
-+--
 Reporter:  srkunze  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 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 srkunze):

 So, it's not entirely what we think is useful.

 Not sure if it is a locale-dependent issue, but in German, we actually
 like to see capitalized first letters. So, for auto-generated
 verbose_names, it's okay.

 But when a developer specifies the capitalization himself via the
 verbose_name attribute, it should not be changed anymore.


 Will have a look at the Sergei's attached patch.

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

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

2016-04-13 Thread Django

#26498: Data loss of microseconds on MySQL and SQLite
-+-
 Reporter:  adamchainz   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * version:  master => 1.8


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

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

2016-04-13 Thread Django

#26498: Data loss of microseconds on MySQL and SQLite
-+-
 Reporter:  adamchainz   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


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

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

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

2016-04-13 Thread Django

#26497: No Capitalization of verbose_name of model fields when Rendered by
BoundField
-+--
 Reporter:  srkunze  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 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 timgraham):

 The proposal on the mailing list is to drop all automatic capitalization
 in field labels in favor of doing it with CSS, e.g.
 {{{
 label::first-letter {
text-transform: capitalize;
 }
 }}}

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

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

2016-04-13 Thread Django

#26498: Data loss of microseconds on MySQL and SQLite
-+-
 Reporter:  adamchainz   |Owner:  nobody
 Type:  Bug  |   Status:  new
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
-+-

Comment (by adamchainz):

 I'm hoping so, we've had to `patchy.patch` this in

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

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

2016-04-13 Thread Django

#26498: Data loss of microseconds on MySQL and SQLite
-+-
 Reporter:  adamchainz   |Owner:  nobody
 Type:  Bug  |   Status:  new
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
-+-

Comment (by timgraham):

 Should this be backported? Typically that's what we do for data loss
 issues.

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

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

2016-04-13 Thread Django

#26498: Data loss of microseconds on MySQL and SQLite
-+-
 Reporter:  adamchainz   |Owner:  nobody
 Type:  Bug  |   Status:  new
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 charettes):

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

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

2016-04-13 Thread Django

#26498: Data loss of microseconds on MySQL and SQLite
-+-
 Reporter:  adamchainz   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * has_patch:  0 => 1
 * version:  1.8 => master
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

2016-04-13 Thread Django

#26498: Data loss of microseconds on MySQL and SQLite
-+-
 Reporter:  adamchainz   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.8
  (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
-+-
Changes (by lwiecek):

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


Comment:

 https://github.com/django/django/pull/6450

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

[Django] #26498: Data loss of microseconds on MySQL and SQLite

2016-04-13 Thread Django

#26498: Data loss of microseconds on MySQL and SQLite
--+
 Reporter:  adamchainz|  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Django provides `django.db.backends.utils.typecast_time` as a converter
 function for MySQL and SQLite. This function uses floating point logic
 which unfortunately causes loss of precision on some values, for example:

 {{{
 In [1]: from django.db.backends.utils import typecast_time

 In [2]: typecast_time('12:45:30.126631')  # okay
 Out[2]: datetime.time(12, 45, 30, 126631)

 In [3]: typecast_time('12:45:30.126630')   # woops
 Out[3]: datetime.time(12, 45, 30, 126629)
 }}}

 This will probably only cause loss of a single microsecond, but it's
 annoying that the database doesn't roundtrip values.

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

Re: [Django] #22383: Add the required tag to the input fields which are required for database entry

2016-04-13 Thread Django

#22383: Add the required tag to the input fields which are required for database
entry
-+
 Reporter:  abhishek.garg@…  |Owner:
 Type:  New feature  |   Status:  new
Component:  Forms|  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:

 For the record, Loic dropped his suggestion of a deprecation cycle: "I
 guess people can easily add `novalidate` to their `` to opt out of
 that".

 I've left some comments for improvement on the pull request.

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

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

2016-04-13 Thread Django

#26497: No Capitalization of verbose_name of model fields when Rendered by
BoundField
-+--
 Reporter:  srkunze  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 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 srkunze):

 Not sure if I understand it all correctly.

 We want capfirst(field.verbose_name) deactivated WHEN we specify the
 verbose_name in the model field.

 However, we don't think that it should be deactivated WHEN the
 verbose_name is generated from the field.name.

 Does this makes sense? Is that different from the proposal?

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

Re: [Django] #26486: Fix select_related() + defer() MTI tests marked as @expectedFailure

2016-04-13 Thread Django

#26486: Fix select_related() + defer() MTI tests marked as @expectedFailure
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:  Bug  |   Status:  closed
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 Tim Graham ):

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


Comment:

 In [changeset:"0456a8b9e66608e2e7b7e64035d477f44c259c94" 0456a8b9]:
 {{{
 #!CommitTicketReference repository=""
 revision="0456a8b9e66608e2e7b7e64035d477f44c259c94"
 Fixed #26486 -- Fixed a select_related() + defer() MTI edge case.
 }}}

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

Re: [Django] #16508: Provide real support for virtual fields

2016-04-13 Thread Django

#16508: Provide real support for virtual fields
-+-
 Reporter:  vzima|Owner:  pirosb3
 Type:  New feature  |   Status:  assigned
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 Tim Graham ):

 In [changeset:"c339a5a6f72690cd90d5a653dc108fbb60274a20" c339a5a]:
 {{{
 #!CommitTicketReference repository=""
 revision="c339a5a6f72690cd90d5a653dc108fbb60274a20"
 Refs #16508 -- Renamed the current "virtual" fields to "private".

 The only reason why GenericForeignKey and GenericRelation are stored
 separately inside _meta is that they need to be cloned for every model
 subclass, but that's not true for any other virtual field. Actually,
 it's only true for GenericRelation.
 }}}

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

Re: [Django] #26486: Fix select_related() + defer() MTI tests marked as @expectedFailure

2016-04-13 Thread Django

#26486: Fix select_related() + defer() MTI tests marked as @expectedFailure
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:  Bug  |   Status:  assigned
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 charettes):

 * version:  1.9 => master
 * 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/067.e589fbff546983b239a94000e184c0da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

2016-04-13 Thread Django

#26497: No Capitalization of verbose_name of model fields when Rendered by
BoundField
-+--
 Reporter:  srkunze  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 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 timgraham):

 Is it the same issue described in https://groups.google.com/d/topic
 /django-developers/gaocodgZVAk/discussion?

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

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

2016-04-13 Thread Django

#26497: No Capitalization of verbose_name of model fields when Rendered by
BoundField
-+--
 Reporter:  srkunze  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 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 TZanke):

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

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

2016-04-13 Thread Django

#26497: No Capitalization of verbose_name of model fields when Rendered by
BoundField
-+--
 Reporter:  srkunze  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 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 srkunze):

 * type:  Uncategorized => New feature


Comment:

 Would this be a valid ticket if I change its type to "new Feature"?

 "Disable capitalization of verbose_name of model fields in forms" ?

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

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

2016-04-13 Thread Django

#26497: No Capitalization of verbose_name of model fields when Rendered by
BoundField
---+--
 Reporter:  srkunze|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Forms  |  Version:  1.8
 Severity:  Normal |   Resolution:  invalid
 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 timgraham):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Please see TicketClosingReasons/UseSupportChannels for usage questions.

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

Re: [Django] #21231: Limiting the number of variables and files that a POST request can contain

2016-04-13 Thread Django

#21231: Limiting the number of variables and files that a POST request can 
contain
---+
 Reporter:  epandurski@…   |Owner:
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  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
---+

Comment (by timgraham):

 [https://github.com/django/django/pull/6447 Updated PR]. I've put out
 another call for reviews on [https://groups.google.com/d/topic/django-
 developers/UwkkZ4h0dVA/discussion django-developers].

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

Re: [Django] #26493: Document that built-in signals use send()

2016-04-13 Thread Django

#26493: Document that built-in signals use send()
-+-
 Reporter:  marfire  |Owner:  filias
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 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:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"8bf5cede3785a49b90737440eb9cc082ff29c054" 8bf5ced]:
 {{{
 #!CommitTicketReference repository=""
 revision="8bf5cede3785a49b90737440eb9cc082ff29c054"
 [1.9.x] Fixed #26493 -- Documented how built-in signals are sent.

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

Re: [Django] #26493: Document that built-in signals use send()

2016-04-13 Thread Django

#26493: Document that built-in signals use send()
-+-
 Reporter:  marfire  |Owner:  filias
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 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:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"47fbbc33de805c803c39483344854caa2890c32c" 47fbbc33]:
 {{{
 #!CommitTicketReference repository=""
 revision="47fbbc33de805c803c39483344854caa2890c32c"
 Fixed #26493 -- Documented how built-in signals are sent.
 }}}

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

Re: [Django] #26493: Document that built-in signals use send()

2016-04-13 Thread Django

#26493: Document that built-in signals use send()
-+-
 Reporter:  marfire  |Owner:  filias
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * has_patch:  0 => 1
 * 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.413248b6000328b6a560cac827a65d91%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24787: Cannot assign a ForeignKey field with blank=True and null=False in Model.clean()

2016-04-13 Thread Django

#24787: Cannot assign a ForeignKey field with blank=True and null=False in
Model.clean()
-+
 Reporter:  mssnlayam|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 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 timgraham):

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


Comment:

 The null assignment exception in the ticket description was removed in
 04e13c89138d48c20e774a2b6bf06796f73ac0fe (#26179) which will be in Django
 1.10. I believe that resolves this issue.

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

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

Re: [Django] #26496: AdminEmailHandler can produce mails violating RFC2822

2016-04-13 Thread Django

#26496: AdminEmailHandler can produce mails violating RFC2822
-+
 Reporter:  nijel|Owner:
 Type:  Bug  |   Status:  new
Component:  Error reporting  |  Version:  1.9
 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 timgraham):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * 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/063.628208d94cede92e5ccd9dd3c987d19a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

2016-04-13 Thread Django

#26497: No Capitalization of verbose_name of model fields when Rendered by
BoundField
---+
 Reporter:  srkunze|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Forms  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 When designing a new model, we named all fields as intended and correct
 capitalization using the verbose_name property.

 So, we actually want all ModelForms to respect the well-defined
 capitalization. We couldn't find anything related in the docs.

 How can this be achieved?

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

Re: [Django] #22561: EmailMessage should respect RFC2822 on max line length

2016-04-13 Thread Django

#22561: EmailMessage should respect RFC2822 on max line length
-+-
 Reporter:  notsqrt  |Owner:  levkowetz
 Type:  Bug  |   Status:  assigned
Component:  Core (Mail)  |  Version:  1.6
 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 nijel):

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

[Django] #26496: AdminEmailHandler can produce mails violating RFC2822

2016-04-13 Thread Django

#26496: AdminEmailHandler can produce mails violating RFC2822
-+-
 Reporter:  nijel|  Owner:
 Type:  Bug  | Status:  new
Component:  Error reporting  |Version:  1.9
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 The RFC2822 specifies maximal length of line in a message to 998
 characters (see also https://code.djangoproject.com/ticket/22561). However
 with AdminEmailHandler it's quite easy to reach it once settings contains
 some more complex dictionary, which is always printed on single line.

 The problematic template is TECHNICAL_500_TEXT_TEMPLATE in
 django/views/debug.py:

 https://github.com/django/django/blob/master/django/views/debug.py#L1121

 Specially this code:

 {{{
 Using settings module {{ settings.SETTINGS_MODULE }}{% for k, v in
 settings.items|dictsort:0 %}
 {{ k }} = {{ v|stringformat:"r" }}{% endfor %}
 }}}


 I think best approach would be to use pformat for formatting those entries
 same as is used for request parameters.

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

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

Re: [Django] #26493: Document that built-in signals use send()

2016-04-13 Thread Django

#26493: Document that built-in signals use send()
--+
 Reporter:  marfire   |Owner:  filias
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  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 filias):

 Added documentation available in
 https://github.com/filias/django/tree/ticket_26493

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

Re: [Django] #26493: Document that built-in signals use send()

2016-04-13 Thread Django

#26493: Document that built-in signals use send()
--+
 Reporter:  marfire   |Owner:  filias
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  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
--+
Changes (by filias):

 * owner:  nobody => filias
 * 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/065.f3902450659f27fd1f4eadb67b8c3e69%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

47 matches

Mail list logo