Re: [Django] #26629: Login failures should be logged

[Django]

#26629: Login failures should be logged
-+-
 Reporter:  jacobian |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  login security   | Triage Stage:
  logigng|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mallyvai):

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


Comment:

 Unsure about correct process, but I reopened the original ticket. Should I
 set that to New instead?

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

Re: [Django] #26670: makemessages' plural form handling helper function can insert extra empty line in PO file

[Django]

#26670: makemessages' plural form handling helper function can insert extra 
empty
line in PO file
-+-
 Reporter:  ramiro   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:   |  Version:  master
  Internationalization   |
 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
-+-
Description changed by ramiro:

Old description:

> When it copieds the plural form formula header line from Django
> translations it can insert a line with a triling newline:
>
> https://github.com/django/django/blob/4731e9d82ea72b6d793fb06713d11d228eb89ace/django/core/management/commands/makemessages.py#L624
>
> This is mostly a correctness issue rarely seen in final PO files as
> makemessages usually runs
> the resulting PO file through additional invocations of gettext tools
> which can correct the issue in case the plural forms formula PO header
> line is the last one.

New description:

 When it copies the plural form formula header line from Django
 translations it can insert a line with a triling newline:

 
https://github.com/django/django/blob/4731e9d82ea72b6d793fb06713d11d228eb89ace/django/core/management/commands/makemessages.py#L624

 This is mostly a correctness issue rarely seen in final PO files as
 makemessages usually runs
 the resulting PO file through additional invocations of gettext tools
 which can correct the issue in case the plural forms formula PO header
 line is the last one.

--

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

Re: [Django] #26670: makemessages' plural form handling helper function can insert extra empty line in PO file

[Django]

#26670: makemessages' plural form handling helper function can insert extra 
empty
line in PO file
-+-
 Reporter:  ramiro   |Owner:  ramiro
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:   |  Version:  master
  Internationalization   |
 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 ramiro):

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

[Django] #26670: makemessages' plural form handling helper function can insert extra empty line in PO file

[Django]

#26670: makemessages' plural form handling helper function can insert extra 
empty
line in PO file
+
   Reporter:  ramiro|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Internationalization  |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 |
+
 When it copieds the plural form formula header line from Django
 translations it can insert a line with a triling newline:

 
https://github.com/django/django/blob/4731e9d82ea72b6d793fb06713d11d228eb89ace/django/core/management/commands/makemessages.py#L624

 This is mostly a correctness issue rarely seen in final PO files as
 makemessages usually runs
 the resulting PO file through additional invocations of gettext tools
 which can correct the issue in case the plural forms formula PO header
 line is the last one.

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

Re: [Django] #26644: [Regression?] SuspiciousFileOperation when creating a File from a NamedTemporaryFile

[Django]

#26644: [Regression?] SuspiciousFileOperation when creating a File from a
NamedTemporaryFile
-+-
 Reporter:  hobarrera|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  1.10
  uploads/storage|
 Severity:  Release blocker  |   Resolution:
 Keywords:  File,| Triage Stage:  Accepted
  SuspiciousFileOperation,   |
  NamedTemporaryFile, regression |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 Sure, at least seeing the regression test in your PR will help me
 understand the problem a bit more.

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

Re: [Django] #26659: Allow filtering of which tests run (was: New parameter for test methods filtering)

[Django]

#26659: Allow filtering of which tests run
-+-
 Reporter:  apiraino |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  tests| Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

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

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

Re: [Django] #26659: New parameter for test methods filtering

[Django]

#26659: New parameter for test methods filtering
-+-
 Reporter:  apiraino |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  tests| Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * component:  Uncategorized => Testing framework
 * easy:  1 => 0
 * stage:  Unreviewed => Someday/Maybe


