date:20170130

Re: [Django] #27539: assertNumQueries fails if debug cursor wrapper fills

2017-01-30 Thread Django

#27539: assertNumQueries fails if debug cursor wrapper fills
---+
 Reporter:  Malcolm Box|Owner:  (none)
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.10
 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 reficul31):

 I am sorry but I was unable to reproduce the bug with the following test.
 {{{
 def test_assert_num_queries(self):
 person = Person.objects.create(name='test')
 with self.assertNumQueries(1):
 self.client.get("/test_utils/get_person/%s/" % person.pk)
 }}}

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

Re: [Django] #25889: Organize tests in tests/queries

2017-01-30 Thread Django

#25889: Organize tests in tests/queries
-+-
 Reporter:  Claude Paroz |Owner:  reficul31
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by reficul31):

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


Comment:

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

Re: [Django] #27751: Teardown of a PG test database fails if it is an autogenerated test_MYDB database

2017-01-30 Thread Django

#27751: Teardown of a PG test database fails if it is an autogenerated test_MYDB
database
---+
 Reporter:  Cynthia Kiser  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords:  database, testing  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Ian Clark):

 This is happening because you are missing an entry in your pg_hba.conf
 file for your user to access the database 'postgres'.  Ran into this
 problem myself today.

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

Re: [Django] #27782: Model signals and Many2Many fields

2017-01-30 Thread Django

#27782: Model signals and Many2Many fields
-+-
 Reporter:  Дилян Палаузов   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  needsinfo
 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 Tim Graham):

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


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

Re: [Django] #27777: File object does not consistently open itself in context manager use

2017-01-30 Thread Django

#2: File object does not consistently open itself in context manager use
--+
 Reporter:  Raphael Gaschignard   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  File uploads/storage  |  Version:  1.10
 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):

 * Attachment "2.diff" 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.69df5a144daf70bb605b6c6962caeb81%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27777: File object does not consistently open itself in context manager use

2017-01-30 Thread Django

#2: File object does not consistently open itself in context manager use
--+
 Reporter:  Raphael Gaschignard   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  File uploads/storage  |  Version:  1.10
 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):

 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 From a quick look, I'm not sure about if the change can be done in a
 backwards compatible way. The attached patch seems what you have in mind
 but it causes a regression in one test. Accepting for further
 investigation.
 {{{
 ==
 ERROR: test_filefield_write (file_storage.tests.FileFieldStorageTests)
 --
 Traceback (most recent call last):
   File "/opt/python3.5.3/lib/python3.5/unittest/case.py", line 59, in
 testPartExecutor
 yield
   File "/opt/python3.5.3/lib/python3.5/unittest/case.py", line 601, in run
 testMethod()
   File "/home/tim/code/django/tests/file_storage/tests.py", line 660, in
 test_filefield_write
 normal.write(b'updated')
 io.UnsupportedOperation: write
 }}}

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

Re: [Django] #27791: update_or_create() doesn't work properly when model has auto_now=True

2017-01-30 Thread Django

#27791: update_or_create() doesn't work properly when model has auto_now=True
-+-
 Reporter:  Andrew Chiw  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ryan Castner):

 The fact that you use `unique_together = (("base", "target", "date"),)` is
 causing the error you are seeing, it is trying to put two values in there
 since auto_now adds the current datetime as Tim stated as well as your
 provided datetime value and it can't create two primary keys as it
 violates the single unique primary key constraint generated by those three
 fields.

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

Re: [Django] #27783: VariableDoesNotExist can lead to stack overflows unusually easily

2017-01-30 Thread Django

#27783: VariableDoesNotExist can lead to stack overflows unusually easily
-+---
 Reporter:  Ryan O’Hara  |Owner:  Ryan O’Hara
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.10
 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 Thomas Hauk):

 Also the cause of an exception death spiral in DRF, c.f.:
 https://github.com/tomchristie/django-rest-framework/issues/3736

 Would love to see this patch integrated into 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.9942e34fb2c80175fe3e34621b449133%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27792: Extended category support for Atom and RSS feeds

2017-01-30 Thread Django

#27792: Extended category support for Atom and RSS feeds
-+-
 Reporter:  Pavlo Kapyshin   |Owner:  Pavlo
 |  Kapyshin
 Type:  New feature  |   Status:  assigned
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  feedgenerator| 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):

 * stage:  Unreviewed => Accepted


