Re: [Django] #25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres

[Django]

#25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres
-+-
 Reporter:  Asif Saifuddin Auvi  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgres, index, | Triage Stage:  Accepted
  BRIN   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mads Jensen):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres

[Django]

#25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres
-+-
 Reporter:  Asif Saifuddin Auvi  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgres, index, | Triage Stage:  Accepted
  BRIN   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mads Jensen):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #27358: Add a system check for FileField upload_to starting with a slash

[Django]

#27358: Add a system check for FileField upload_to starting with a slash
--+
 Reporter:  Tim Graham|Owner:  Frank
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (System checks)  |  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:  1 |UI/UX:  0
--+
Changes (by Frank):

 * status:  new => assigned
 * owner:  nobody => Frank


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

Re: [Django] #27328: return `Set-Cookie` if sessionid= None value

[Django]

#27328: return `Set-Cookie` if sessionid=  None value
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:  Bug  |   Status:  new
Component:  contrib.sessions |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Your last comment describes how cookies work but I don't see a description
 of the problem and how this ticket fixes it. I didn't see that information
 in the video either. Anyway, for everyone else following this ticket, it
 would be a lot more helpful if you could list the steps to reproduce the
 issue here as well as the actual (current) and expected (after the patch)
 results. 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/065.04f43db7f33942fd93bc5e5ea2e9f8c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27328: return `Set-Cookie` if sessionid= None value

[Django]

#27328: return `Set-Cookie` if sessionid=  None value
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:  Bug  |   Status:  closed
Component:  contrib.sessions |  Version:  1.10
 Severity:  Normal   |   Resolution:  invalid
 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 Ramin Farajpour Cami):

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


Comment:

 do you see my video,? you see sessionid alwasy in my case empty,

 I have nothing more to tell you. i will change code django  local machin ,
 now i close PR ,

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

[Django] #27359: Make it possible to specify a default template engine

[Django]

#27359: Make it possible to specify a default template engine
--+--
 Reporter:  Artur Barseghyan  |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Template system   |Version:  1.10
 Severity:  Normal|   Keywords:  template engines
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 This is my first django ticket here. Please, forgive for possible
 mistakes.

 Issue:
 I want to be able to use a custom template engine (same DjangoTemplates,
 but with different settings). Multiple template engines seems to be a
 great feature, but it becomes not that usable with big projects that
 depend on third party packages (such as django-cms, wagtail, etc) - you
 have to tell each view/render to use the default engine, otherwise you get
 "Several DjangoTemplates backends are configured. You must select one
 explicitly." `ImproperlyConfigured` exception.

 Solution:
 It would be really useful if it would be possible to mark one of the
 template engines as default and choose alternative engine where desired.

 Changes to :meth:`django.template.engine.get_default` and engine
 configuration (`TEMPLATES` setting) would be really trivial. I could make
 a patch if approved.

 Thank you (in any 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/058.6e152d554cd66500e5a53c36980ddfe2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27359: Make it possible to specify a default template engine

[Django]

#27359: Make it possible to specify a default template engine
--+--
 Reporter:  Artur Barseghyan  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Template system   |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:  template engines  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Aymeric Augustin):

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


Comment:

 You shouldn't hit this error unless the third party apps rely on
 deprecated or private APIs.

 Can you provide the full stack trace for the exception you're getting?

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

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

Re: [Django] #27141: makemigrations fails with PermissionDenied on django_migrations

[Django]

#27141: makemigrations fails with PermissionDenied on django_migrations
--+
 Reporter:  Sjoerd Job Postmus|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  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 ldng):

 A similar usesase but maybe needing a different solution (or even a
 different ticket) is that of a read only database connection.

 Say you have :
 {{{#!python
 DATABASES = {
 'default': ...,
 'another_db_rw': ...,
 'yet_another_db_r': ...,
 }
 }}}

 //makemigrations//  will try to "make" migrations for all 3 connections.
 Maybe a solution for that would be a '--database' option like //migrate//
 command ?

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

Re: [Django] #27359: Make it possible to specify a default template engine

[Django]