Comment:

 I'm more convinced by [https://groups.google.com/d/msg/django-
 developers/W6YiFg9ITg0/Uk8U7D3JBgAJ Josh's proposal] on the mailing list
 thread about the possibility of using glob-style patterns. Perhaps adding
 a new parameter to the test runner isn't needed. I'd also like to see if
 any other testing tools implement something similar. The problem this
 ticket aims to address doesn't seem Django specific.

 The change in the output format was proposed in #23332. Perhaps you could
 try addressing [http://bugs.python.org/issue22431 the Python issue]
 spawned by that ticket. We might consider reopening the Django ticket in
 light of your solution if the issue cannot be addressed upstream. For
 future reference, please don't combined multiple features in a single
 ticket.

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

Re: [Django] #26663: libgeos in django makes a gevent gunicorn worker crash

[Django]

#26663: libgeos in django makes a gevent gunicorn worker crash
---+--
 Reporter:  tapanpandita   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords:  libgeos geodjango  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timgraham):

 Also reported on [https://groups.google.com/d/topic/django-
 users/zfqG7ZR3rQE/discussion django-users].

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

Re: [Django] #25777: Django admin/views don't expect forms to fail after validation

[Django]

#25777: Django admin/views don't expect forms to fail after validation
-+--
 Reporter:  vzima|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.8
 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 timgraham):

 * type:  Uncategorized => New feature
 * component:  Uncategorized => Forms


Comment:

 [https://groups.google.com/d/topic/django-
 developers/Dju2vvbzECI/discussion django-developers thread]

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

Re: [Django] #26655: Provide a hook to handle database exceptions in Django Admin

[Django]

#26655: Provide a hook to handle database exceptions in Django Admin
---+--
 Reporter:  nickretallack  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 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 timgraham):

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


Comment:

 Discussion perhaps to be continued on a related
 [https://groups.google.com/d/topic/django-
 developers/Dju2vvbzECI/discussion django-developers thread].

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

Re: [Django] #26621: simplify_regex handles named capture groups incorrectly (was: simplify_regex having problems with named capture groups)

[Django]

#26621: simplify_regex handles named capture groups incorrectly
---+
 Reporter:  cancan101  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admindocs  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * component:  Uncategorized => contrib.admindocs
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Old description:

> For example using the regex from [here](http://www.django-rest-
> framework.org/api-guide/versioning/):
>

> {{{
> simplify_regex(r'^(?P(v1|v2))/bookings/(?P[0-9]+)/$')
>
> '/)/bookings//'
> }}}
>
> Escaping the `/` does not seem to help.

New description:

 For example using a regex from [http://www.django-rest-framework.org/api-
 guide/versioning/  Django Rest Framework docs]:

 {{{
 >>> from django.contrib.admindocs.views import simplify_regex
 >>> simplify_regex(r'^(?P(v1|v2))/bookings/(?P[0-9]+)/$')
 '/)/bookings//'
 }}}

 The closing parenthesis in the output is unexpected.

 Escaping the `/` does not seem to help.

--

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

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

Re: [Django] #26628: Document that CSRF violations are logged to the django.request logger (was: CSRF violations should be logged)

[Django]

#26628: Document that CSRF violations are logged to the django.request logger
--+
 Reporter:  jacobian  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  csrf security | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * status:  closed => new
 * type:  New feature => Cleanup/optimization
 * component:  CSRF => Documentation
 * resolution:  worksforme =>
 * 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/066.226e82ede2f3f800884303b7e6f8240a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26635: Clarify "memory_cost" of Argon2PasswordHasher differs from command line utility (was: "memory_cost" of Argon2PasswordHasher)

[Django]

#26635: Clarify "memory_cost" of Argon2PasswordHasher differs from command line
utility
--+
 Reporter:  danielfeng|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * component:  contrib.auth => Documentation
 * stage:  Unreviewed => Accepted


Comment:

 Sounds good, thanks!

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

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

Re: [Django] #26624: Error when running sqlmigrate after dropping index (of index_together) without actually migrating

[Django]

#26624: Error when running sqlmigrate after dropping index (of index_together)
without actually migrating
-+-
 Reporter:  akki |Owner:  
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sqlmigrate db-   | Triage Stage:  Accepted
  indexes|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * keywords:  sqlmigrate index => sqlmigrate db-indexes
 * stage:  Unreviewed => Accepted


Comment:

 Traceback is for PostgreSQL. Seems to work on SQLite, but not on MySQL.

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

Re: [Django] #26635: "memory_cost" of Argon2PasswordHasher

[Django]

#26635: "memory_cost" of Argon2PasswordHasher
-+-
 Reporter:  danielfeng   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.auth |  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