Old description:

> This patch adds category (label, scheme/domain) attributes support for
> Atom and RSS feeds.
>
> Attachment is outdated, see
> https://github.com/PavloKapyshin/django/commit/9c03f13d2442f8dacc98514e1f5d1a332bc1dfc1

New description:

 This patch adds category (label, scheme/domain) attributes support for
 Atom and RSS feeds.

 See
 
https://github.com/PavloKapyshin/django/commit/9c03f13d2442f8dacc98514e1f5d1a332bc1dfc1

--

Comment:

 I'm not a user of the syndication framework but this looks okay at first
 glance. If you could find another syndication user to review it, that
 would be really helpful. Please send a pull request when the patch is
 conforming to the PatchReviewChecklist.

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

Re: [Django] #27795: Audit force_text invocations

2017-01-30 Thread Django

#27795: Audit force_text invocations
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 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 Claude Paroz ):

 In [changeset:"ccfd1295f986cdf628d774937d0b38a14584721f" ccfd1295]:
 {{{
 #!CommitTicketReference repository=""
 revision="ccfd1295f986cdf628d774937d0b38a14584721f"
 Refs #27795 -- Prevented SafeText from losing safe status on str()

 This will allow to replace force_text() by str() in several places (as one
 of
 the features of force_text is to keep the safe status).
 }}}

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

Re: [Django] #27792: Extended category support for Atom and RSS feeds

2017-01-30 Thread Django

#27792: Extended category support for Atom and RSS feeds
-+-
 Reporter:  Pavlo Kapyshin   |Owner:  Pavlo
 |  Kapyshin
 Type:  New feature  |   Status:  assigned
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  feedgenerator| Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Pavlo Kapyshin:

Old description:

> This patch adds category (label, scheme/domain) attributes support for
> Atom and RSS feeds.

New description:

 This patch adds category (label, scheme/domain) attributes support for
 Atom and RSS feeds.

 Attachment is outdated, see
 
https://github.com/PavloKapyshin/django/commit/9c03f13d2442f8dacc98514e1f5d1a332bc1dfc1

--

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

Re: [Django] #27792: Extended category support for Atom and RSS feeds

2017-01-30 Thread Django

#27792: Extended category support for Atom and RSS feeds
-+-
 Reporter:  Pavlo Kapyshin   |Owner:  Pavlo
 |  Kapyshin
 Type:  New feature  |   Status:  assigned
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  feedgenerator| Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Pavlo Kapyshin:

Old description:

> I’m working on category (label, scheme/domain) attributes support for
> Atom and RSS. I have a patch for all three feed types:
> https://github.com/PavloKapyshin/django/tree/feeds_category_object
>
> Next step is to work on docs for this.

New description:

 This patch adds category (label, scheme/domain) attributes support for
 Atom and RSS feeds.

--

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

Re: [Django] #27792: Extended category support for Atom and RSS feeds

2017-01-30 Thread Django

#27792: Extended category support for Atom and RSS feeds
-+-
 Reporter:  Pavlo Kapyshin   |Owner:  Pavlo
 |  Kapyshin
 Type:  New feature  |   Status:  assigned
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  feedgenerator| Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Pavlo Kapyshin):

 * Attachment "0001-Refs-27792-Added-extended-category-support-for-
 feeds.patch" 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/071.1d39fa364eea8259ca545672faa3cfbc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27792: Extended category support for Atom and RSS feeds

2017-01-30 Thread Django

#27792: Extended category support for Atom and RSS feeds
-+-
 Reporter:  Pavlo Kapyshin   |Owner:  Pavlo
 |  Kapyshin
 Type:  New feature  |   Status:  assigned
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  feedgenerator| Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Pavlo Kapyshin):

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

Re: [Django] #27797: dumpdata generate a backup not usable with loaddata using MySQL

2017-01-30 Thread Django

#27797: dumpdata generate a backup not usable with loaddata using MySQL
-+-
 Reporter:  David CHANIAL|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core |  Version:  1.9
  (Serialization)|
 Severity:  Normal   |   Resolution:  wontfix
 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 Tim Graham):

 * status:  new => closed
 * component:  Core (Management commands) => Core (Serialization)
 * resolution:   => wontfix