#27359: Make it possible to specify a default template engine
--+--
 Reporter:  Artur Barseghyan  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Template system   |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:  template engines  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Artur Barseghyan):

 @Aymeric Augustin:

 Sure!

 ---

 My settings:

 {{{

 TEMPLATES = [
 # The default engine - a heavy one with a lot of context processors
 {
 'NAME': 'default',
 'BACKEND': 'django.template.backends.django.DjangoTemplates',
 'DIRS': [],
 'APP_DIRS': True,
 'OPTIONS': {
 'context_processors': [
 'django.contrib.auth.context_processors.auth',
 'django.contrib.messages.context_processors.messages',
 'django.template.context_processors.i18n',
 'django.template.context_processors.request',
 'django.template.context_processors.media',
 'django.template.context_processors.static',
 'sekizai.context_processors.sekizai',
 'cms.context_processors.cms_settings',
 ],
 'debug': True,
 }
 },

 # Light engine - only very necessary things go here
 {
 'NAME': 'light',
 'BACKEND': 'django.template.backends.django.DjangoTemplates',
 'DIRS': [],
 'APP_DIRS': True,
 'OPTIONS': {
 'context_processors': [
 'django.contrib.auth.context_processors.auth',
 'django.contrib.messages.context_processors.messages',
 'django.template.context_processors.i18n',
 'django.template.context_processors.request',
 'django.template.context_processors.media',
 'django.template.context_processors.static',
 ],
 'debug': True,
 },
 },
 ]

 }}}

 ---

 {{{

 Environment:


 Request Method: GET
 Request URL: http://localhost:8000/de-at/suchen/

 Django Version: 1.8.7
 Python Version: 2.7.6
 Installed Applications:
 ('djangocms_admin_style',
  'django.contrib.admin',
  'django.contrib.auth',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.messages',
  'django.contrib.redirects',
  'django.contrib.staticfiles',
  'django.contrib.sites',
  'django.contrib.sitemaps',
  'mptt',
  'treebeard',
  'menus',
  'sekizai',
  'easy_select2',
  'easy_thumbnails',
  'metatags',
  'ckeditor',
  'cmsplugin_filer_file',
  'cmsplugin_filer_folder',
  'cmsplugin_filer_link',
  'cmsplugin_filer_image',
  'cmsplugin_filer_teaser',
  'cmsplugin_filer_video',
  'cms',
  'hvad',
  'reversion',
  'compressor',
  'filer',
  'rosetta',
  'debug_toolbar')
 Installed Middleware:
 ('django.middleware.cache.UpdateCacheMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.middleware.csrf.CsrfViewMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.contrib.messages.middleware.MessageMiddleware',
  'django.contrib.redirects.middleware.RedirectFallbackMiddleware',
  'django.middleware.locale.LocaleMiddleware',
  'django.contrib.admindocs.middleware.XViewMiddleware',
  'django.middleware.common.CommonMiddleware',
  'cms.middleware.page.CurrentPageMiddleware',
  'cms.middleware.user.CurrentUserMiddleware',
  'cms.middleware.toolbar.ToolbarMiddleware',
  'cms.middleware.language.LanguageCookieMiddleware',
  'django.middleware.cache.FetchFromCacheMiddleware',
  'debug_toolbar.middleware.DebugToolbarMiddleware')


 Traceback:
 File "/home/me/.virtualenvs/myenv/local/lib/python2.7/site-
 packages/django/core/handlers/base.py" in get_response
   164. response = response.render()
 File "/home/me/.virtualenvs/myenv/local/lib/python2.7/site-
 packages/django/template/response.py" in render
   158. self.content = self.rendered_content
 File "/home/me/.virtualenvs/myenv/local/lib/python2.7/site-
 packages/django/template/response.py" in rendered_content
   135. content = template.render(context, self._request)
 File "/home/me/.virtualenvs/myenv/local/lib/python2.7/site-
 packages/django/template/backends/django.py" in render
   74. return self.template.render(context)
 File "/home/me/.virtualenvs/myenv/local/lib/python2.7/site-
 packages/django/template/base.py" in render
   210. return self._render(context)
 File "/home/me/.virtualenvs/myenv/local/lib/python2.7/site-
 packa

Re: [Django] #27359: Make it possible to specify a default template engine

[Django]

#27359: Make it possible to specify a default template engine
--+--
 Reporter:  Artur Barseghyan  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Template system   |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  template engines  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Artur Barseghyan):

 * version:  1.10 => 1.8


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

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

Re: [Django] #27359: Make it possible to specify a default template engine

[Django]

#27359: Make it possible to specify a default template engine
--+--
 Reporter:  Artur Barseghyan  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Template system   |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  template engines  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Aymeric Augustin):

 Right, this situation is described in this part of the documentation:
 https://docs.djangoproject.com/en/1.10/ref/templates/api/#loading-a-template
 (the first two paragraphs).

 I suppose the transition could be smoothed by adopting a convention for
 determining the default Django templates engine, perhaps by deciding it
 the one called "django" (or similar) when there are multiple engines
 configured.

 Can you start by reporting this issue to `django-cms`? They're doing
 `context.template = Template('')` which, per the current documentation,
 isn't supported.

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

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

Re: [Django] #27359: Make it possible to specify a default template engine

[Django]

#27359: Make it possible to specify a default template engine
--+--
 Reporter:  Artur Barseghyan  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Template system   |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  template engines  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Artur Barseghyan):

 @Aymeric Augustin:

 Thanks! I have already tracked it down and reported an issue.

 - https://github.com/divio/django-cms/issues/5730

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

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