-+-

Comment (by bwesterb):

 Replying to [comment:4 timgraham]:
 > Is this a release blocker for Django 1.10? I'm not clear what the next
 steps are.

 In my opinion this shouldn't be a blocker: it only affects those who
 choose a configuration different from the default.  If you want, I could
 write a PR tomorrow which adds a mention in the docs and code that the
 memory_cost attribute we use is the same as in the API, but different from
 the commandline utility.

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

Re: [Django] #26652: Model instance no longer has a _default_manager attribute

[Django]

#26652: Model instance no longer has a _default_manager attribute
--+
 Reporter:  rsalmaso  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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:  1 |UI/UX:  0
--+

Comment (by rsalmaso):

 Ok, thanks.
 I'll open a ticket on django-paypal.

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

Re: [Django] #26619: BaseCache incr method will reset the timeout

[Django]

#26619: BaseCache incr method will reset the timeout
-+-
 Reporter:  nitely   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  cache, incr, | Triage Stage:  Accepted
  DatabaseCache, BaseCache   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 Some discussion on the DevelopersMailingList may be useful to decide on
 how to proceed.

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

Re: [Django] #26651: Keep uploaded file suffix for TemporaryUploadedFile

[Django]

#26651: Keep uploaded file suffix for TemporaryUploadedFile
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  File |  Version:  master
  uploads/storage|
 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 timgraham):

 * cc: axiak (added)
 * component:  Core (Other) => File uploads/storage


Comment:

 Michael, it looks like you may have been involved in the original design
 of this (ticket:2070#comment:129). Do you have any thoughts?

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

Re: [Django] #26556: set_language with i18n_patterns doesn't work all the time

[Django]

#26556: set_language with i18n_patterns doesn't work all the time
--+
 Reporter:  hchargois |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

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

Re: [Django] #26556: set_language with i18n_patterns doesn't work all the time

[Django]

#26556: set_language with i18n_patterns doesn't work all the time
-+-
 Reporter:  hchargois|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.9
  Internationalization   |
 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 aaugustin):

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


Comment:

 The description makes sense. (I didn't attempt to reproduce.)

 The reason why set_language shouldn't be in i18n_patterns is discussed in
 #18472:

 > I've seen people get confused by including the `set_language` URL within
 their `i18n_patterns` and wondering why it doesn't work (the form `POST`
 turns into a redirected `GET` request which fails); we should probably add
 a warning to ensure that this URL is locale-independent

 (There's nothing else about this issue in that ticket.)

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

Re: [Django] #26635: "memory_cost" of Argon2PasswordHasher

[Django]

#26635: "memory_cost" of Argon2PasswordHasher
-+-
 Reporter:  danielfeng   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.auth |  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
-+-

Comment (by timgraham):

 Is this a release blocker for Django 1.10? I'm not clear what the next
 steps are.

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

Re: [Django] #26661: Why not using AppConfig's name attribute instead of app_name in urls.py?

[Django]

#26661: Why not using AppConfig's name attribute instead of app_name in urls.py?
---+--
 Reporter:  john-bonachon  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Core (Other)   |  Version:  1.9
 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 timgraham):

 * cc: knbk (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 I seems to remember discussing this during the development of this feature
 (#21927) but I'm not certain. Marten, do you recall?

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

Re: [Django] #26652: Model instance no longer has a _default_manager attribute

[Django]

#26652: Model instance no longer has a _default_manager attribute
--+
 Reporter:  rsalmaso  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_docs:  1 => 0
 * has_patch:  0 => 1


Comment:

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

Re: [Django] #26647: Post migrate signal old content type model

[Django]

#26647: Post migrate signal old content type model
-+-
 Reporter:  jlemaes  |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.10
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"dfae72f45a74b8fe3a08fe0a48c11bfeb9b9efda" dfae72f]:
 {{{
 #!CommitTicketReference repository=""
 revision="dfae72f45a74b8fe3a08fe0a48c11bfeb9b9efda"
 [1.10.x] Fixed #26647 -- Included the state of all applied migrations when
 migrating forward.

 Thanks Jasper Maes for the detailed report.

 Backport of 36d36818a30025034cad6f1ee59b2a960a6582ec from master
 }}}

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

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

Re: [Django] #26647: Post migrate signal old content type model

[Django]

#26647: Post migrate signal old content type model
-+-
 Reporter:  jlemaes  |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.10
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"36d36818a30025034cad6f1ee59b2a960a6582ec" 36d3681]:
 {{{
 #!CommitTicketReference repository=""
 revision="36d36818a30025034cad6f1ee59b2a960a6582ec"
 Fixed #26647 -- Included the state of all applied migrations when
 migrating forward.

 Thanks Jasper Maes for the detailed report.
 }}}

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

