Re: [Django] #28695: Allow models to use __init_subclass__

2017-10-13 Thread Django 
#28695: Allow models to use __init_subclass__
-+-
 Reporter:  Jarosław Wygoda  |Owner:  Jarosław
 Type:   |  Wygoda
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ModelBase| Triage Stage:  Accepted
  __init_subclass__  |
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:"399a8db33b14a1f707912ac48a185fb0a1204913" 399a8db3]:
 {{{
 #!CommitTicketReference repository=""
 revision="399a8db33b14a1f707912ac48a185fb0a1204913"
 Fixed #28695 -- Allowed models to use __init_subclass__().
 }}}

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

Re: [Django] #26139: UUIDField value must be declared "binary" to avoid MySQL warning

2017-10-13 Thread Django 
#26139: UUIDField value must be declared "binary" to avoid MySQL warning
-+-
 Reporter:  Guilhem Bichot   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  MySQL| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Chris Foresman):

 Replying to [comment:3 Tim Graham]:
 > Yes, Claude is correct. Django's `UUIDField` uses `char(32)` -- the
 `binary(16)` representation is a third-party implementation. The warnings
 I'm seeing for Django's test suite are for `BinaryField` (created #26140).

 I've been researching this; is there a reason we _don't_ use `BINARY(16)`
 for MySQL? It should be massively [http://mysqlserverteam.com/storing-
 uuid-values-in-mysql-tables/ more efficient] in storage and index space. I
 think if I subclass the existing `UUIDField`, this should be pretty close
 to working (I think I need to override `__init__` to set the `max_length`
 to 16:

 {{{
 class MySQLUUIDField(UUIDField):

 def get_internal_type(self):
 return "BinaryField"

 def get_db_prep_value(self, value, connection, prepared=False):
 if value is None:
 return None
 if not isinstance(value, uuid.UUID):
 value = self.to_python(value)

 if connection.features.has_native_uuid_field:
 return value
 return value.bytes

 def to_python(self, value):
 if value is not None and not isinstance(value, uuid.UUID):
 try:
 return uuid.UUID(bytes=value)
 except (AttributeError, ValueError):
 raise exceptions.ValidationError(
 self.error_messages['invalid'],
 code='invalid',
 params={'value': value},
 )
 return value
 }}}

 I'm taking some liberties and not accounting for every edge case, but I
 think that's enough to work with the existing MySQL backend as written,
 though ideally I'd like the backend to presume `BINARY(16)` and the field
 definition could act accordingly. Looking at Oracle and sqlite, those DBs
 use a `BLOB` type for binary data, so I'm not sure if there is any benefit
 or not using that type for a UUID.

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

Re: [Django] #28575: Allow pickling dynamically created Model exception classes (DoesNotExist, MultipleObjectsReturned, RelatedObjectDoesNotExist)

2017-10-13 Thread Django 
#28575: Allow pickling dynamically created Model exception classes 
(DoesNotExist,
MultipleObjectsReturned, RelatedObjectDoesNotExist)
-+-
 Reporter:  Rachel Tobin |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (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
-+-

Comment (by Tim Graham ):

 In [changeset:"216eda103bee71725b26421e578705f24e17dae0" 216eda1]:
 {{{
 #!CommitTicketReference repository=""
 revision="216eda103bee71725b26421e578705f24e17dae0"
 Refs #28575 -- Removed unnecessary code for model exception pickling.

 Setting __qualname__ is sufficient for pickling of DoesNotExist and
 and MultipleObjectsReturned to work correctly.
 }}}

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

Re: [Django] #28643: Complete the ORM Function Library

2017-10-13 Thread Django 
#28643: Complete the ORM Function Library
-+-
 Reporter:  Matthew Pava |Owner:  JunyiJ
 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 GitHub ):

 In [changeset:"4f27e475b30d0cf91be24f3116a54b17789ac403" 4f27e475]:
 {{{
 #!CommitTicketReference repository=""
 revision="4f27e475b30d0cf91be24f3116a54b17789ac403"
 Refs #28643 -- Reorganized database functions.

 Thanks Tim Graham for the review.
 }}}

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

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

Re: [Django] #28690: django.utils.http.parse_http_date two digit year check is incorrect

2017-10-13 Thread Django 
#28690: django.utils.http.parse_http_date two digit year check is incorrect
-+-
 Reporter:  Mads Jensen  |Owner:  Alexander
 |  Vyushkov
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Levi Payne):

 * stage:  Ready for checkin => Accepted


Comment:

 Still some suggested edits on the 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/068.8f2841c757f97c9bf9307fd9146d4124%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28690: django.utils.http.parse_http_date two digit year check is incorrect

2017-10-13 Thread Django 
#28690: django.utils.http.parse_http_date two digit year check is incorrect
-+-
 Reporter:  Mads Jensen  |Owner:  Alexander
 |  Vyushkov
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  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 Levi Payne):

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