Re: [Django] #27141: makemigrations fails with PermissionDenied on django_migrations

[Django]

#27141: makemigrations fails with PermissionDenied on django_migrations
--+
 Reporter:  Sjoerd Job Postmus|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  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 Tim Graham):

 You should set up database routers so that `allow_migrate()` returns
 `False` for read-only connections.

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

Re: [Django] #27352: Warn about social media fingerprinting when using redirect_authenticated_user

[Django]

#27352: Warn about social media fingerprinting when using
redirect_authenticated_user
-+-
 Reporter:  Markus Holtermann|Owner:  Markus
 Type:   |  Holtermann
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"b5fc192b99ce92a7ccad08cca7b59b1a4e7ca230" b5fc192]:
 {{{
 #!CommitTicketReference repository=""
 revision="b5fc192b99ce92a7ccad08cca7b59b1a4e7ca230"
 Fixed #27352 -- Doc'd social media fingerprinting consideration with
 login's redirect_authenticated_user.
 }}}

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

Re: [Django] #17985: Add documentation for the lookup_allowed method

[Django]

#17985: Add documentation for the lookup_allowed method
---+
 Reporter:  3point2|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Zach):

 * cc: zborboa@… (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/065.ba97b2e6dfc68b94dcf74006c5be7cf0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27352: Warn about social media fingerprinting when using redirect_authenticated_user

[Django]

#27352: Warn about social media fingerprinting when using
redirect_authenticated_user
-+-
 Reporter:  Markus Holtermann|Owner:  Markus
 Type:   |  Holtermann
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"d3ca2907789c348bb132dfd112379df07db0cbbf" d3ca2907]:
 {{{
 #!CommitTicketReference repository=""
 revision="d3ca2907789c348bb132dfd112379df07db0cbbf"
 [1.10.x] Fixed #27352 -- Doc'd social media fingerprinting consideration
 with login's redirect_authenticated_user.

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

[Django] #27360: Make it easier to track down the offending models for AlreadyRegistered exceptions

[Django]

#27360: Make it easier to track down the offending models for AlreadyRegistered
exceptions
---+
 Reporter:  Ed Morley  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  contrib.admin  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I've just updated 20+ packages locally in a project's requirements file,
 one of which has caused:

 {{{
 [2016-10-18 15:00:18,667] ERROR [django.request:256] Internal Server
 Error: /browserid/csrf/
 Traceback (most recent call last):
   File "/home/vagrant/venv/local/lib/python2.7/site-
 packages/django/core/handlers/base.py", line 223, in get_response
 response = middleware_method(request, response)
   File "/home/vagrant/venv/local/lib/python2.7/site-
 packages/debug_toolbar/middleware.py", line 129, in process_response
 panel.generate_stats(request, response)
   File "/home/vagrant/venv/local/lib/python2.7/site-
 packages/debug_toolbar/panels/request.py", line 41, in generate_stats
 match = resolve(request.path)
   File "/home/vagrant/venv/local/lib/python2.7/site-
 packages/django/core/urlresolvers.py", line 521, in resolve
 return get_resolver(urlconf).resolve(path)
   File "/home/vagrant/venv/local/lib/python2.7/site-
 packages/django/core/urlresolvers.py", line 365, in resolve
 for pattern in self.url_patterns:
   File "/home/vagrant/venv/local/lib/python2.7/site-
 packages/django/core/urlresolvers.py", line 401, in url_patterns
 patterns = getattr(self.urlconf_module, "urlpatterns",
 self.urlconf_module)
   File "/home/vagrant/venv/local/lib/python2.7/site-
 packages/django/core/urlresolvers.py", line 395, in urlconf_module
 self._urlconf_module = import_module(self.urlconf_name)
   File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
 import_module
 __import__(name)
   File "/home/vagrant/treeherder/treeherder/config/urls.py", line 12, in
 
 browserid_admin.copy_registry(admin.site)
   File "/home/vagrant/venv/local/lib/python2.7/site-
 packages/django_browserid/admin.py", line 39, in copy_registry
 self.register(model, modeladmin.__class__)
   File "/home/vagrant/venv/local/lib/python2.7/site-
 packages/django/contrib/admin/sites.py", line 90, in register
 raise AlreadyRegistered('The model %s is already registered' %
 model.__name__)
 AlreadyRegistered: The model Site is already registered
 }}}

 This model isn't defined in the project's own models so in this particular
 case it must be django-browserid now clashing with one of the packages
 that was updated.

 Rather than having to bisect, it would be much more helpful if this
 exception gave more details about the already-registered model, so I know
 which package/app is clashing with the later app's attempts to re-register
 it.

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

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

Re: [Django] #12087: Django "TransactionTestCase" isn't

[Django]

#12087: Django "TransactionTestCase" isn't
---+
 Reporter:  brandon|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Testing framework  |  Version:  1.1
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Thomas Hauk):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 The name `TransactionTestCase` was definitely a mistake and it should have
 been changed ages ago. Very confusing to have a class named after
 something which it ''definitely'' doesn't do! Maybe it should be renamed
 `DefinitelyNotInATransactionTestCase` as a breaking change in the next
 major release...

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

Re: [Django] #27360: Make it easier to track down the offending models for AlreadyRegistered exceptions

[Django]

#27360: Make it easier to track down the offending models for AlreadyRegistered
exceptions
--+
 Reporter:  Ed Morley |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * 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.99eff78a60161e5b2be88724285cd79b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27360: Make it easier to track down the offending models for AlreadyRegistered exceptions

[Django]

#27360: Make it easier to track down the offending models for AlreadyRegistered
exceptions
--+
 Reporter:  Ed Morley |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.8
 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 Quentin Fulsher):

 It might be a good idea to add the model's `__module__` field in front of
 the model name. Suppose for example I defined the model `UserModel` in
 `app1.models`. This would turn the resulting exception's message to
 `AlreadyRegistered: The model app1.models.Site is already registered`.
 Does this sound like a good addition?

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

[Django] #27361: Small clean up on forms api documentation

[Django]

#27361: Small clean up on forms api documentation
--+
 Reporter:  Zach Borboa   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
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/053.41268127be14e014a5f082fccecffd35%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27361: Small clean up on forms api documentation

[Django]

#27361: Small clean up on forms api documentation
-+-
 Reporter:  Zach Borboa  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Uncategorized|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Zach Borboa):

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


Old description:



New description:

 PR

--

Comment:

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

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

Re: [Django] #27361: Small clean up on forms api documentation

[Django]

#27361: Small clean up on forms api documentation
-+-
 Reporter:  Zach Borboa  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Uncategorized|  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
-+-
Description changed by Zach Borboa:

Old description:

> PR

New description:



--

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