Re: [Django] #26664: Support of model_object.delete(cascade=True)

[Django]

#26664: Support of model_object.delete(cascade=True)
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 timgraham):

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


Comment:

 This seems a bit dangerous to me. In particular, there's no way to control
 how far or to which relations the deletions will cascade. I think it's
 safer to explicitly handle the deletions in a use case like this. Of
 course, you can also override the `Model.delete()` method to have whatever
 behavior you like.

 If you can find consensus on the DevelopersMailingList to add something
 like this, I'll be happy to reopen the ticket.

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

Re: [Django] #26647: Post migrate signal old content type model

[Django]

#26647: Post migrate signal old content type model
-+-
 Reporter:  jlemaes  |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.10
 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 timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #26669: UnicodeDecodeError with non-ASCII string in 'Content-Type' header

[Django]

#26669: UnicodeDecodeError with non-ASCII string in 'Content-Type' header
-+-
 Reporter:  karech   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  UnicodeDecodeError   |  worksforme
  request META CONTENT_TYPE  | Triage Stage:
  Content-Type   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Perhaps there's something missing in the report but I can't reproduce a
 crash. Perhaps you could provide a test for Django's test suite instead?

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

Re: [Django] #26652: Model instance no longer has a _default_manager attribute

[Django]

#26652: Model instance no longer has a _default_manager attribute
--+
 Reporter:  rsalmaso  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by loic):

 * component:  Database layer (models, ORM) => Documentation
 * needs_docs:  0 => 1
 * type:  Uncategorized => Cleanup/optimization
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Managers were never intended to be accessible on model instances, we even
 
[https://github.com/django/django/blob/30d110ef43d8a3c50ea8ec4e4fe49bd2bb859530/django/db/models/manager.py#L186
 use a descriptor to prevent that usage] but  `_default_manager` somehow
 escaped that restriction. I guess we can mention the change in the release
 notes.

 For completeness I'll mention that if we really wanted these available on
 the instance we could just move the properties from `ModelBase` to
 `models.Model`, but I don't think we should.

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

Re: [Django] #26666: assertRedirects gives unhelpful error message expected URL is external

[Django]

#2: assertRedirects gives unhelpful error message expected URL is external
--+
 Reporter:  inglesp   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * type:  Bug => Cleanup/optimization
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 The message could suggest using the `fetch_redirect_response=False`
 argument.

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

Re: [Django] #26618: Improve error message when AppConfig.name is invalid

[Django]

#26618: Improve error message when AppConfig.name is invalid
--+
 Reporter:  alasdairnicol |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * component:  Error reporting => Core (Other)
 * needs_tests:  1 => 0
 * owner:   => nobody
 * needs_docs:  1 => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I don't think any documentation changes are required.

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

Re: [Django] #26652: Model instance no longer has a _default_manager attribute (was: missing _default_manager in model instance)

[Django]

#26652: Model instance no longer has a _default_manager attribute
-+-
 Reporter:  rsalmaso |Owner:  nobody
 Type:  Uncategorized|   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
-+-
Changes (by timgraham):

 * cc: loic (added)


Comment:

 Bisected to ed0ff913c648b16c4471fc9a9441d1ee48cb5420.

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

Re: [Django] #26656: Add timedelta support to DjangoJSONEncoder

[Django]

#26656: Add timedelta support to DjangoJSONEncoder
--+
 Reporter:  willhardy |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Serialization)  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #26668: HTTPResponse.content is not unicode in context of test cases.

[Django]

#26668: HTTPResponse.content is not unicode in context of test cases.
---+--
 Reporter:  wjdp   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.8
 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 wjdp):

 Feel free to mark as invalid.

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

