Re: [Django] #28578: Rename DatabaseCreation.clone_test_db() argument from number to suffix

2017-09-09 Thread Django 
#28578: Rename DatabaseCreation.clone_test_db() argument from number to suffix
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

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

Re: [Django] #21381: Remove contrib.redirects dependency on contrib.sites

2017-09-09 Thread Django 
#21381: Remove contrib.redirects dependency on contrib.sites
-+-
 Reporter:  Aymeric Augustin |Owner:  Dmitry
 |  Pechnikov
 Type:  New feature  |   Status:  assigned
Component:  contrib.redirects|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Dmitry Pechnikov):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #28580: AUTH_USER_MODEL not working in 1.11.5

2017-09-09 Thread Django 
#28580: AUTH_USER_MODEL not working in 1.11.5
-+-
 Reporter:  Kevin Ramirez|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  1.11.5   | Triage Stage:
  AUTH_USER_MODEL AbstractUser   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 I don't see anything in the 1.11.5 release notes that seems likely to
 cause this. Can you provide a sample project?

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

[Django] #28580: AUTH_USER_MODEL not working in 1.11.5

2017-09-09 Thread Django 
#28580: AUTH_USER_MODEL not working in 1.11.5
-+-
   Reporter:  Kevin  |  Owner:  nobody
  Ramirez|
   Type:  Bug| Status:  new
  Component: |Version:  1.11
  contrib.auth   |   Keywords:  1.11.5
   Severity:  Normal |  AUTH_USER_MODEL AbstractUser
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 If you try to use AUTH_USER_MODEL with Django 1.11.5 on a new app creating
 an AbstractUser gives you an error when you try to login in admin.

 **no such table: auth_user**

 If you downgrade to 1.11.4 works great the AbstractUser.

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

Re: [Django] #24928: Add UUIDField, RangeField, JSONField, etc to database introspection

2017-09-09 Thread Django 
#24928: Add UUIDField, RangeField, JSONField, etc to database introspection
-+-
 Reporter:  Markus Holtermann|Owner:  Claude
 |  Paroz
 Type:  New feature  |   Status:  assigned
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 Claude Paroz):

 * needs_better_patch:  0 => 1


Comment:

 HStoreField and ArrayField support still missing.

-- 
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.1e291985379b29b31c35d72d1405537c%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 (was: Runserver does not correctly close connections once a response is sent)

2017-09-09 Thread Django 
#28440: runserver doesn't close the connection for responses without a Content-
Length
-+-
 Reporter:  Tom  |Owner:  Tom
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  master
 Severity:  Release blocker  |   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 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/061.c84d15d56fb3d70358c411c00df89c87%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24928: Add UUIDField, RangeField, JSONField, etc to database introspection

2017-09-09 Thread Django 
#24928: Add UUIDField, RangeField, JSONField, etc to database introspection
-+-
 Reporter:  Markus Holtermann|Owner:  Claude
 |  Paroz
 Type:  New feature  |   Status:  assigned
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
-+-

Comment (by Claude Paroz ):

 In [changeset:"a599ae6018f748f66e774604d12989911ea09d33" a599ae60]:
 {{{
 #!CommitTicketReference repository=""
 revision="a599ae6018f748f66e774604d12989911ea09d33"
 Refs #24928 -- Added introspection support for PostgreSQL RangeField
 }}}

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

Re: [Django] #28405: CICharField on a ModelFormSet doesn't catch unique constraint violations with different capitalization

2017-09-09 Thread Django 
#28405: CICharField on a ModelFormSet doesn't catch unique constraint violations
with different capitalization
--+
 Reporter:  Jon Dufresne  |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham):

 I think it'd be difficult to translate a database's exception into the
 corresponding (translated) Django message.

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

Re: [Django] #28579: Clarify 2.0 is just a new version numbering scheme

2017-09-09 Thread Django 
#28579: Clarify 2.0 is just a new version numbering scheme
--+
 Reporter:  Collin Anderson   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
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:  0 |UI/UX:  0
--+
Changes (by Tim Graham):

 * needs_docs:  1 => 0
 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

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

Re: [Django] #28574: Add a QuerySet.explain() method

2017-09-09 Thread Django 
#28574: Add a QuerySet.explain() method
-+-
 Reporter:  Tom  |Owner:  Tom
 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 Tom):

 * cc: Tom (added)
 * owner:  nobody => Tom
 * 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/061.e9e9e1ff0f7f5f319805a92a068779c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28571: Allow createsuperuser to bypass password validation