Re: [Django] #28575: Allow pickling dynamically created Model exception classes (DoesNotExist, MultipleObjectsReturned, RelatedObjectDoesNotExist)

2017-10-13 Thread Django 
#28575: Allow pickling dynamically created Model exception classes 
(DoesNotExist,
MultipleObjectsReturned, RelatedObjectDoesNotExist)
-+-
 Reporter:  Rachel Tobin |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (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 Simon Charette):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #28710: Wrong Basque DATE_FORMAT string

2017-10-13 Thread Django 
#28710: Wrong Basque DATE_FORMAT string
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.11
  Internationalization   |
 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 Claude Paroz ):

 In [changeset:"50bbc93ccb9c90a527849cbd18c2f6f02ca83cd1" 50bbc93]:
 {{{
 #!CommitTicketReference repository=""
 revision="50bbc93ccb9c90a527849cbd18c2f6f02ca83cd1"
 [1.11.x] Fixed #28710 -- Fixed the Basque DATE_FORMAT string

 Thanks Eneko Illarramendi for the report and initial patch.
 Backport of 8c538871bda3832bca2dddefe317bf4a9230dd45 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.d49969de278e3ae82751ec55d1c8321c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28710: Wrong Basque DATE_FORMAT string

2017-10-13 Thread Django 
#28710: Wrong Basque DATE_FORMAT string
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.11
  Internationalization   |
 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 Claude Paroz ):

 In [changeset:"5595eccd4f21098f13640711420463d528b22560" 5595eccd]:
 {{{
 #!CommitTicketReference repository=""
 revision="5595eccd4f21098f13640711420463d528b22560"
 [2.0.x] Fixed #28710 -- Fixed the Basque DATE_FORMAT string

 Thanks Eneko Illarramendi for the report and initial patch.
 Backport of 8c538871bda3832bca2dddefe317bf4a9230dd45 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.17d99de93a577adb5f81dac239ac35b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28710: Wrong Basque DATE_FORMAT string

2017-10-13 Thread Django 
#28710: Wrong Basque DATE_FORMAT string
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.11
  Internationalization   |
 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 Claude Paroz ):

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


Comment:

 In [changeset:"8c538871bda3832bca2dddefe317bf4a9230dd45" 8c538871]:
 {{{
 #!CommitTicketReference repository=""
 revision="8c538871bda3832bca2dddefe317bf4a9230dd45"
 Fixed #28710 -- Fixed the Basque DATE_FORMAT string

 Thanks Eneko Illarramendi for the report and initial 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.616dffbc12b185c926680e1cc77d8ad7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28440: runserver doesn't close the connection for responses without a Content-Length

2017-10-13 Thread Django 
#28440: runserver doesn't close the connection for responses without a Content-
Length
-+-
 Reporter:  Tom Forbes   |Owner:  Tom
 |  Forbes
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Release blocker  |   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
-+-

Comment (by Tim Graham ):

 In [changeset:"32ade78c55edd6231544607a841a9e7efdcbdb5b" 32ade78c]:
 {{{
 #!CommitTicketReference repository=""
 revision="32ade78c55edd6231544607a841a9e7efdcbdb5b"
 Refs #28440 -- Fixed server connection closing test on macOS.
 }}}

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

Re: [Django] #28440: runserver doesn't close the connection for responses without a Content-Length

2017-10-13 Thread Django 
#28440: runserver doesn't close the connection for responses without a Content-
Length
-+-
 Reporter:  Tom Forbes   |Owner:  Tom
 |  Forbes
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Release blocker  |   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
-+-

Comment (by Tim Graham ):

 In [changeset:"73d025a04215a3738867fbe1f8b0ce6557a3ee03" 73d025a0]:
 {{{
 #!CommitTicketReference repository=""
 revision="73d025a04215a3738867fbe1f8b0ce6557a3ee03"
 [2.0.x] Refs #28440 -- Fixed server connection closing test on macOS.

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

Re: [Django] #28703: URL regex for admin's app_index view isn't constructed deterministically

2017-10-13 Thread Django 
#28703: URL regex for admin's app_index view isn't constructed deterministically
-+-
 Reporter:  Erik Bryant  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  stable   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 I don't entirely understand your setup but I wonder if you're concerned
 with changes to admin URLs and this URL in particular? Admin URLs may
 change when upgrading Django when new features are added or removed. For
 example, Django 2.0 adds an "autocomplete view". I wonder if your
 mechanism could ignore `admin/` URLs entirely?

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

Re: [Django] #28440: runserver doesn't close the connection for responses without a Content-Length

2017-10-13 Thread Django 
#28440: runserver doesn't close the connection for responses without a Content-
Length
-+-
 Reporter:  Tom Forbes   |Owner:  Tom
 |  Forbes
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Release blocker  |   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
-+-

Comment (by Tim Graham):

 A [https://github.com/django/django/pull/9233 PR] to fix the test on macOS
 as reported on [https://groups.google.com/d/topic/django-
 developers/zsfgCudRnFI/discussion reported on 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/061.68a8953a84fd4ed95661f06dbbd17c06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28005: normalize usage of terms 'argument' and 'parameter'

2017-10-13 Thread Django 
#28005: normalize usage of terms 'argument' and 'parameter'
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Levi
 Type:   |  Payne
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Levi Payne):

 * needs_better_patch:  1 => 0


Comment:

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

Re: [Django] #28710: Wrong Basque DATE_FORMAT string

2017-10-13 Thread Django 
#28710: Wrong Basque DATE_FORMAT string
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.11
  Internationalization   |
 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 Tim Graham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #28710: Wrong Basque DATE_FORMAT string

2017-10-13 Thread Django 
#28710: Wrong Basque DATE_FORMAT string
--+
 Reporter:  Claude Paroz  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Claude Paroz):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #28643: Complete the ORM Function Library

2017-10-13 Thread Django 
#28643: Complete the ORM Function Library
-+-
 Reporter:  Matthew Pava |Owner:  JunyiJ
 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 Mariusz Felisiak ):

 In [changeset:"8b42a18b2d7bbd9e94ee80458a1cfcbb544e588c" 8b42a18b]:
 {{{
 #!CommitTicketReference repository=""
 revision="8b42a18b2d7bbd9e94ee80458a1cfcbb544e588c"
 [2.0.x] Refs #28643 -- Reorganized database functions docs.

 Thanks Tim Graham for the review.

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

[Django] #28710: Wrong Basque DATE_FORMAT string

2017-10-13 Thread Django 
#28710: Wrong Basque DATE_FORMAT string
+
   Reporter:  Claude Paroz  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Internationalization  |Version:  1.11
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 Reported by Eneko Illarramendi on a Github pull request:
 Basque DATE_FORMAT string is not properly escaped resulting in an
 Exception that breaks the Django i18n
 module: `The format for date objects may not contain time-related format
 specifiers (found 'e').`

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

Re: [Django] #28703: URL regex for admin's app_index view isn't constructed deterministically

2017-10-13 Thread Django 
#28703: URL regex for admin's app_index view isn't constructed deterministically
-+-
 Reporter:  erikbryant   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  stable   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by erikbryant):

 I was asked to create a mechanism that would tell us if any new endpoints
 were added or if any existing endpoints were deleted. In either case we
 would need to update the web UI that uses our endpoints.

 My less-than-ideal solution was to create a snapshot of our existing
 endpoints in a file. I wrote a test that compares the current set of
 endpoints with the snapshot. If an endpoint is added/deleted the test will
 fail. The expectation is that the developer who is making the change would
 see the failure and create a ticket to have the web UI updated. I'd be
 happy to know how other teams deal with this. I'm sure there is a better
 way.

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

Re: [Django] #28643: Complete the ORM Function Library

2017-10-13 Thread Django 
#28643: Complete the ORM Function Library
-+-
 Reporter:  Matthew Pava |Owner:  JunyiJ
 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 GitHub ):

 In [changeset:"ad8036d715d4447b95d485332511b4edb1a40c0e" ad8036d7]:
 {{{
 #!CommitTicketReference repository=""
 revision="ad8036d715d4447b95d485332511b4edb1a40c0e"
 Refs #28643 -- Reorganized database functions docs.

 Thanks Tim Graham for the review.
 }}}

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

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

Re: [Django] #28643: Complete the ORM Function Library

2017-10-13 Thread Django 
#28643: Complete the ORM Function Library
-+-
 Reporter:  Matthew Pava |Owner:  JunyiJ
 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
-+-
Changes (by Shai Berger):

 * cc: Shai Berger (added)


Comment:

 Replying to [comment:12 Matthew Pava]:
 >
 > I was also wondering about the use of Trim.  Python doesn't use that
 term; instead, it uses strip.  I wonder if that really matters.  Some
 developers may look for a strip functionality in Django ORM not realizing
 that the databases use the term Trim.  Perhaps that could be clarified in
 the documentation.

 Unless there is some other use for the term `strip` in the databases, I'd
 consider "documenting" this by giving an alias:
 {{{
 class Trim(Transform):
 # ...

 Strip = Trim  # Give Trim a more Pythonic name
 }}}

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

Re: [Django] #28005: normalize usage of terms 'argument' and 'parameter'

2017-10-13 Thread Django 
#28005: normalize usage of terms 'argument' and 'parameter'
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Levi
 Type:   |  Payne
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Levi Payne):

 * needs_better_patch:  0 => 1


Comment:

 Current PR is incomplete. Working on a new one that incorporates the
 changes made so far.

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

Re: [Django] #28708: Add constants to detect the Python version

2017-10-13 Thread Django 
#28708: Add constants to detect the Python version
--+
 Reporter:  Tim Graham|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 Tim Graham ):

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


Comment:

 In [changeset:"941b0a5b334e043b5fb5ea694d60da0128a8a3b8" 941b0a5b]:
 {{{
 #!CommitTicketReference repository=""
 revision="941b0a5b334e043b5fb5ea694d60da0128a8a3b8"
 Fixed #28708 -- Added constants to detect the Python version.
 }}}

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

Re: [Django] #28643: Complete the ORM Function Library

2017-10-13 Thread Django 
#28643: Complete the ORM Function Library
-+-
 Reporter:  Matthew Pava |Owner:  JunyiJ
 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 Matthew Pava):

 In regards to Left() and Right(), they are  available in PostgreSQL and
 MySQL, but not in SQLite or Oracle.  However, you can emulate their
 functionality using the corresponding Substr function in the database
 backend.  I would hate to see us leave those out for that reason alone.
 At the same time, developers could use the Substr across all databases
 instead of using Left and Right.

 I was also wondering about the use of Trim.  Python doesn't use that term;
 instead, it uses strip.  I wonder if that really matters.  Some developers
 may look for a strip functionality in Django ORM not realizing that the
 databases use the term Trim.  Perhaps that could be clarified in the
 documentation.

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

Re: [Django] #28575: Allow pickling dynamically created Model exception classes (DoesNotExist, MultipleObjectsReturned, RelatedObjectDoesNotExist) (was: Model.DoesNotExist classes are not pickleable)

2017-10-13 Thread Django 
#28575: Allow pickling dynamically created Model exception classes 
(DoesNotExist,
MultipleObjectsReturned, RelatedObjectDoesNotExist)
-+-
 Reporter:  Rachel Tobin |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (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 Tim Graham):

 * needs_better_patch:  1 => 0
 * has_patch:  1 => 0


Comment:

 The ticket remains open to allow pickling `RelatedObjectDoesNotExist`
 which according to Simon, "will require a lot more work."

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

Re: [Django] #28575: Model.DoesNotExist classes are not pickleable

2017-10-13 Thread Django 
#28575: Model.DoesNotExist classes are not pickleable
-+-
 Reporter:  Rachel Tobin |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (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
-+-

Comment (by Tim Graham ):

 In [changeset:"6c92f711eaf382113e811e43900f4fabd0f95c26" 6c92f711]:
 {{{
 #!CommitTicketReference repository=""
 revision="6c92f711eaf382113e811e43900f4fabd0f95c26"
 Refs #28575 -- Allowed pickling Model.DoesNotExist and
 MultipleObjectsReturned classes.
 }}}

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

Re: [Django] #28643: Complete the ORM Function Library

2017-10-13 Thread Django 
#28643: Complete the ORM Function Library
-+-
 Reporter:  Matthew Pava |Owner:  JunyiJ
 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 felixxm):

 Agreed. I updated above comment and both PRs.

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

Re: [Django] #28709: makemessages creates faulty .po file

2017-10-13 Thread Django 
#28709: makemessages creates faulty .po file
-+-
 Reporter:  Davor Teskera|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:   |  Version:  1.11
  Internationalization   |
 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 Claude Paroz):

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


Comment:

 Duplicate of #28085, should be fixed in Django 2.0.

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

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

[Django] #28709: makemessages creates faulty .po file

2017-10-13 Thread Django 
#28709: makemessages creates faulty .po file
+
   Reporter:  Davor Teskera |  Owner:  nobody
   Type:  Uncategorized | Status:  new
  Component:  Internationalization  |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 |
+
 invoking
 {{{
 makemessages -l en
 }}}
 creates a faulty .po file that contains this line
 {{{
 "Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n"
 }}}
 invoking it for other languages that i have tested creates a valid file
 eg. for -l hr
 {{{
 "Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
 "%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n"
 }}}

 if you afterwards call compilemessages your app will raise exceptions
 {{{
 ValueError: invalid token in plural form: EXPRESSION
 }}}

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