Re: [Django] #28351: "Conflicting migrations detected" CommandError due to replacement Migration being removed

[Django]

#28351: "Conflicting migrations detected" CommandError due to replacement 
Migration
being removed
---+
 Reporter:  Daniel Hahler  |Owner:  Windson yang
 Type:  Bug|   Status:  assigned
Component:  Migrations |  Version:  1.11
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Windson yang):

 * status:  new => assigned
 * owner:  nobody => Windson yang


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

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

[Django]

#27796: Middlewares load twice due to StaticFilesHandler(WSGIHandler)
-+-
 Reporter:  Anthony King |Owner:
 |  Chandrakant Kumar
 Type:  Bug  |   Status:  assigned
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
-+-

Comment (by Patrick Nicholls):

 Are you still working on this Chandrakant Kumar? If not I may give it a
 crack.

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

Re: [Django] #28360: DebugSQLTextTestResult.printErrorList crashes on subTest failure

[Django]

#28360: DebugSQLTextTestResult.printErrorList crashes on subTest failure
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Bug  |   Status:  assigned
Component:  Uncategorized|  Version:  1.11
 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 Sergey Fedoseev):

 * status:  new => assigned
 * owner:  nobody => Sergey Fedoseev


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

[Django] #28360: DebugSQLTextTestResult.printErrorList crashes on subTest failure

[Django]

#28360: DebugSQLTextTestResult.printErrorList crashes on subTest failure
---+
   Reporter:  Sergey Fedoseev  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Uncategorized|Version:  1.11
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 tests/test_subtest.py:

 {{{
 from django.test import TestCase

 class TestSubTest(TestCase):

 def test(self):
 with self.subTest():
 self.assertTrue(False)

 }}}

 {{{
 python  tests/runtests.py  --debug-sql test_subtest
 1 ↵
 Testing against Django installed in '/home/sergey/dev/django/django' with
 up to 4 processes
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 System check identified no issues (0 silenced).

 Traceback (most recent call last):
   File "tests/runtests.py", line 478, in 
 options.exclude_tags,
   File "tests/runtests.py", line 286, in django_tests
 extra_tests=extra_tests,
   File "/home/sergey/dev/django/django/test/runner.py", line 604, in
 run_tests
 result = self.run_suite(suite)
   File "/home/sergey/dev/django/django/test/runner.py", line 570, in
 run_suite
 return runner.run(suite)
   File "/usr/lib/python3.5/unittest/runner.py", line 183, in run
 result.printErrors()
   File "/usr/lib/python3.5/unittest/runner.py", line 110, in printErrors
 self.printErrorList('FAIL', self.failures)
   File "/home/sergey/dev/django/django/test/runner.py", line 60, in
 printErrorList
 for test, err, sql_debug in errors:
 ValueError: not enough values to unpack (expected 3, got 2)
 }}}

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

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

Re: [Django] #10060: Multiple table annotation failure

[Django]

#10060: Multiple table annotation failure
-+-
 Reporter:  svsharma@…   |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Artem.Bernatskyy):

 Just have spent 5 hours debugging this bug.

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

Re: [Django] #28358: LazyObject defines attribute that don't exist on wrapped object

[Django]

#28358: LazyObject defines attribute that don't exist on wrapped object
-+-
 Reporter:  Andrey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sergey Fedoseev):

 * status:  new => assigned
 * owner:  nobody => Sergey Fedoseev


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

Re: [Django] #28359: SecurityMiddleware's SECURE_SSL_HOST only affects unsecure requests

[Django]

#28359: SecurityMiddleware's SECURE_SSL_HOST only affects unsecure requests
-+-
 Reporter:  Matthias Kestenholz  |Owner:  Irindu
 |  Indeera
 Type:  New feature  |   Status:  assigned
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Matthias Kestenholz):

 You could help review the proposed feature itself and also the pull
 request: https://github.com/django/django/pull/8698

 A good idea would also be to follow the ticket triaging steps as
 documented here:
 https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/#unreviewed

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

Re: [Django] #28359: SecurityMiddleware's SECURE_SSL_HOST only affects unsecure requests

[Django]

#28359: SecurityMiddleware's SECURE_SSL_HOST only affects unsecure requests
-+-
 Reporter:  Matthias Kestenholz  |Owner:  Irindu
 |  Indeera
 Type:  New feature  |   Status:  assigned
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Irindu Indeera ):

 * status:  new => assigned
 * owner:  nobody => Irindu Indeera


Comment:

 HI I'd like to work on this issue, but I am a newbie to open source, I am
 currently a computer engineering undergraduate, I am confident that I'll
 be able to contribute but I need some mentoring, Mr Matthias Kestenholz
 can you please help me

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