2017-09-09 Thread Django 
#28571: Allow createsuperuser to bypass password validation
--+
 Reporter:  Daniel Hahler |Owner:  Tom
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.auth  |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tom):

 PR: https://github.com/django/django/pull/9050/

 I was not sure what the prompt message should be or if we should include
 some kind of warning, so I went with: `Bypass validation and create user
 anyway? [y/n]: '`

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

Re: [Django] #28578: Rename DatabaseCreation.clone_test_db() argument from number to suffix

2017-09-09 Thread Django 
#28578: Rename DatabaseCreation.clone_test_db() argument from number to suffix
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jon Dufresne):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/9048 PR]

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

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

Re: [Django] #28571: Allow createsuperuser to bypass password validation

2017-09-09 Thread Django 
#28571: Allow createsuperuser to bypass password validation
--+
 Reporter:  Daniel Hahler |Owner:  Tom
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.auth  |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tom):

 * cc: Tom (added)
 * owner:  nobody => Tom
 * 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.518cb1080d5b75d923a2c8505dedb5f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28579: Clarify 2.0 is just a new version numbering scheme

2017-09-09 Thread Django 
#28579: Clarify 2.0 is just a new version numbering scheme
-+-
 Reporter:  Collin Anderson  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Collin Anderson):

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

Re: [Django] #28579: Clarify 2.0 is just a new version numbering scheme

2017-09-09 Thread Django 
#28579: Clarify 2.0 is just a new version numbering scheme
-+-
 Reporter:  Collin Anderson  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 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 Collin Anderson):

 * cc: Collin Anderson (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/072.81c436d3a96ba37835e4bcec6eac8bb0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28579: Clarify 2.0 is just a new version numbering scheme

2017-09-09 Thread Django 
#28579: Clarify 2.0 is just a new version numbering scheme
+
   Reporter:  Collin Anderson   |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  master
   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 |
+
 I've seen a question or two asking how big of a break will 2.0 be.

 It could be worth clarifying near the top of the release notes that 2.0 is
 part of a new version numbering scheme, and there is no major /
 unprecedented backwards compatibility. It's no bigger of a change than
 from 1.8 -> 1.9 besides dropping 2.x support.

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

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

Re: [Django] #24928: Add UUIDField, RangeField, JSONField, etc to database introspection

2017-09-09 Thread Django 
#24928: Add UUIDField, RangeField, JSONField, etc to database introspection
-+-
 Reporter:  Markus Holtermann|Owner:  Claude
 |  Paroz
 Type:  New feature  |   Status:  assigned
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
-+-

Comment (by Claude Paroz ):

 In [changeset:"0cbb6ac00770d201b8f30a404d516b97fe41485d" 0cbb6ac0]:
 {{{
 #!CommitTicketReference repository=""
 revision="0cbb6ac00770d201b8f30a404d516b97fe41485d"
 Refs #24928 -- Added introspection support for PostgreSQL JSONField

 Thanks Adam Johnson and Tim Graham for the reviews.
 }}}

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

Re: [Django] #28405: CICharField on a ModelFormSet doesn't catch unique constraint violations with different capitalization

2017-09-09 Thread Django 
#28405: CICharField on a ModelFormSet doesn't catch unique constraint violations
with different capitalization
--+
 Reporter:  Jon Dufresne  |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Jon Dufresne):

 As a potential solution, what do others think about catching the
 database's `IntegrityError` during `ModelForm.save()` to report unique
 constraint violations in model forms? The database is already optimized
 for robust checking of unique constraints, why repeat that code at the
 application layer? It produces subtle differences and edge cases. This
 solution could potentially deprecate the large amounts of Django code used
 to check if a submitted form violates unique constraints and rely on the
 basic database feature instead. All builtin datbase backends support
 unique constraints. If we rely on the database, we wouldn't need to figure
 out how the database is comparing rows (case sensitive vs case
 insensitive), it'll tell us.

 Something to note, this would mean that not all validation occurs before
 the `ModelForm.save()` and that the `ModelForm.save()` can be unsuccessful
 and could add errors to the form.

 (Usual backward compatibility concerns apply.)

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

Re: [Django] #25961: remove handling of thread-non-safe GEOS functions

2017-09-09 Thread Django 
#25961: remove handling of thread-non-safe GEOS functions
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  master
 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 Tim Graham ):

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