Comment:

 Thanks for the detailed report.

 My understanding is that the zero datetime values aren't permitted if
 strict mode is enabled (and it's recommended for Django as of #15940).
 Given that and that `dumpdata` isn't meant as a backup tool (databases
 have their own tool for that), I think this is too much of an edge case to
 add some workaround in 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/064.27bfe620e8d3ffe38ed943657a10486d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27796: Middlewares load twice due to StaticFilesHandler(WSGIHandler)

2017-01-30 Thread Django

#27796: Middlewares load twice due to StaticFilesHandler(WSGIHandler)
-+
 Reporter:  Anthony King |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted


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

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

[Django] #27797: dumpdata generate a backup not usable with loaddata using MySQL

2017-01-30 Thread Django

#27797: dumpdata generate a backup not usable with loaddata using MySQL
-+-
   Reporter:  David  |  Owner:  nobody
  CHANIAL|
   Type: | Status:  new
  Uncategorized  |
  Component:  Core   |Version:  1.9
  (Management commands)  |
   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  |
-+-
 == Introduction

 Hi !

 

 I have two problem :

 * The first one is that django produce me a record using DateTimeField
 with a value of "-00-00 00:00:00.00", i '''never''' update
 database content without using django orm api. For this ticket, i tried 2
 hours to reproduce this problem, but i haven't. But i think that is there
 a different bug than the second one :

 * The second one, which permit me to discover the first one, is that
 dumpdata does not raise an error when dumping this kind of record. So,
 when using loaddata later, an error happend, failing to restore this
 record.

 

 I'm using a MySQL database with server : 10.1.21-MariaDB and Django-1.9.12
 During my tests, it's seems (unconfirmed) that SQLite has not the same
 behavior.


 == The bug

 * As said previously, no matter how the record in the database is weird or
 invalid, i think django MUST fail during '''dumpdata''' and not during
 '''loaddata''' when django can detect (as here) that produced data are not
 loadable.


 == Reproduce the bug

 * In an existing MySQL Django project named - for example - ''bobb'' :

 {{{
 cd bobb
 python manage.py startapp campanella
 echo 'INSTALLED_APPS = list(INSTALLED_APPS) + ["campanella"]' >>
 bobb/settings.py
 export DJANGO_SETTINGS_MODULE=bobb.settings
 }}}
 {{{
 cat >campanella/models.py  <<'EOF'
 from __future__ import unicode_literals
 from django.db import models

 class Interpretation(models.Model):
 player = models.CharField(max_length=200)
 inserted_on = models.DateTimeField(auto_now_add=True)
 EOF
 }}}
 {{{
 python manage.py makemigrations campanella
 python manage.py migrate campanella
 }}}
 {{{
 mysql -udev_mybb -p -S/var/lib/mysql/mysql.sock db_dev_mybb -e 'INSERT
 INTO campanella_interpretation (player, inserted_on) VALUES ("Lang Lang",
 "-00-00 00:00:00.00");'
 }}}
 {{{
 python manage.py dumpdata campanella.interpretation --indent 4 > db.json
 }}}
 {{{
 cat db.json
 [
 {
 "model": "campanella.interpretation",
 "pk": 1,
 "fields": {
 "player": "Lang Lang",
 "inserted_on": null
 }
 }
 ]
 }}}
 {{{
 python -c 'import django;django.setup();from campanella.models import
 Interpretation; Interpretation.objects.all().delete()'
 }}}
 {{{
 python manage.py loaddata db.json
 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/dev_mybb/virtualenv/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 353, in
 execute_from_command_line
 utility.execute()
   File "/home/dev_mybb/virtualenv/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 345, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/dev_mybb/virtualenv/lib/python2.7/site-
 packages/django/core/management/base.py", line 348, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/dev_mybb/virtualenv/lib/python2.7/site-
 packages/django/core/management/base.py", line 399, in execute
 output = self.handle(*args, **options)
   File "/home/dev_mybb/virtualenv/lib/python2.7/site-
 packages/django/core/management/commands/loaddata.py", line 60, in handle
 self.loaddata(fixture_labels)
   File "/home/dev_mybb/virtualenv/lib/python2.7/site-
 packages/django/core/management/commands/loaddata.py", line 100, in
 loaddata
 self.load_label(fixture_label)
   File "/home/dev_mybb/virtualenv/lib/python2.7/site-
 packages/django/core/management/commands/loaddata.py", line 158, in
 load_label
 obj.save(using=self.using)
   File "/home/dev_mybb/virtualenv/lib/python2.7/site-
 packages/django/core/serializers/base.py", line 201, in save
 models.Model.save_base(self.object, using=using, raw=True, **kwargs)
   File "/home/dev_mybb/virtualenv/lib/python2.7/site-
 packages/django/db/models/base.py", line 736, in save_base
 updated = self._save_table(raw, cls, force_insert, force_update,
 using, update_fields)
   File "/home/dev_mybb/virtualenv/lib/python2.7/site-
 packages/django/db/models/base.py", line 820, in _save_table
 result = self._do_insert(cls._base_manager, using, fields,

Re: [Django] #27796: Middlewares load twice due to StaticFilesHandler(WSGIHandler)

2017-01-30 Thread Django

#27796: Middlewares load twice due to StaticFilesHandler(WSGIHandler)
-+-
 Reporter:  Anthony King |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carl Meyer):

 I've always thought it a bit strange that `StaticFilesHandler` inherits
 `WSGIHandler`; it seems prone to unintended effects like this one. IMO the
 right fix here is to make `StaticFilesHandler` self-contained, even if
 that requires a bit more verbose WSGI-handling code in it.

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

Re: [Django] #27796: Middlewares load twice due to StaticFilesHandler(WSGIHandler)

2017-01-30 Thread Django

#27796: Middlewares load twice due to StaticFilesHandler(WSGIHandler)
-+-
 Reporter:  Anthony King |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Anthony King):

 introduced in
 
https://github.com/django/django/commit/99bb7fcc1859615a7b8c2468e7b97d54853bfb10

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

[Django] #27796: Middlewares load twice due to StaticFilesHandler(WSGIHandler)

2017-01-30 Thread Django

#27796: Middlewares load twice due to StaticFilesHandler(WSGIHandler)
---+
   Reporter:  Anthony King |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  contrib.staticfiles  |Version:  1.10
   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|
---+
 In Django 1.10, a new middleware system was implemented. As part of this
 implementation, loading of middleware was moved to WSGIHandler.__init__.

 When `django.contrib.staticfiles` is used, `StaticFilesHandler` is used as
 part of `runserver`, which causes `WSGIHandler.__init__` to be called
 twice.

 This, in turn, causes the middlewares to all be initialised twice.

 This will affect the majority of development environments. It should not
 affect production environments, as people should not be using `runserver`.

 With the example middleware, you can see the class being initialised
 twice.

 {{{#!python
 # middleware.py
 class ExampleMiddleware(MiddlewareMixin):

 def __init__(self, get_response=None):
 super().__init__(get_response=get_response)
 print("simple_middleware - class: ", time.time(), self)
 }}}

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

[Django] #27795: Audit force_text invocations

2017-01-30 Thread Django

#27795: Audit force_text invocations
-+-
   Reporter:  Claude |  Owner:  Claude Paroz
  Paroz  |
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component:  Utilities  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 `django.utils.encoding.force_text` is called many times in Django code for
 several use cases:
   - force the evaluation of a lazy string
   - convert bytes or a bytestring (PY2) to str
   - convert an object to its string representation

 A global audit is needed to clean that usage, also considering that Python
 3 native strings are more wildly used.
 I'm working on it currently.

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

Re: [Django] #27791: update_or_create() doesn't work properly when model has auto_now=True

2017-01-30 Thread Django

Comment (by Tim Graham):

This looks like invalid usage of `auto_now`. As

[https://docs.djangoproject.com/en/stable/ref/models/fields/#django.db.models.DateField.auto_now
the documentation] says, "Automatically set the field to now every time
the object is saved. Useful for “last-modified” timestamps. Note that the
current date is always used; it’s not just a default value that you can
override." It seems like `update_or_create()` can't work intuitively with
an `auto_now` field as whatever value you specify is ignored.

I'm not sure if anything should be done to improve the situation
considering that there are suggestions to deprecate `auto_now`; see #22995
for details and alternatives.

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

Re: [Django] #27792: Extended category support for Atom and RSS feeds

2017-01-30 Thread Django

#27792: Extended category support for Atom and RSS feeds
-+-
 Reporter:  Pavlo Kapyshin   |Owner:  Pavlo
 |  Kapyshin
 Type:  New feature  |   Status:  assigned
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  feedgenerator| Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Pavlo Kapyshin):

 * needs_docs:  0 => 1


Old description:

> I’m working on category (label, scheme/domain) attributes support for
> Atom and RSS. I have a patch for Atom
> (https://github.com/PavloKapyshin/django/tree/feeds_category_object), and
> want to ask what's the best way to implement same functionality for RSS
> feeds.
>
> RSS domain maps fairly well to Atom's scheme.
>
> Question is: for RSS, should category label be taken from Atom namespace
> (so there'll be an attribute) or just put inside 
> instead of term, if available?

New description:

 I’m working on category (label, scheme/domain) attributes support for Atom
 and RSS. I have a patch for all three feed types:
 https://github.com/PavloKapyshin/django/tree/feeds_category_object

 Next step is to work on docs for this.

--

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

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

Re: [Django] #25889: Organize tests in tests/queries

2017-01-30 Thread Django

Comment (by reficul31):

Replying to [comment:1 Tim Graham]:
> If we can break up the single `tests.py` file into multiple tests files
(perhaps based on the models they use) and `models.py` into a package
similar to `tests/auth_tests/models`, I think that would be a useful task.
If we can do some renaming along the way, that seems okay but it would be
easiest to review in a separate commit from one that moves things around.

I think this sort of thing won't be easy. As most of the models aren't
reused. If the patch required something there was a high chance that the
contributor made the model similar to that given in the ticket. According
to me the maximum we can do is to rename the tests such that they provide
the context of what the test is for without loosing the information
provided by the original author of the test.

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

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

Re: [Django] #23919: Cleanups for when we drop Python 2 compatibility

2017-01-30 Thread Django

#23919: Cleanups for when we drop Python 2 compatibility
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:
 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 Claude Paroz ):

 In [changeset:"52138b1fd08f80fe98def7e22a9693415b4f7744" 52138b1f]:
 {{{
 #!CommitTicketReference repository=""
 revision="52138b1fd08f80fe98def7e22a9693415b4f7744"
 Refs #23919 -- Removed usage of obsolete SafeBytes class

 The class will be removed as part of #27753.
 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/067.3fb459cd2629074531e0d4e647cb1429%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27794: Fix confusing error messages for broken `context_processors`

2017-01-30 Thread Django

#27794: Fix confusing error messages for broken `context_processors`
-+-
 Reporter:  Elena Williams   |Owner:  (none)
 Type:  Uncategorized|   Status:  new
Component:  Error reporting  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  errors,  | Triage Stage:
  context_processors |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Could you given an example of what you mean by a broken context processor?
 Do you mean nonexistent?

 On Python 3, with an `context_processors` entry like
 `'django.core.context_processors.debug'` (which I think is the one used to
 reproduce the screenshot), the error gives the full path which is more
 helpful: "No module named 'django.core.context_processors'.

 Maybe a system check to flag nonexistent context processors would be
 helpful.

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

Re: [Django] #27793: Use Python's ipaddress module for IP validation

2017-01-30 Thread Django

#27793: Use Python's ipaddress module for IP validation
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Utilities|  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:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"277a4dd4b4cc2a2cad77139882f084480751a95a" 277a4dd4]:
 {{{
 #!CommitTicketReference repository=""
 revision="277a4dd4b4cc2a2cad77139882f084480751a95a"
 Fixed #27793 -- Used stdlib's ipaddress module to validate IP addresses

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

Re: [Django] #23919: Cleanups for when we drop Python 2 compatibility

2017-01-30 Thread Django

#23919: Cleanups for when we drop Python 2 compatibility
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:
 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 Claude Paroz ):

 In [changeset:"c688336ebcc1bddc65f2d48e15b981b6caa7ef1a" c688336e]:
 {{{
 #!CommitTicketReference repository=""
 revision="c688336ebcc1bddc65f2d48e15b981b6caa7ef1a"
 Refs #23919 -- Assumed request COOKIES and META are str
 }}}

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

Re: [Django] #27793: Use Python's ipaddress module for IP validation (was: Use the new ipaddress module for IP validation)

2017-01-30 Thread Django

#27793: Use Python's ipaddress module for IP validation
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
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:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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

Re: [Django] #27789: Simplified get sequence value on Oracle.

2017-01-30 Thread Django

#27789: Simplified get sequence value on Oracle.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  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:"89501d9298494d732f56cf577e70d4203f45467b" 89501d92]:
 {{{
 #!CommitTicketReference repository=""
 revision="89501d9298494d732f56cf577e70d4203f45467b"
 Fixed #27789 -- Simplified query for sequence value on Oracle.
 }}}

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

Re: [Django] #23919: Cleanups for when we drop Python 2 compatibility

2017-01-30 Thread Django

#23919: Cleanups for when we drop Python 2 compatibility
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:
 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
--+

Old description:

> This is a tracking ticket of things that we can remove when we drop
> Python 2 compatibility in Django 2.0. Please edit the description of the
> ticket as you come across new items.
>
> * ~~`django.core.mail.message.make_msgid()`~~ #23905
> * ~~`django.dispatch.weakref_backports`~~
> * ~~`django.http.cookie` workarounds~~ (remains for Python 3.4)
> * ~~`django.utils.2to3_fixes`~~
> * ~~`django.utils.decorators.ContextDecorator` ~~
> * `django.utils.encoding`
>  * ~~`@python_2_unicode_compatible`~~
>  * ~~force/smart _unicode~~
>  * either force/smart _text or force/smart _str
> [https://github.com/django/django/pull/7913 PR]
> * ~~`django.utils.html_parser.use_workaround`~~
> * ~~`django.utils.http` functions like `urlquote_plus` -- I think the
> versions of these functions on Python 3 don't have the unicode characters
> bug we are working around [https://github.com/django/django/pull/7953 PR]
> * ~~Stop using `django.utils.lru_cache`~~
> * ~~Figure the deprecation plan for `django.utils.lru_cache`~~ (staying
> for now)
> * ~~`django.utils.six`~~
> * ~~`from __future__ import unicode_literals`~~
> * ~~`str()` stuff for environment variables, e.g.
> 0bfb53866199f366ed140d49938fd185e5898156~~
> * ~~`str()` stuff for `type(name)` and `__name__`~~
> * ~~Inheriting from `object` in `django.core.servers.basehttp` (and
> perhaps other places) ala 4ee06ec3fc8e94d164afbd2f9c880c60c658a9ac~~
> * ~~`git grep 'long int'` (mostly docs)~~
> * ~~`django.utils._os [npath,upath]`~~
> * ~~In tests: `contextlib.closing(self.urlopen` (`contextlib.closing` no
> longer needed)~~
> * ~~Support for pysqlite (doesn't support Python 3)~~
> * ~~Replace `super(ClassName, self)` with `super()`~~
> [https://github.com/django/django/pull/7905 PR]
> * ~~Remove `# -*- coding: utf-8 -*-` source file encoding~~ (that's the
> default on Python 3)
> * Evaluate replacement of custom `__del__` methods by
> [https://docs.python.org/3/library/weakref.html#weakref.finalize
> weakref.finalize]
> * ~~Remove `__ne__` from objects already defining a `__eq__`~~
> * ~~Remove note about PYTHONHASHSEED (see #26243)~~
> * Remove Field.creation_counter (replace by metaclass `__prepare__`
> returning `OrderedDict()`,
> https://docs.python.org/3/reference/datamodel.html#preparing-the-class-
> namespace)
> * ~~`django.test.utils.reset_warning_registry()`~~
> * ~~Replace `errno` checks by `IOError` subclasses defined by
> [https://www.python.org/dev/peps/pep-3151/ PEP 3151]~~
> [https://github.com/django/django/pull/7915 PR]
> * ~~`django.utils.glob`~~
> * ~~`django.utils.cookies.SimpleCookie`~~ (remains for Python 3.4
> compatibility)
> * ~~`django.test.mock`~~
> * ~~Replace `tempfile.mkdtemp` + remove with
> `tempfile.TemporaryDirectory` context manager~~
> * ~~Replace `io.open()` by a plain `open()`~~
> * ~~Evaluate need for `assertRegex`, `assertRaisesRegex` in tests. Some
> usage is merely to account for differences in messages between Python 2
> and 3.~~
> * ~~`re.U`, `re.UNICODE` (default behavior of Python 3)~~ -
> [https://github.com/django/django/pull/7879 PR 7879]

New description:

 This is a tracking ticket of things that we can remove when we drop Python
 2 compatibility in Django 2.0. Please edit the description of the ticket
 as you come across new items.

 * ~~`django.core.mail.message.make_msgid()`~~ #23905
 * ~~`django.dispatch.weakref_backports`~~
 * ~~`django.http.cookie` workarounds~~ (remains for Python 3.4)
 * ~~`django.utils.2to3_fixes`~~
 * ~~`django.utils.decorators.ContextDecorator` ~~
 * `django.utils.encoding`
  * ~~`@python_2_unicode_compatible`~~
  * ~~force/smart _unicode~~
  * either force/smart _text or force/smart _str
 [https://github.com/django/django/pull/7913 PR]
 * ~~`django.utils.html_parser.use_workaround`~~
 * ~~`django.utils.http` functions like `urlquote_plus` -- I think the
 versions of these functions on Python 3 don't have the unicode characters
 bug we are working around [https://github.com/django/django/pull/7953 PR]
 * ~~Stop using `django.utils.lru_cache`~~
 * ~~Figure the deprecation plan for `django.utils.lru_cache`~~ (staying
 for now)
 * ~~`django.utils.six`~~
 * ~~`from __future__ import unicode_literals`~~
 * ~~`str()` stuff

Re: [Django] #27697: JSONField with blank=True is rendered as non-required field in a ModelForm

2017-01-30 Thread Django

#27697: JSONField with blank=True is rendered as non-required field in a 
ModelForm
-+-
 Reporter:  aruseni  |Owner:  Andrew
 |  Nester
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  postgres | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Andrew Nester):

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

Re: [Django] #27697: JSONField with blank=True is rendered as non-required field in a ModelForm

2017-01-30 Thread Django

#27697: JSONField with blank=True is rendered as non-required field in a 
ModelForm
-+-
 Reporter:  aruseni  |Owner:  Andrew
 |  Nester
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  postgres | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Andrew Nester):

 * owner:  (none) => Andrew Nester
 * status:  new => assigned


Comment:

 I've added pull request [https://github.com/django/django/pull/7990 #PR]

 I've decided to make logic so: if we have {{{blank=True}}} and
 {{{null=False}}} for {{{JSONField}}}, we make this field required with
 empty value set to } }}}

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

Re: [Django] #24686: Support for Moving a model between two Django apps

2017-01-30 Thread Django

#24686: Support for Moving a model between two Django apps
---+
 Reporter:  Alex Rothberg  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Migrations |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Petr Dlouhý):

 Maybe this could be separated into two separate tasks.
 We could first create database operation like
 `django.db.models.MoveToApp`. This alone could save a lot of manual work
 and confusion for developers.

 Second stage would be creating the autodetection mechanism, which would
 make migrations with this operation automatically.

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

Re: [Django] #27784: Custom Site model support for django.contrib.sites.

2017-01-30 Thread Django

#27784: Custom Site model support for django.contrib.sites.
-+-
 Reporter:  Massimo Scamarcia|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.sites|  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  sites swappable  | Triage Stage:
  models |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Massimo Scamarcia):

 Replying to [comment:4 Tim Graham]:
 > You should continue the discussion on the mailing list. We won't make a
 change either way without a consensus there.

 Ok thanks, I will do.

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

Re: [Django] #27742: Unexpected migration on Parent -> child model inheritence

2017-01-30 Thread Django

Comment (by Markus Holtermann):

Replying to [comment:6 Anthony King]:
> What are the implications for distributed packages that have parent ->
child models, and intend to support older versions of Django?

Django's version support for migrations is outlined
inhttps://docs.djangoproject.com/en/1.10/topics/migrations/#supporting-
multiple-django-versions . I see how this will lead to errors on 1.11 if
you want to check that all required migrations have been applied. I'll try
to come up with a solution or workaround for your 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.33976d79e0e3acdeaec8c9b08a2ed82c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27794: Fix confusing error messages for broken `context_processors`

2017-01-30 Thread Django

#27794: Fix confusing error messages for broken `context_processors`
-+-
 Reporter:  Elena Williams   |Owner:  (none)
 Type:  Uncategorized|   Status:  new
Component:  Error reporting  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  errors,  | Triage Stage:
  context_processors |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 Any error message improvement is welcome when it's possible. Did you spot
 the location in Django where the import swallowed the initial exception?

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

Re: [Django] #22669: bulk_create with empty model fields fails on oracle

2017-01-30 Thread Django

#22669: bulk_create with empty model fields fails on oracle
-+-
 Reporter:  sns1081@…|Owner:  Michael
 |  Nacharov
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  QuerySet.bulk_create   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Michael Nacharov):

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

38 matches

Mail list logo