Re: [Django] #26668: HTTPResponse.content is not unicode in context of test cases.

[Django]

#26668: HTTPResponse.content is not unicode in context of test cases.
---+--
 Reporter:  wjdp   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  1.8
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by charettes):

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


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

Re: [Django] #26668: HTTPResponse.content is not unicode in context of test cases.

[Django]

#26668: HTTPResponse.content is not unicode in context of test cases.
---+--
 Reporter:  wjdp   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.8
 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 wjdp):

 Ah, must have glossed over that, `assertContains` seems to fix all of
 this. `unicode_literals` was unrelated I think, just fixing up use of
 literals.

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

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value (was: RenameModel should rename indexes, constraints, sequences and tri

[Django]

#23577: Rename operations should rename indexes, constraints, sequences and
triggers named after their former value
+
 Reporter:  CrimsonZen  |Owner:
 Type:  Bug |   Status:  new
Component:  Migrations  |  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 charettes):

 This should also be the case for `AlterField` operations on both sides
 (e.g. foreign key constraint names are generated from their referenced
 table and column names).

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

Re: [Django] #26638: Allow callable in defaults argument for QuerySet.get_or_create

[Django]

#26638: Allow callable in defaults argument for QuerySet.get_or_create
-+-
 Reporter:  mlorant  |Owner:
 |  ddsnowboard
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #22931: Migrations cannot rename intermediate models

[Django]

#22931: Migrations cannot rename intermediate models
-+-
 Reporter:  JockeTF  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  migrations migrate   | Triage Stage:  Accepted
  makemigrations rename  |
  intermediate model |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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


Comment:

 Let's close this ticket as a duplicate in this 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/065.1fcdba70ad15d871c3a0dbbc91ef344c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26663: libgeos in django makes a gevent gunicorn worker crash

[Django]

#26663: libgeos in django makes a gevent gunicorn worker crash
---+--
 Reporter:  tapanpandita   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords:  libgeos geodjango  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timgraham):

 Can you provide a minimal project to reproduce the crash?

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

Re: [Django] #26645: Errors when running i18n makemessages tests on Windows

[Django]

#26645: Errors when running i18n makemessages tests on Windows
--+
 Reporter:  ramiro|Owner:  ramiro
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  windows makemessages  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #26658: "When Case" query generating rule in duplicate

[Django]

#26658: "When Case" query generating rule in duplicate
-+-
 Reporter:  imaia|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 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 timgraham):

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

Re: [Django] #26656: Add timedelta support to DjangoJSONEncoder

[Django]