Comment:

 In [changeset:"8b5a29800ce0bc7272917de99b46f6f6dcdb7d74" 8b5a2980]:
 {{{
 #!CommitTicketReference repository=""
 revision="8b5a29800ce0bc7272917de99b46f6f6dcdb7d74"
 Fixed #25961 -- Removed handling of non-thread safe GEOS functions.
 }}}

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

[Django] #28578: Rename DatabaseCreation.clone_test_db() argument from number to suffix

2017-09-09 Thread Django 
#28578: Rename DatabaseCreation.clone_test_db() argument from number to suffix
-+-
   Reporter:  Jon|  Owner:  nobody
  Dufresne   |
   Type: | Status:  new
  Cleanup/optimization   |
  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  |
-+-
 Recently, I had the need to use `DatabaseCreation.clone_test_db()`. The
 function has the argument `number`. `number` is
 
[https://github.com/django/django/blob/63d2472b1066c6a2038c5e903aafb5437f78a415/django/db/backends/base/creation.py#L225
 concatenated to the end of the database name] to create the test database
 name. This value does ''not'' need to be a number nor is it used
 numerically. Any string will do. In my use case, I was using a random
 string, not a number. Therefore, I find the current name misleading and
 inaccurate. I suggest the name `suffix` instead.

 `DatabaseCreation.clone_test_db()`, `DatabaseCreation._clone_test_db()`,
 and `DatabaseCreation.get_test_db_clone_settings()` are not documented
 functions. So I believe no deprecation path is required.

 `DatabaseCreation.destroy_test_db()`, which also has the `number`
 argument,
 
[https://docs.djangoproject.com/en/1.11/topics/testing/advanced/#django.db.connection.creation.destroy_test_db
 is documented], but the `number` argument is not part of that
 documentation. I'm not sure if this is intentional or an oversight. But if
 intentional, again, I believe no deprecation path is required.

 If I'm misunderstanding and a deprecation path is required, please let me
 know.

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

Re: [Django] #28539: REMOTE_USER auth docs (and middleware logging?) should mention that headers with underscores are stripped when using "runserver" command

2017-09-09 Thread Django 
#28539: REMOTE_USER auth docs (and middleware logging?) should mention that 
headers
with underscores are stripped when using "runserver" command
-+-
 Reporter:  jcmcken  |Owner:  Israel
 |  Fermín Montilla
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  1.11
 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
-+-

Comment (by Israel Fermín Montilla):

 The proposed patch diff along with my comments can be found here:
 
https://github.com/jcmcken/django/commit/f9eb8c81d0338ec2f543e45a4681d494a1716459

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

Re: [Django] #28539: REMOTE_USER auth docs (and middleware logging?) should mention that headers with underscores are stripped when using "runserver" command

2017-09-09 Thread Django 
#28539: REMOTE_USER auth docs (and middleware logging?) should mention that 
headers
with underscores are stripped when using "runserver" command
-+-
 Reporter:  jcmcken  |Owner:  Israel
 |  Fermín Montilla
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  1.11
 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 Israel Fermín Montilla):

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

Re: [Django] #28539: REMOTE_USER auth docs (and middleware logging?) should mention that headers with underscores are stripped when using "runserver" command

2017-09-09 Thread Django 
#28539: REMOTE_USER auth docs (and middleware logging?) should mention that 
headers
with underscores are stripped when using "runserver" command
-+-
 Reporter:  jcmcken  |Owner:  Israel
 |  Fermín Montilla
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  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 Israel Fermín Montilla):

 * cc: Israel Fermín Montilla (added)
 * status:  new => assigned
 * owner:  nobody => Israel Fermín Montilla
 * stage:  Unreviewed => Accepted


Comment:

 I think this is a valid addition to the docs, someone checking how to
 perform Remote User Authentication might not be aware of this behavior and
 the fact that django's middleware will normalize evetything to uppercase
 and underscores and also prepend `HTTP_` to the header name.

 I left just a couple of comments 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/065.7022133514827da35a154f25e0351d79%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28562: DecimalValidator raises ValidationError for decimals in scientific notation

2017-09-09 Thread Django 
#28562: DecimalValidator raises ValidationError for decimals in scientific 
notation
-+-
 Reporter:  Maksim Iakovlev  |Owner:  Josh
 |  Schneier
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  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:  0|UI/UX:  0
-+-
Changes (by Tim Martin):

 * cc: Tim Martin (added)
 * 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.403c64be85e4e2621ce2abdbaf3f7cbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.