Re: [Django] #28358: LazyObject defines attribute that don't exist on wrapped object

[Django]

#28358: LazyObject defines attribute that don't exist on wrapped object
-+
 Reporter:  Andrey Fedoseev  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Sergey Fedoseev):

 * cc: Sergey Fedoseev (added)


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

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

Re: [Django] #28359: SecurityMiddleware's SECURE_SSL_HOST only affects unsecure requests

[Django]

#28359: SecurityMiddleware's SECURE_SSL_HOST only affects unsecure requests
-+-
 Reporter:  Matthias Kestenholz  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Matthias Kestenholz):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #28359: SecurityMiddleware's SECURE_SSL_HOST only affects unsecure requests

[Django]

#28359: SecurityMiddleware's SECURE_SSL_HOST only affects unsecure requests
-+-
 Reporter:  Matthias Kestenholz  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by Matthias Kestenholz:

Old description:

> For search engine optimization purposes it is preferable to have a single
> domain serving all requests. We have a custom middleware in most projects
> which handles this but dropped the middleware for sites using SSL:
>

> {{{
> from django.conf import settings
> from django.http import HttpResponsePermanentRedirect
>

> def force_domain(get_response):
> if settings.DEBUG or not settings.FORCE_DOMAIN:
> return get_response
>
> def middleware(request):
> if request.method != 'GET':
> return get_response(request)
>
> if request.get_host() != settings.FORCE_DOMAIN:
> target = 'http%s://%s%s' % (
> request.is_secure() and 's' or '',
> settings.FORCE_DOMAIN,
> request.get_full_path())
> return HttpResponsePermanentRedirect(target)
>
> return get_response(request)
>
> return middleware
> }}}
>
> It seems to me that setting `SECURE_SSL_REDIRECT` and `SECURE_SSL_HOST`
> should also handle the case where 1. a request already uses a secure
> connection but 2. the host does not equal `SECURE_SSL_HOST`.
>
> (Categorized as new feature because that's more fun.)

New description:

 For search engine optimization purposes it is preferable to have a single
 domain serving all requests. We have a custom middleware in most projects
 which handles this but dropped the middleware for sites using SSL:


 {{{
 from django.conf import settings
 from django.http import HttpResponsePermanentRedirect


 def force_domain(get_response):
 if settings.DEBUG or not settings.FORCE_DOMAIN:
 return get_response

 def middleware(request):
 if request.method != 'GET':
 return get_response(request)

 if request.get_host() != settings.FORCE_DOMAIN:
 target = 'http%s://%s%s' % (
 request.is_secure() and 's' or '',
 settings.FORCE_DOMAIN,
 request.get_full_path())
 return HttpResponsePermanentRedirect(target)

 return get_response(request)

 return middleware
 }}}

 We noticed today that setting `SECURE_SSL_HOST = 'example.com'` does not
 redirect requests to `https://www.example.com`

 It seems to me that setting `SECURE_SSL_REDIRECT` and `SECURE_SSL_HOST`
 should also handle the case where 1. a request already uses a secure
 connection but 2. the host does not equal `SECURE_SSL_HOST`.

 (Categorized as new feature because that's more fun.)

--

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

[Django] #28359: SecurityMiddleware's SECURE_SSL_HOST only affects unsecure requests

[Django]

#28359: SecurityMiddleware's SECURE_SSL_HOST only affects unsecure requests
---+
   Reporter:  Matthias Kestenholz  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  HTTP handling|Version:  master
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  1
  UI/UX:  0|
---+
 For search engine optimization purposes it is preferable to have a single
 domain serving all requests. We have a custom middleware in most projects
 which handles this but dropped the middleware for sites using SSL:


 {{{
 from django.conf import settings
 from django.http import HttpResponsePermanentRedirect


 def force_domain(get_response):
 if settings.DEBUG or not settings.FORCE_DOMAIN:
 return get_response

 def middleware(request):
 if request.method != 'GET':
 return get_response(request)

 if request.get_host() != settings.FORCE_DOMAIN:
 target = 'http%s://%s%s' % (
 request.is_secure() and 's' or '',
 settings.FORCE_DOMAIN,
 request.get_full_path())
 return HttpResponsePermanentRedirect(target)

 return get_response(request)

 return middleware
 }}}

 It seems to me that setting `SECURE_SSL_REDIRECT` and `SECURE_SSL_HOST`
 should also handle the case where 1. a request already uses a secure
 connection but 2. the host does not equal `SECURE_SSL_HOST`.

 (Categorized as new feature because that's more fun.)

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