#26656: Add timedelta support to DjangoJSONEncoder
-+-
 Reporter:  willhardy|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core |  Version:  1.9
  (Serialization)|
 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 willhardy):

 See [https://github.com/django/django/pull/6651 another PR], using a ISO
 8601 string instead of a float.

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

Re: [Django] #26616: Documentation: Improve description of AppConfig.ready()

[Django]

#26616: Documentation: Improve description of AppConfig.ready()
--+
 Reporter:  marfire   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #26634: Add the ability to do subselects for querying versioned data

[Django]

#26634: Add the ability to do subselects for querying versioned data
-+-
 Reporter:  dhobbs   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * component:  Uncategorized => Database layer (models, ORM)
 * type:  Uncategorized => New feature
 * 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/064.9f4ef20728aba03e9709765ee00430d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26669: UnicodeDecodeError with non-ASCII string in 'Content-Type' header

[Django]

#26669: UnicodeDecodeError with non-ASCII string in 'Content-Type' header
-+-
 Reporter:  karech   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  HTTP |Version:  1.8
  handling   |   Keywords:  UnicodeDecodeError request META
 Severity:  Normal   |  CONTENT_TYPE Content-Type
 Triage Stage:   |  Has patch:  0
  Unreviewed |
Easy pickings:  0|  UI/UX:  0
-+-
 If someone sends POST request with headers containing non-ASCII value for
 'Content-Type', then django raises UnicodeDecodeError.

 {{{#!python
 Traceback (most recent call last):
   File "/usr/lib/python2.7/wsgiref/handlers.py", line 85, in run
 self.result = application(self.environ, self.start_response)
   File "/usr/lib/python2.7/site-
 packages/django/contrib/staticfiles/handlers.py", line 63, in __call__
 return self.application(environ, start_response)
   File "/usr/lib/python2.7/site-packages/django/core/handlers/wsgi.py",
 line 189, in __call__
 response = self.get_response(request)
   File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py",
 line 218, in get_response
 response = self.handle_uncaught_exception(request, resolver,
 sys.exc_info())
   File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py",
 line 261, in handle_uncaught_exception
 return debug.technical_500_response(request, *exc_info)
   File "/usr/lib/python2.7/site-packages/django/views/debug.py", line 97,
 in technical_500_response
 html = reporter.get_traceback_html()
   File "/usr/lib/python2.7/site-packages/django/views/debug.py", line 383,
 in get_traceback_html
 c = Context(self.get_traceback_data(), use_l10n=False)
   File "/usr/lib/python2.7/site-packages/django/views/debug.py", line 328,
 in get_traceback_data
 frames = self.get_traceback_frames()
   File "/usr/lib/python2.7/site-packages/django/views/debug.py", line 501,
 in get_traceback_frames
 'vars': self.filter.get_traceback_frame_variables(self.request,
 tb.tb_frame),
   File "/usr/lib/python2.7/site-packages/django/views/debug.py", line 234,
 in get_traceback_frame_variables
 cleansed[name] = self.cleanse_special_types(request, value)
   File "/usr/lib/python2.7/site-packages/django/views/debug.py", line 191,
 in cleanse_special_types
 value = self.get_request_repr(value)
   File "/usr/lib/python2.7/site-packages/django/views/debug.py", line 122,
 in get_request_repr
 return build_request_repr(request,
 POST_override=self.get_post_parameters(request))
   File "/usr/lib/python2.7/site-packages/django/views/debug.py", line 186,
 in get_post_parameters
 return request.POST
   File "/usr/lib/python2.7/site-packages/django/core/handlers/wsgi.py",
 line 137, in _get_post
 self._load_post_and_files()
   File "/usr/lib/python2.7/site-packages/django/http/request.py", line
 253, in _load_post_and_files
 if self.META.get('CONTENT_TYPE', '').startswith('multipart/form-
 data'):
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 0:
 ordinal not in range(128)
 }}}

 How reproduce:
 {{{#!python
 import requests

 url = 'http://somesite.com/view_with_post_method'
 headers = {'Content-Type': b'\xf0'}
 requests.post(url, headers=headers)
 }}}

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

Re: [Django] #26667: Invalid query for OneToOneField if 'to_field' specified and primary_key=True

[Django]

#26667: Invalid query for OneToOneField if 'to_field'  specified and
primary_key=True
-+-
 Reporter:  kwist|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  OneToOneField| Triage Stage:  Accepted
  to_field primary_key   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * type:  Uncategorized => Bug
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 Bisected to 9ed82154bd0bd01c6195942db84302e791ad366f.

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

Re: [Django] #26668: HTTPResponse.content is not unicode in context of test cases.

[Django]

#26668: HTTPResponse.content is not unicode in context of test cases.
---+--
 Reporter:  wjdp   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.8
 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 charettes):

 I also noticed that the
 [https://docs.djangoproject.com/en/1.9/topics/python3/#httprequest-and-
 httpresponse-objects Porting to Python 3 guide] mentions why
 `assertContains` should be used instead.

 Is this the reason you added the `from __future__ import unicode_literals`
 import in the first place?

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

Re: [Django] #26668: HTTPResponse.content is not unicode in context of test cases.

[Django]

#26668: HTTPResponse.content is not unicode in context of test cases.
---+--
 Reporter:  wjdp   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.8
 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 charettes):

 The `SimpleTestCase` class already provides the
 
[https://docs.djangoproject.com/en/1.9/topics/testing/tools/#django.test.SimpleTestCase.assertContains
 assertContains method] for this use case.

 I'm afraid there's not much we can do to make the error message more
 descriptive as that's standard Python stuff.

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

Re: [Django] #26668: HTTPResponse.content is not unicode in context of test cases.

[Django]

#26668: HTTPResponse.content is not unicode in context of test cases.
---+--
 Reporter:  wjdp   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.8
 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 wjdp):

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


Old description:

> Came across the following when adding `from __future__ import
> unicode_literals` to my test.py-s
>
> When doing the following for an existing view with an expected output:
>
> {{{
> def test_page_not_found(self):
> url = '/help/404/'
> c = self.get_client()
> response = c.get(url)
> self.assertIn("Page Not Found", response.content)
> }}}
>
> We get:
>
> {{{
> ==
> ERROR: test_page_not_found (xsd_help.tests.HelpViewTest)
> --
> Traceback (most recent call last):
>   File "/builds/wjdp/xsacdb/src/xsd_help/tests.py", line 23, in
> test_page_not_found
> self.assertTrue("Page Not Found" in response.content)
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
> 21370: ordinal not in range(128)
> }}}
>
> Workaround is to replace `response.content` with
> `unicode(response.content, encoding=settings.DEFAULT_ENCODING)`.
> According to what I could find in the docs the content should be encoded
> with uft-8, I think this issue is because `request.content` is a
> bytestring without an encoding attached.
>
> I'm raising this either in case this in not expected or if it is
> suggesting a more descriptive error is generated and/or better
> documentation for those who come across this - there was a *lot* of
> headscratching needed to find the root of these test failures.
>
> Another suggestion: could we have another property of HTTPResponse that
> gives us a unicode string rather than a bytestring for test cases?
>
> See http://stackoverflow.com/questions/36004324/function-assertin-causes-
> the-unicodedecodeerror/37456287 for another similar use case.

New description:

 Came across the following when adding `from __future__ import
 unicode_literals` to my test.py-s

 When doing the following for an existing view with an expected output:

 {{{
 def test_page_not_found(self):
 url = '/help/404/'
 c = self.get_client()
 response = c.get(url)
 self.assertIn("Page Not Found", response.content)
 }}}

 We get:

 {{{
 ==
 ERROR: test_page_not_found (xsd_help.tests.HelpViewTest)
 --
 Traceback (most recent call last):
   File "/builds/wjdp/xsacdb/src/xsd_help/tests.py", line 23, in
 test_page_not_found
 self.assertTrue("Page Not Found" in response.content)
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
 21370: ordinal not in range(128)
 }}}

 Workaround is to replace `response.content` with
 `unicode(response.content, encoding=settings.DEFAULT_CHARSET)`. According
 to what I could find in the docs the content should be encoded with uft-8,
 I think this issue is because `request.content` is a bytestring without an
 encoding attached.

 I'm raising this either in case this in not expected or if it is
 suggesting a more descriptive error is generated and/or better
 documentation for those who come across this - there was a *lot* of
 headscratching needed to find the root of these test failures.

 Another suggestion: could we have another property of HTTPResponse that
 gives us a unicode string rather than a bytestring for test cases?

 See http://stackoverflow.com/questions/36004324/function-assertin-causes-
 the-unicodedecodeerror/37456287 for another similar use 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/062.524f9253d50d78e1ef38935fd8e4e4e6%40djangoproject.com.
For more options, visit 

[Django] #26668: HTTPResponse.content is not unicode in context of test cases.

[Django]

#26668: HTTPResponse.content is not unicode in context of test cases.
---+
 Reporter:  wjdp   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  HTTP handling  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Came across the following when adding `from __future__ import
 unicode_literals` to my test.py-s

 When doing the following for an existing view with an expected output:

 {{{
 def test_page_not_found(self):
 url = '/help/404/'
 c = self.get_client()
 response = c.get(url)
 self.assertIn("Page Not Found", response.content)
 }}}

 We get:

 {{{
 ==
 ERROR: test_page_not_found (xsd_help.tests.HelpViewTest)
 --
 Traceback (most recent call last):
   File "/builds/wjdp/xsacdb/src/xsd_help/tests.py", line 23, in
 test_page_not_found
 self.assertTrue("Page Not Found" in response.content)
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
 21370: ordinal not in range(128)
 }}}

 Workaround is to replace `response.content` with
 `unicode(response.content, encoding=settings.DEFAULT_ENCODING)`. According
 to what I could find in the docs the content should be encoded with uft-8,
 I think this issue is because `request.content` is a bytestring without an
 encoding attached.

 I'm raising this either in case this in not expected or if it is
 suggesting a more descriptive error is generated and/or better
 documentation for those who come across this - there was a *lot* of
 headscratching needed to find the root of these test failures.

 Another suggestion: could we have another property of HTTPResponse that
 gives us a unicode string rather than a bytestring for test cases?

 See http://stackoverflow.com/questions/36004324/function-assertin-causes-
 the-unicodedecodeerror/37456287 for another similar use 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/047.d8ec3db89b680381af10b93d7d9a8f56%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26667: Invalid query for OneToOneField if 'to_field' specified and primary_key=True

[Django]

#26667: Invalid query for OneToOneField if 'to_field'  specified and
primary_key=True
-+-
 Reporter:  kwist|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  OneToOneField| Triage Stage:
  to_field primary_key   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by kwist):

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


Old description:

> Given the following models:
> {{{
> #!python
> class Model1(models.Model):
> str_id = models.CharField(max_length=12, unique=True)
>

> class Model2(models.Model):
> model1 = models.OneToOneField(Model1, to_field='str_id',
> primary_key=True)
> }}}
>
> In Django 1.9 query:
> {{{
> #!python
> Model2.objects.filter(model1=instance_model1)
> }}}
> always returns an empty list, though in Django 1.8 works
>
> Django 1.9 query
> {{{
> #!python
> In [4]: print Model2.objects.filter(model1=model1).query
> SELECT "app_model2"."model1_id" FROM "app_model2" WHERE
> "app_model2"."model1_id" = 1
> }}}
>
> Django 1.8 query
> {{{
> #!python
> In [4]: print Model2.objects.filter(model1=model1).query
> SELECT `app_model2`.`model1_id` FROM `app_model2` WHERE
> `app_model2`.`model1_id` = 1234567890ax
> }}}

New description:

 Given the following models:
 {{{
 #!python
 class Model1(models.Model):
 str_id = models.CharField(max_length=12, unique=True)


 class Model2(models.Model):
 model1 = models.OneToOneField(Model1, to_field='str_id',
 primary_key=True)
 }}}

 In Django 1.9 query:
 {{{
 #!python
 Model2.objects.filter(model1=instance_model1)
 }}}
 always returns an empty list, though in Django 1.8 works

 Django 1.9 query
 {{{
 #!python
 In [4]: print Model2.objects.filter(model1=instance_model1).query
 SELECT "app_model2"."model1_id" FROM "app_model2" WHERE
 "app_model2"."model1_id" = 1
 }}}

 Django 1.8 query
 {{{
 #!python
 In [4]: print Model2.objects.filter(model1=instance_model1).query
 SELECT `app_model2`.`model1_id` FROM `app_model2` WHERE
 `app_model2`.`model1_id` = 1234567890ax
 }}}

--

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

[Django] #26667: Invalid query for OneToOneField if 'to_field' specified and primary_key=True

[Django]

#26667: Invalid query for OneToOneField if 'to_field'  specified and
primary_key=True
-+-
 Reporter:  kwist|  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Database layer   |Version:  1.9
  (models, ORM)  |   Keywords:  OneToOneField to_field
 Severity:  Normal   |  primary_key
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 Given the following models:
 {{{
 #!python
 class Model1(models.Model):
 str_id = models.CharField(max_length=12, unique=True)


 class Model2(models.Model):
 model1 = models.OneToOneField(Model1, to_field='str_id',
 primary_key=True)
 }}}

 In Django 1.9 query:
 {{{
 #!python
 Model2.objects.filter(model1=instance_model1)
 }}}
 always returns an empty list, though in Django 1.8 works

 Django 1.9 query
 {{{
 #!python
 In [4]: print Model2.objects.filter(model1=model1).query
 SELECT "app_model2"."model1_id" FROM "app_model2" WHERE
 "app_model2"."model1_id" = 1
 }}}

 Django 1.8 query
 {{{
 #!python
 In [4]: print Model2.objects.filter(model1=model1).query
 SELECT `app_model2`.`model1_id` FROM `app_model2` WHERE
 `app_model2`.`model1_id` = 1234567890ax
 }}}

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

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