Re: [Django] #23331: Circular dependencies are not resolved by new Migrate framework

[Django]

#23331: Circular dependencies are not resolved by new Migrate framework
-+
 Reporter:  aidanlister  |Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  migrate  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by andrewgodwin):

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


Comment:

 Tried to reproduce from example project, and it worked perfectly with the
 line:

 {{{
 ./manage.py makemigrations tasks timeline organisations reports
 contractors inspections properties
 }}}

 The generated migrations then also ran successfully.

 Closing as INVALID as I suspect this was encountered just before the fixes
 to #23322 and #23315 landed in master earlier, and in particular #23315
 would have manifested as the first command not being able to run.

 If you can reproduce this on the most recent commit in master, please
 reopen and this time provide full console output from when the command
 runs.

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

Re: [Django] #23331: Circular dependencies are not resolved by new Migrate framework

[Django]

#23331: Circular dependencies are not resolved by new Migrate framework
-+
 Reporter:  aidanlister  |Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  migrate  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by aidanlister):

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


Old description:



New description:

 It's very easy and not explicitly not-supported to create circular
 dependencies in your apps. I have attached a test project which has two
 circular dependency resolution failures.

 This fails to create migrations:

 ./manage.py makemigrations contractors inspections organisations
 properties reports tasks timeline

 This creates the migrations:

 ./manage.py makemigrations properties reports tasks timeline
 ./manage.py makemigrations contractors inspections

 But then ./manage.py migrate fails:

 django.db.migrations.graph.CircularDependencyError: [('contractors',
 u'0002_auto_20140821_0156'), ('reports', u'0001_initial'), ('inspections',
 u'0001_initial'), ('contractors', u'0002_auto_20140821_0156')]


 I have tried manually breaking up the migrations into lots of little
 steps, but you'll have the same problem with the reports and inspections
 app. Even with lots of tiny migrations it eventually loops around.

--

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

[Django] #23331: Circular dependencies are not resolved by new Migrate framework

[Django]

#23331: Circular dependencies are not resolved by new Migrate framework
-+--
 Reporter:  aidanlister  |  Owner:  andrewgodwin
 Type:  Bug  | Status:  new
Component:  Migrations   |Version:  master
 Severity:  Normal   |   Keywords:  migrate
 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/054.61d98d8fb0dcd280cd252a577358f208%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23330: RedirectResponse option to check the host of the url

[Django]

#23330: RedirectResponse option to check the host of the url
---+
 Reporter:  doctormo   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  HTTP handling  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 https://github.com/django/django/pull/3094

 Proposed addition.

 When redirecting it's often useful to redirect to the 'next' url which is
 passed from the browser. This variable might be altered before it gets
 back to us and so we want to check that the host is a known local host and
 approved. Because we don't want this to be checked all the time, it's
 optional in the proposed code.

 The patch/pull request uses the existing urlparser data to perform the
 checks and the placement of the functionality seems like it would make a
 good django contribution.

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

Re: [Django] #23329: Regression in security patch for querystring manipulation in admin

[Django]

#23329: Regression in security patch for querystring manipulation in admin
---+--
 Reporter:  Markush2010|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.5
 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):

 Shouldn't `TO_FIELD_VAR` be `'title_ptr_id'` in this case? Which should be
 the default `to_field` if you have `ForeignKey` pointing to
 `Recommendation`.

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

Re: [Django] #23329: Regression in security patch for querystring manipulation in admin

[Django]

#23329: Regression in security patch for querystring manipulation in admin
---+--
 Reporter:  Markush2010|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.5
 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 charettes):

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

Re: [Django] #22948: Django 1.6, Python3.4, apache2.4, mod_wsgi not working

[Django]

#22948: Django 1.6, Python3.4, apache2.4, mod_wsgi not working
-+-
 Reporter:  tom@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Python 3 |  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  python3, apache2,| Triage Stage:
  mod_wsgi   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GrahamDumpleton):

 For Python 3.4 you need to have an update to date mod_wsgi version. Use
 mod_wsgi 4.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/074.83cf79eeaf1dfc5895f87177fdddb27e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23329: Regression in security patch for querystring manipulation in admin

[Django]

#23329: Regression in security patch for querystring manipulation in admin
---+--
 Reporter:  Markush2010|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.5
 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 Markush2010):

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


Old description:

> At least on 1.5.9 the following modified Test failed:
>
> Explanation: the model "Recommendation" inherits from "Title".
> "Recommendation" has a ModelAdmin registerd, "Title" does not. Due to the
> restrictiveness of the new ``to_field_allowed`` function, one cannot open
> the popup for "Recommendation" anymore.
>
> {{{#!diff
> diff --git a/tests/regressiontests/admin_views/tests.py
> b/tests/regressiontests/admin_views/tests.py
> index e7efca2..08f90d8 100644
> --- a/tests/regressiontests/admin_views/tests.py
> +++ b/tests/regressiontests/admin_views/tests.py
> @@ -567,6 +567,11 @@ class AdminViewBasicTest(TestCase):
>  with self.assertRaises(DisallowedModelAdminToField):
>  response =
> self.client.get("/test_admin/admin/admin_views/section/", {TO_FIELD_VAR:
> 'name'})
>
> +# Specifying a field that is not refered by any other model
> directly registered
> +# to this admin site but registered through inheritance
> +response =
> self.client.get("/test_admin/admin/admin_views/recommendation/",
> {TO_FIELD_VAR: 'id'})
> +self.assertEqual(response.status_code, 200)
> +
>  # Specifying a field referenced by another model should be
> allowed.
>  response =
> self.client.get("/test_admin/admin/admin_views/section/", {TO_FIELD_VAR:
> 'id'})
>  self.assertEqual(response.status_code, 200)
> }}}

New description:

 At least on 1.5.9 the following modified Test failed:

 Explanation: the model "Recommendation" inherits from "Title".
 "Recommendation" has a ModelAdmin registerd, "Title" does not. Due to the
 restrictiveness of the new `to_field_allowed` function, one cannot open
 the popup for "Recommendation" anymore.

 {{{#!diff
 diff --git a/tests/regressiontests/admin_views/tests.py
 b/tests/regressiontests/admin_views/tests.py
 index e7efca2..08f90d8 100644
 --- a/tests/regressiontests/admin_views/tests.py
 +++ b/tests/regressiontests/admin_views/tests.py
 @@ -567,6 +567,11 @@ class AdminViewBasicTest(TestCase):
  with self.assertRaises(DisallowedModelAdminToField):
  response =
 self.client.get("/test_admin/admin/admin_views/section/", {TO_FIELD_VAR:
 'name'})

 +# Specifying a field that is not refered by any other model
 directly registered
 +# to this admin site but registered through inheritance
 +response =
 self.client.get("/test_admin/admin/admin_views/recommendation/",
 {TO_FIELD_VAR: 'id'})
 +self.assertEqual(response.status_code, 200)
 +
  # Specifying a field referenced by another model should be
 allowed.
  response =
 self.client.get("/test_admin/admin/admin_views/section/", {TO_FIELD_VAR:
 'id'})
  self.assertEqual(response.status_code, 200)
 }}}

--

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

[Django] #23329: Regression in security patch for querystring manipulation in admin

[Django]

#23329: Regression in security patch for querystring manipulation in admin
---+
 Reporter:  Markush2010|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 At least on 1.5.9 the following modified Test failed:

 Explanation: the model "Recommendation" inherits from "Title".
 "Recommendation" has a ModelAdmin registerd, "Title" does not. Due to the
 restrictiveness of the new ``to_field_allowed`` function, one cannot open
 the popup for "Recommendation" anymore.

 {{{#!diff
 diff --git a/tests/regressiontests/admin_views/tests.py
 b/tests/regressiontests/admin_views/tests.py
 index e7efca2..08f90d8 100644
 --- a/tests/regressiontests/admin_views/tests.py
 +++ b/tests/regressiontests/admin_views/tests.py
 @@ -567,6 +567,11 @@ class AdminViewBasicTest(TestCase):
  with self.assertRaises(DisallowedModelAdminToField):
  response =
 self.client.get("/test_admin/admin/admin_views/section/", {TO_FIELD_VAR:
 'name'})

 +# Specifying a field that is not refered by any other model
 directly registered
 +# to this admin site but registered through inheritance
 +response =
 self.client.get("/test_admin/admin/admin_views/recommendation/",
 {TO_FIELD_VAR: 'id'})
 +self.assertEqual(response.status_code, 200)
 +
  # Specifying a field referenced by another model should be
 allowed.
  response =
 self.client.get("/test_admin/admin/admin_views/section/", {TO_FIELD_VAR:
 'id'})
  self.assertEqual(response.status_code, 200)
 }}}

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

[Django] #23328: get_javascript_catalog bug

[Django]

#23328: get_javascript_catalog bug
--+--
 Reporter:  liminspace|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Internationalization  |Version:  1.7-rc-2
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 There is a project with two languages: "en" and "uk" (ukrainian).
 Default language is "uk".

 There are pharases:
 locale/
 en/
 djangojs.po
 msgid "Всім привіт!"
 msgstr "Hello everyone!"
 uk/
 djangojs.po
 msgid "Всім привіт!"
 msgstr ""

 In this case, the activated language "uk" phrase "Всім привіт!" will be in
 "en" -- "Hello everyone!".
 It's a bug, because must be "uk".

 I propose remove loading "en" translation as default (is better).
 Or change update method for other default language:
 {{{
 if default_locale != 'en':
 for path in paths:
 try:
 catalog = gettext_module.translation(domain, path,
 [default_locale])
 except IOError:
 catalog = None
 if catalog is not None:
 # t.update(catalog._catalog)  # remove it
 t = catalog._catalog  # <- add 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/053.c3a94c4911d23f7e7d8630c460245bc3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23326: DatabaseCache must implement incr to guarantee atomic increment

[Django]

#23326: DatabaseCache must implement incr to guarantee atomic increment
-+
 Reporter:  vinayan3 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.6
 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 freakboy3742):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 You are correct that the implementation of incr on the DB cache backend
 will be subject to race conditions, so we should fix that.

 However, I'd also say that if you're using the database cache backend for
 a count where there is heavy traffic, You're Doing It Wrong(TM). You
 should be using Redis, or at least Memcached.

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

Re: [Django] #8851: Please add a default option to list_filter in the admin interface

[Django]

#8851: Please add a default option to list_filter in the admin interface
-+-
 Reporter:  Riskable |Owner:  nobody
 |   Status:  new
 Type:  New feature  |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  admin, list_filter,  |  Needs documentation:  0
  default|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by trbs):

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

[Django] #23327: Add "migrate zero" syntax to migrate help message

[Django]

#23327: Add "migrate  zero" syntax to migrate help message
---+--
 Reporter:  nikolas|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.7-rc-2
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+--
 There's an essential piece of info in the documentation for `./manage.py
 migrate` here:

   https://docs.djangoproject.com/en/1.7/ref/django-admin/#django-admin-
 migrate

 which explains how to roll back a migration to before the initial
 migration. This is the `./manage.py migrate  zero` syntax.

 I think this should be explained in the help message when you run
 `./manage.py migrate --help`, as well.

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

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

[django/django] 808c0d: [1.6.x] Bumped version number post-release.

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 808c0dc705cd4b5be9903d20163e08bb080a42c2
  
https://github.com/django/django/commit/808c0dc705cd4b5be9903d20163e08bb080a42c2
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  [1.6.x] Bumped version number post-release.


-- 
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/53f5076974e62_2b63f930ccab2bc10314a%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 4fa3c0: [1.5.x] Bumped version number post-release.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 4fa3c041054865cf0b7004200cf9bcc325ff1369
  
https://github.com/django/django/commit/4fa3c041054865cf0b7004200cf9bcc325ff1369
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  [1.5.x] Bumped version number post-release.


-- 
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/53f5076a52902_3b5b3ffb1f8552a0656d3%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 27c682: [1.4.x] Bumped version number post-release.

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 27c682ffa08264dee63c82751ebfa9d8eeaf62df
  
https://github.com/django/django/commit/27c682ffa08264dee63c82751ebfa9d8eeaf62df
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  [1.4.x] Bumped version number post-release.


-- 
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/53f506eecb209_1f433f9ddd7d72a07275d%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] e484df: [1.4.x] Added dates to release notes.

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: e484df76b68ea8b23e5d6d07d61d408c8d756931
  
https://github.com/django/django/commit/e484df76b68ea8b23e5d6d07d61d408c8d756931
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M docs/releases/1.4.14.txt

  Log Message:
  ---
  [1.4.x] Added dates to release notes.


-- 
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/53f50639e7cd9_f683fe9baa1929c10332f%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] ed4cf3: [1.5.x] Added dates to release notes.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: ed4cf3b450f1d6e3b0aa4af6692348c0323fc7a3
  
https://github.com/django/django/commit/ed4cf3b450f1d6e3b0aa4af6692348c0323fc7a3
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt

  Log Message:
  ---
  [1.5.x] Added dates to release notes.


-- 
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/53f5063895e95_7ff43f98efd3729c516c7%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] f8aa2a: [1.7.x] Added dates to release notes.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: f8aa2aa48679e12e05e8d8f01710e81a6df6022c
  
https://github.com/django/django/commit/f8aa2aa48679e12e05e8d8f01710e81a6df6022c
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt

  Log Message:
  ---
  [1.7.x] Added dates to release notes.

Backport of b902be798e from master


-- 
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/53f505fc2df72_206b3f8ad1b4d2a081561%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 66638a: [1.6.x] Added dates to release notes.

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 66638a09c582a3b9de23c04ccaa326e6ba6575b7
  
https://github.com/django/django/commit/66638a09c582a3b9de23c04ccaa326e6ba6575b7
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt

  Log Message:
  ---
  [1.6.x] Added dates to release notes.

Backport of b902be798e from master


-- 
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/53f505fd15bdf_78a23f909be4729c739c%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] b902be: Added dates to release notes.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b902be798e4a2b760fa6bc86dac5af1c127e5e58
  
https://github.com/django/django/commit/b902be798e4a2b760fa6bc86dac5af1c127e5e58
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt

  Log Message:
  ---
  Added dates to release notes.


-- 
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/53f505c55819e_103b3fae8ce492b84538a%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] ad9625: [1.7.x] Bump version number for security release.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: ad96254af98f961d6691481c27127613afeee840
  
https://github.com/django/django/commit/ad96254af98f961d6691481c27127613afeee840
  Author: James Bennett 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  [1.7.x] Bump version number for security release.


-- 
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/53f5044b7ce49_5a03f9acac172b8555e9%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 8b19a4: [1.6.x] Update version number for security release...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 8b19a4e275313cf2226f535d3ec10f414e0c6885
  
https://github.com/django/django/commit/8b19a4e275313cf2226f535d3ec10f414e0c6885
  Author: James Bennett 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  [1.6.x] Update version number for security release.


-- 
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/53f501c84b9d1_3ba73ff04c0252c090030%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 1f5ff0: [1.5.x] Bump version numbers for security release.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 1f5ff0b1eb2f123523dd659916b6f0a4c0068249
  
https://github.com/django/django/commit/1f5ff0b1eb2f123523dd659916b6f0a4c0068249
  Author: James Bennett 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/__init__.py
M docs/conf.py
M setup.py

  Log Message:
  ---
  [1.5.x] Bump version numbers for security release.


-- 
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/53f500a4a0ca9_33e33f9b9dd752bc10059f%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23322: CircularDependencyError in migrations

[Django]

#23322: CircularDependencyError in migrations
-+-
 Reporter:  gabejackson  |Owner:
 Type:  Bug  |  Markush2010
Component:  Migrations   |   Status:  closed
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:  migrations,  |   Resolution:  fixed
  circular dependency| Triage Stage:  Accepted
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:"2da20379c0dd0171eb11c188909096f708dd6095"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2da20379c0dd0171eb11c188909096f708dd6095"
 [1.7.x] Fixed #23322 -- Use resolved swappable model for dependency
 resolution during makemigrations

 Backport of 144cff3f51 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/069.c5a153cff5b4d32e0dee163ad0ef891d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23322: CircularDependencyError in migrations

[Django]

#23322: CircularDependencyError in migrations
-+-
 Reporter:  gabejackson  |Owner:
 Type:  Bug  |  Markush2010
Component:  Migrations   |   Status:  closed
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:  migrations,  |   Resolution:  fixed
  circular dependency| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"144cff3f516f7c718cbe4bd3165e18781c09042a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="144cff3f516f7c718cbe4bd3165e18781c09042a"
 Fixed #23322 -- Use resolved swappable model for dependency resolution
 during makemigrations
 }}}

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

[django/django] 2da203: [1.7.x] Fixed #23322 -- Use resolved swappable mod...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 2da20379c0dd0171eb11c188909096f708dd6095
  
https://github.com/django/django/commit/2da20379c0dd0171eb11c188909096f708dd6095
  Author: Markus Holtermann 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M tests/migrations/test_autodetector.py

  Log Message:
  ---
  [1.7.x] Fixed #23322 -- Use resolved swappable model for dependency 
resolution during makemigrations

Backport of 144cff3f51 from master


-- 
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/53f5005a34ffb_31c93fc7f221529c847f8%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 144cff: Fixed #23322 -- Use resolved swappable model for d...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 144cff3f516f7c718cbe4bd3165e18781c09042a
  
https://github.com/django/django/commit/144cff3f516f7c718cbe4bd3165e18781c09042a
  Author: Markus Holtermann 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/db/migrations/autodetector.py
M tests/migrations/test_autodetector.py

  Log Message:
  ---
  Fixed #23322 -- Use resolved swappable model for dependency resolution during 
makemigrations


-- 
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/53f5004675b8f_de23f8f616692b85098d%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 4fce01: [1.4.x] Bump version numbers for security release.

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 4fce0193d21b893f0ba186b10cfcdd6350fa5865
  
https://github.com/django/django/commit/4fce0193d21b893f0ba186b10cfcdd6350fa5865
  Author: James Bennett 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/__init__.py
M docs/conf.py
M setup.py

  Log Message:
  ---
  [1.4.x] Bump version numbers for security release.


-- 
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/53f4fe73441b9_79f13fb371e372b87043c%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23157: O(n) behaviour in default configuration when uploading many duplicate filenames

[Django]

#23157: O(n) behaviour in default configuration when uploading many duplicate
filenames
-+-
 Reporter:  dw   |Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  File |   Resolution:  fixed
  uploads/storage| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"3123f8452cf49071be9110e277eea60ba0032216"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3123f8452cf49071be9110e277eea60ba0032216"
 [1.7.x] Fixed #23157 -- Removed O(n) algorithm when uploading duplicate
 file names.

 This is a security fix. Disclosure following shortly.
 }}}

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

Re: [Django] #23066: Already logged-in user remains logged in when RemoteUser authentication of new user fails

[Django]

#23066: Already logged-in user remains logged in when RemoteUser authentication 
of
new user fails
-+-
 Reporter:  david.greisen@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  remoteUserBackend| Triage Stage:  Accepted
  RemoteUserMiddleware   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"1a45d059c70385fcd6f4a3955f3b4e4cc96d0150"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1a45d059c70385fcd6f4a3955f3b4e4cc96d0150"
 [1.7.x] Fixed #23066 -- Modified RemoteUserMiddleware to logout on
 REMOTE_USER change.

 This is a security fix. Disclosure following shortly.
 }}}

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

Re: [Django] #23157: O(n) behaviour in default configuration when uploading many duplicate filenames

[Django]

#23157: O(n) behaviour in default configuration when uploading many duplicate
filenames
-+-
 Reporter:  dw   |Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  File |   Resolution:  fixed
  uploads/storage| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"30042d475bf084c6723c6217a21598d9247a9c41"]:
 {{{
 #!CommitTicketReference repository=""
 revision="30042d475bf084c6723c6217a21598d9247a9c41"
 [1.4.x] Fixed #23157 -- Removed O(n) algorithm when uploading duplicate
 file names.

 This is a security fix. Disclosure following shortly.
 }}}

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

Re: [Django] #23066: Already logged-in user remains logged in when RemoteUser authentication of new user fails

[Django]

#23066: Already logged-in user remains logged in when RemoteUser authentication 
of
new user fails
-+-
 Reporter:  david.greisen@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  remoteUserBackend| Triage Stage:  Accepted
  RemoteUserMiddleware   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"dd68f319b365f6cb38c5a6c106faf4f6142d7d88"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dd68f319b365f6cb38c5a6c106faf4f6142d7d88"
 [1.5.x] Fixed #23066 -- Modified RemoteUserMiddleware to logout on
 REMOTE_USE change.

 This is a security fix. Disclosure following shortly.
 }}}

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

Re: [Django] #23157: O(n) behaviour in default configuration when uploading many duplicate filenames

[Django]

#23157: O(n) behaviour in default configuration when uploading many duplicate
filenames
-+-
 Reporter:  dw   |Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  File |   Resolution:  fixed
  uploads/storage| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"0d8d30b7ddfe83ab03120f4560c7aa153f4d0ed1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0d8d30b7ddfe83ab03120f4560c7aa153f4d0ed1"
 Fixed #23157 -- Removed O(n) algorithm when uploading duplicate file
 names.

 This is a security fix. Disclosure following shortly.
 }}}

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

Re: [Django] #23157: O(n) behaviour in default configuration when uploading many duplicate filenames

[Django]

#23157: O(n) behaviour in default configuration when uploading many duplicate
filenames
-+-
 Reporter:  dw   |Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  File |   Resolution:  fixed
  uploads/storage| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"26cd48e166ac4d84317c8ee6d63ac52a87e8da99"]:
 {{{
 #!CommitTicketReference repository=""
 revision="26cd48e166ac4d84317c8ee6d63ac52a87e8da99"
 [1.5.x] Fixed #23157 -- Removed O(n) algorithm when uploading duplicate
 file names.

 This is a security fix. Disclosure following shortly.
 }}}

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

Re: [Django] #23066: Already logged-in user remains logged in when RemoteUser authentication of new user fails

[Django]

#23066: Already logged-in user remains logged in when RemoteUser authentication 
of
new user fails
-+-
 Reporter:  david.greisen@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  remoteUserBackend| Triage Stage:  Accepted
  RemoteUserMiddleware   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"c9e3b9949cd55f090591fbdc4a114fcb8368b6d9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c9e3b9949cd55f090591fbdc4a114fcb8368b6d9"
 [1.4.x] Fixed #23066 -- Modified RemoteUserMiddleware to logout on
 REMOTE_USE change.

 This is a security fix. Disclosure following shortly.
 }}}

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

[django/django] 4d5e97: [1.4.x] Added release note stub for 1.4.14.

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 4d5e972a2c9f3e2f6ce115f7fbe44df8dd8612ef
  
https://github.com/django/django/commit/4d5e972a2c9f3e2f6ce115f7fbe44df8dd8612ef
  Author: Tim Graham 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
A docs/releases/1.4.14.txt
M docs/releases/index.txt

  Log Message:
  ---
  [1.4.x] Added release note stub for 1.4.14.


  Commit: c2fe73133b62a1d9e8f7a6b43966570b14618d7e
  
https://github.com/django/django/commit/c2fe73133b62a1d9e8f7a6b43966570b14618d7e
  Author: Florian Apolloner 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M django/core/urlresolvers.py
M docs/releases/1.4.14.txt
M tests/regressiontests/urlpatterns_reverse/tests.py
M tests/regressiontests/urlpatterns_reverse/urls.py

  Log Message:
  ---
  [1.4.x] Prevented reverse() from generating URLs pointing to other hosts.

This is a security fix. Disclosure following shortly.


  Commit: 30042d475bf084c6723c6217a21598d9247a9c41
  
https://github.com/django/django/commit/30042d475bf084c6723c6217a21598d9247a9c41
  Author: Tim Graham 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M django/core/files/storage.py
M docs/howto/custom-file-storage.txt
M docs/ref/files/storage.txt
M docs/releases/1.4.14.txt
M tests/modeltests/files/tests.py
M tests/regressiontests/file_storage/tests.py

  Log Message:
  ---
  [1.4.x] Fixed #23157 -- Removed O(n) algorithm when uploading duplicate file 
names.

This is a security fix. Disclosure following shortly.


  Commit: c9e3b9949cd55f090591fbdc4a114fcb8368b6d9
  
https://github.com/django/django/commit/c9e3b9949cd55f090591fbdc4a114fcb8368b6d9
  Author: Preston Holmes 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M django/contrib/auth/middleware.py
M django/contrib/auth/tests/remote_user.py
M docs/releases/1.4.14.txt

  Log Message:
  ---
  [1.4.x] Fixed #23066 -- Modified RemoteUserMiddleware to logout on REMOTE_USE 
change.

This is a security fix. Disclosure following shortly.


  Commit: 027bd348642007617518379f8b02546abacaa6e0
  
https://github.com/django/django/commit/027bd348642007617518379f8b02546abacaa6e0
  Author: Simon Charette 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
A django/contrib/admin/exceptions.py
M django/contrib/admin/options.py
M django/contrib/admin/views/main.py
M docs/releases/1.4.14.txt
M tests/regressiontests/admin_views/tests.py

  Log Message:
  ---
  [1.4.x] Prevented data leakage in contrib.admin via query string manipulation.

This is a security fix. Disclosure following shortly.


Compare: https://github.com/django/django/compare/88cb7aa6aa22...027bd3486420

-- 
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/53f4fcffe8222_7cfa3fee5462929c73472%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23157: O(n) behaviour in default configuration when uploading many duplicate filenames

[Django]

#23157: O(n) behaviour in default configuration when uploading many duplicate
filenames
-+-
 Reporter:  dw   |Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  File |   Resolution:  fixed
  uploads/storage| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"dd0c3f4ee1a30c1a1e6055061c6ba6e58c6b54d1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dd0c3f4ee1a30c1a1e6055061c6ba6e58c6b54d1"
 [1.6.x] Fixed #23157 -- Removed O(n) algorithm when uploading duplicate
 file names.

 This is a security fix. Disclosure following shortly.
 }}}

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

[django/django] 1c00c3: [1.7.x] Added release note stubs for 1.5.9 and 1.4...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 1c00c38b4a81abb54bb8b93d3aa4ce6e661df3dc
  
https://github.com/django/django/commit/1c00c38b4a81abb54bb8b93d3aa4ce6e661df3dc
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
A docs/releases/1.4.14.txt
A docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt
M docs/releases/index.txt

  Log Message:
  ---
  [1.7.x] Added release note stubs for 1.5.9 and 1.4.14.


  Commit: bf650a2ee78c6d1f4544a875dcc777cf27fe93e9
  
https://github.com/django/django/commit/bf650a2ee78c6d1f4544a875dcc777cf27fe93e9
  Author: Florian Apolloner 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/core/urlresolvers.py
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt
M tests/urlpatterns_reverse/tests.py
M tests/urlpatterns_reverse/urls.py

  Log Message:
  ---
  [1.7.x] Prevented reverse() from generating URLs pointing to other hosts.

This is a security fix. Disclosure following shortly.


  Commit: 3123f8452cf49071be9110e277eea60ba0032216
  
https://github.com/django/django/commit/3123f8452cf49071be9110e277eea60ba0032216
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/core/files/storage.py
M docs/howto/custom-file-storage.txt
M docs/ref/files/storage.txt
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt
M docs/releases/1.7.txt
M tests/file_storage/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #23157 -- Removed O(n) algorithm when uploading duplicate file 
names.

This is a security fix. Disclosure following shortly.


  Commit: 1a45d059c70385fcd6f4a3955f3b4e4cc96d0150
  
https://github.com/django/django/commit/1a45d059c70385fcd6f4a3955f3b4e4cc96d0150
  Author: Preston Holmes 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/contrib/auth/middleware.py
M django/contrib/auth/tests/test_remote_user.py
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt

  Log Message:
  ---
  [1.7.x] Fixed #23066 -- Modified RemoteUserMiddleware to logout on 
REMOTE_USER change.

This is a security fix. Disclosure following shortly.


  Commit: 2b31342cdf14fc20e07c43d258f1e7334ad664a6
  
https://github.com/django/django/commit/2b31342cdf14fc20e07c43d258f1e7334ad664a6
  Author: Simon Charette 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/contrib/admin/exceptions.py
M django/contrib/admin/options.py
M django/contrib/admin/views/main.py
M docs/ref/exceptions.txt
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt
M tests/admin_views/tests.py

  Log Message:
  ---
  [1.7.x] Prevented data leakage in contrib.admin via query string manipulation.

This is a security fix. Disclosure following shortly.


Compare: https://github.com/django/django/compare/298148528059...2b31342cdf14

-- 
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/53f4fcfc527e0_2673f821e88b2bc36115%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 25d9ae: [1.5.x] Added release note stubs for 1.5.9 and 1.4...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 25d9ae5214b59f06f385190733914eaa459751ff
  
https://github.com/django/django/commit/25d9ae5214b59f06f385190733914eaa459751ff
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
A docs/releases/1.4.14.txt
A docs/releases/1.5.9.txt
M docs/releases/index.txt

  Log Message:
  ---
  [1.5.x] Added release note stubs for 1.5.9 and 1.4.14.


  Commit: 45ac9d4fb087d21902469fc22643f5201d41a0cd
  
https://github.com/django/django/commit/45ac9d4fb087d21902469fc22643f5201d41a0cd
  Author: Florian Apolloner 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/core/urlresolvers.py
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M tests/regressiontests/urlpatterns_reverse/tests.py
M tests/regressiontests/urlpatterns_reverse/urls.py

  Log Message:
  ---
  [1.5.x] Prevented reverse() from generating URLs pointing to other hosts.

This is a security fix. Disclosure following shortly.


  Commit: 26cd48e166ac4d84317c8ee6d63ac52a87e8da99
  
https://github.com/django/django/commit/26cd48e166ac4d84317c8ee6d63ac52a87e8da99
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/core/files/storage.py
M docs/howto/custom-file-storage.txt
M docs/ref/files/storage.txt
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M tests/modeltests/files/tests.py
M tests/regressiontests/file_storage/tests.py

  Log Message:
  ---
  [1.5.x] Fixed #23157 -- Removed O(n) algorithm when uploading duplicate file 
names.

This is a security fix. Disclosure following shortly.


  Commit: dd68f319b365f6cb38c5a6c106faf4f6142d7d88
  
https://github.com/django/django/commit/dd68f319b365f6cb38c5a6c106faf4f6142d7d88
  Author: Preston Holmes 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/contrib/auth/middleware.py
M django/contrib/auth/tests/remote_user.py
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt

  Log Message:
  ---
  [1.5.x] Fixed #23066 -- Modified RemoteUserMiddleware to logout on REMOTE_USE 
change.

This is a security fix. Disclosure following shortly.


  Commit: 2a446c896e7c814661fb9c4f212b071b2a7fa446
  
https://github.com/django/django/commit/2a446c896e7c814661fb9c4f212b071b2a7fa446
  Author: Simon Charette 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
A django/contrib/admin/exceptions.py
M django/contrib/admin/options.py
M django/contrib/admin/views/main.py
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M tests/regressiontests/admin_views/tests.py

  Log Message:
  ---
  [1.5.x] Prevented data leakage in contrib.admin via query string manipulation.

This is a security fix. Disclosure following shortly.


Compare: https://github.com/django/django/compare/27ab82f7fc72...2a446c896e7c

-- 
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/53f4fcfd94c87_8a03fec705bf29c1010af%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23066: Already logged-in user remains logged in when RemoteUser authentication of new user fails

[Django]

#23066: Already logged-in user remains logged in when RemoteUser authentication 
of
new user fails
-+-
 Reporter:  david.greisen@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  remoteUserBackend| Triage Stage:  Accepted
  RemoteUserMiddleware   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"5307ce565fbedb9cc27cbe7c757b41a00438d37c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5307ce565fbedb9cc27cbe7c757b41a00438d37c"
 Fixed #23066 -- Modified RemoteUserMiddleware to logout on REMOTE_USER
 change.

 This is a security fix. Disclosure following shortly.
 }}}

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

Re: [Django] #23066: Already logged-in user remains logged in when RemoteUser authentication of new user fails

[Django]

#23066: Already logged-in user remains logged in when RemoteUser authentication 
of
new user fails
-+-
 Reporter:  david.greisen@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  remoteUserBackend| Triage Stage:  Accepted
  RemoteUserMiddleware   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"0268b855f9eab3377f2821164ef3e66037789e09"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0268b855f9eab3377f2821164ef3e66037789e09"
 [1.6.x] Fixed #23066 -- Modified RemoteUserMiddleware to logout on
 REMOTE_USE change.

 This is a security fix. Disclosure following shortly.
 }}}

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

[django/django] ec7119: Added release note stubs for 1.5.9 and 1.4.14.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ec71191be0947e22630141e726f0e1f298f930df
  
https://github.com/django/django/commit/ec71191be0947e22630141e726f0e1f298f930df
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
A docs/releases/1.4.14.txt
A docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt
M docs/releases/index.txt

  Log Message:
  ---
  Added release note stubs for 1.5.9 and 1.4.14.


  Commit: 28e765810df46a3f28ff4785491e9973593382fd
  
https://github.com/django/django/commit/28e765810df46a3f28ff4785491e9973593382fd
  Author: Florian Apolloner 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/core/urlresolvers.py
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt
M tests/urlpatterns_reverse/tests.py
M tests/urlpatterns_reverse/urls.py

  Log Message:
  ---
  Prevented reverse() from generating URLs pointing to other hosts.

This is a security fix. Disclosure following shortly.


  Commit: 0d8d30b7ddfe83ab03120f4560c7aa153f4d0ed1
  
https://github.com/django/django/commit/0d8d30b7ddfe83ab03120f4560c7aa153f4d0ed1
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/core/files/storage.py
M docs/howto/custom-file-storage.txt
M docs/ref/files/storage.txt
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt
M docs/releases/1.7.txt
M tests/file_storage/tests.py

  Log Message:
  ---
  Fixed #23157 -- Removed O(n) algorithm when uploading duplicate file names.

This is a security fix. Disclosure following shortly.


  Commit: 5307ce565fbedb9cc27cbe7c757b41a00438d37c
  
https://github.com/django/django/commit/5307ce565fbedb9cc27cbe7c757b41a00438d37c
  Author: Preston Holmes 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/contrib/auth/middleware.py
M django/contrib/auth/tests/test_remote_user.py
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt

  Log Message:
  ---
  Fixed #23066 -- Modified RemoteUserMiddleware to logout on REMOTE_USER change.

This is a security fix. Disclosure following shortly.


  Commit: 53ff0969822ac2248a89ccb6fef1088212dc800d
  
https://github.com/django/django/commit/53ff0969822ac2248a89ccb6fef1088212dc800d
  Author: Simon Charette 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/contrib/admin/exceptions.py
M django/contrib/admin/options.py
M django/contrib/admin/views/main.py
M docs/ref/exceptions.txt
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt
M tests/admin_views/tests.py

  Log Message:
  ---
  Prevented data leakage in contrib.admin via query string manipulation.

This is a security fix. Disclosure following shortly.


Compare: https://github.com/django/django/compare/6f59d2915854...53ff0969822a

-- 
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/53f4fce6c8fe8_d013fc801bbb29c90038%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 52b878: [1.6.x] Added release note stubs for 1.5.9 and 1.4...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 52b878d805c2dc810ddc1ea5493bb7b86455eacc
  
https://github.com/django/django/commit/52b878d805c2dc810ddc1ea5493bb7b86455eacc
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
A docs/releases/1.4.14.txt
A docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt
M docs/releases/index.txt

  Log Message:
  ---
  [1.6.x] Added release note stubs for 1.5.9 and 1.4.14.


  Commit: da051da8df5e69944745072611351d4cfc6435d5
  
https://github.com/django/django/commit/da051da8df5e69944745072611351d4cfc6435d5
  Author: Florian Apolloner 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/core/urlresolvers.py
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt
M tests/urlpatterns_reverse/tests.py
M tests/urlpatterns_reverse/urls.py

  Log Message:
  ---
  [1.6.x] Prevented reverse() from generating URLs pointing to other hosts.

This is a security fix. Disclosure following shortly.


  Commit: dd0c3f4ee1a30c1a1e6055061c6ba6e58c6b54d1
  
https://github.com/django/django/commit/dd0c3f4ee1a30c1a1e6055061c6ba6e58c6b54d1
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/core/files/storage.py
M docs/howto/custom-file-storage.txt
M docs/ref/files/storage.txt
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt
M tests/file_storage/tests.py
M tests/files/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #23157 -- Removed O(n) algorithm when uploading duplicate file 
names.

This is a security fix. Disclosure following shortly.


  Commit: 0268b855f9eab3377f2821164ef3e66037789e09
  
https://github.com/django/django/commit/0268b855f9eab3377f2821164ef3e66037789e09
  Author: Preston Holmes 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/contrib/auth/middleware.py
M django/contrib/auth/tests/test_remote_user.py
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt

  Log Message:
  ---
  [1.6.x] Fixed #23066 -- Modified RemoteUserMiddleware to logout on REMOTE_USE 
change.

This is a security fix. Disclosure following shortly.


  Commit: f7c494f2506250b8cb5923714360a3642ed63e0f
  
https://github.com/django/django/commit/f7c494f2506250b8cb5923714360a3642ed63e0f
  Author: Simon Charette 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/contrib/admin/exceptions.py
M django/contrib/admin/options.py
M django/contrib/admin/views/main.py
M docs/ref/exceptions.txt
M docs/releases/1.4.14.txt
M docs/releases/1.5.9.txt
M docs/releases/1.6.6.txt
M tests/admin_views/tests.py

  Log Message:
  ---
  [1.6.x] Prevented data leakage in contrib.admin via query string manipulation.

This is a security fix. Disclosure following shortly.


Compare: https://github.com/django/django/compare/48368d421cfd...f7c494f25062

-- 
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/53f4fce525dac_37833f95448a929c198e2%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23322: CircularDependencyError in migrations

[Django]

#23322: CircularDependencyError in migrations
-+-
 Reporter:  gabejackson  |Owner:
 Type:  Bug  |  Markush2010
Component:  Migrations   |   Status:  assigned
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:  migrations,  |   Resolution:
  circular dependency| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Markush2010):

 * needs_tests:  1 => 0


Comment:

 Tests are there.

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

Re: [Django] #23312: Windows/Python 3 test failure: test_unicode_decode_error

[Django]

#23312: Windows/Python 3 test failure: test_unicode_decode_error
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  1.7-rc-2
 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 ramiro):

 * stage:  Unreviewed => Accepted


Comment:

 Bisection between 1.7c1 (good) and current stable/1.7.x tip (bad) reports
 that the issue was introduced with commit
 e705d8c4b49d5c5ee747075f12709011f55b7a8a

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

[django/django] 6f59d2: Fixed flake8 warnings.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6f59d291585420800275cff8aa8377c19616b79a
  
https://github.com/django/django/commit/6f59d291585420800275cff8aa8377c19616b79a
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M tests/handlers/tests.py

  Log Message:
  ---
  Fixed flake8 warnings.


-- 
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/53f4eb315431d_1f563f9e4aced2b890235%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 298148: [1.7.x] Fixed flake8 warnings.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 298148528059a84887364acc8a2faa3220eb4897
  
https://github.com/django/django/commit/298148528059a84887364acc8a2faa3220eb4897
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M tests/handlers/tests.py

  Log Message:
  ---
  [1.7.x] Fixed flake8 warnings.

Backport of 6f59d29158 from master


-- 
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/53f4eb392acf2_35103fd2b916b2c0719fd%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23315: Cannot resolve operation dependencies

[Django]

#23315: Cannot resolve operation dependencies
-+-
 Reporter:  gabejackson  |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  migrations,  | Triage Stage:  Accepted
  autodetector, circular dependency  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timgraham):

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


Comment:

 `do_pending_lookups` wasn't resolving the field due to a case mismatch.

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

Re: [Django] #23315: Cannot resolve operation dependencies

[Django]

#23315: Cannot resolve operation dependencies
-+-
 Reporter:  gabejackson  |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  autodetector, circular dependency  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"6981eced83ea2d6462b21c12ecea044e02e56d05"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6981eced83ea2d6462b21c12ecea044e02e56d05"
 [1.7.x] Fixed migrations tests added in refs #23315.

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

[django/django] 6981ec: [1.7.x] Fixed migrations tests added in refs #2331...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 6981eced83ea2d6462b21c12ecea044e02e56d05
  
https://github.com/django/django/commit/6981eced83ea2d6462b21c12ecea044e02e56d05
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M tests/migrations/test_autodetector.py

  Log Message:
  ---
  [1.7.x] Fixed migrations tests added in refs #23315.

Backport of d1299fce0e from master


-- 
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/53f4e2bd10377_7fb13fcff34512a0215de%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23315: Cannot resolve operation dependencies

[Django]

#23315: Cannot resolve operation dependencies
-+-
 Reporter:  gabejackson  |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  autodetector, circular dependency  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"d1299fce0eeeb2a7749fecafc87260462e75aac9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d1299fce0eeeb2a7749fecafc87260462e75aac9"
 Fixed migrations tests added in refs #23315.
 }}}

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

[django/django] d1299f: Fixed migrations tests added in refs #23315.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d1299fce0eeeb2a7749fecafc87260462e75aac9
  
https://github.com/django/django/commit/d1299fce0eeeb2a7749fecafc87260462e75aac9
  Author: Tim Graham 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M tests/migrations/test_autodetector.py

  Log Message:
  ---
  Fixed migrations tests added in refs #23315.


-- 
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/53f4e27496201_72da3f98ff98d2bc901c1%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[Django] #23326: DatabaseCache must implement incr to guarantee atomic increment

[Django]

#23326: DatabaseCache must implement incr to guarantee atomic increment
-+
 Reporter:  vinayan3 |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Cache system)  |Version:  1.6
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 django.core.cache.backends.db.DatabaseCache uses BasesCache's incr which
 does a get followed by a set. If the application uses multiple servers the
 increments will get clobbered. Furthermore, the current implementation
 overwrites the expiry time of a key to the default value instead of using
 the value which was initially set.

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

Re: [Django] #23315: Cannot resolve operation dependencies

[Django]

#23315: Cannot resolve operation dependencies
-+-
 Reporter:  gabejackson  |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  autodetector, circular dependency  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by andrewgodwin):

 That's odd, because all the other relationships in that test file are fine
 under 3.4. It's likely an issue in the State's reconstruction of it. Happy
 to look at this instead if you want to hand it over.

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

Re: [Django] #23322: CircularDependencyError in migrations

[Django]

#23322: CircularDependencyError in migrations
-+-
 Reporter:  gabejackson  |Owner:
 Type:  Bug  |  Markush2010
Component:  Migrations   |   Status:  assigned
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:  migrations,  |   Resolution:
  circular dependency| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by andrewgodwin):

 Without a small test case writing a test is going to be very hard. I can
 have a go if you're willing to assign the ticket to 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/069.96a29498bd14fb38db13507973f72837%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15802: Django stops functioning when the database (PostgreSQL) closes the connection

[Django]

#15802: Django stops functioning when the database (PostgreSQL) closes the
connection
-+-
 Reporter:  Rick.van.Hattem@…|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  database, postgres,  |  Needs documentation:  0
  postgresql, connection, closed |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aivus):

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

Re: [Django] #23325: InterfaceError: connection already closed in PostgreSQL

[Django]

#23325: InterfaceError: connection already closed in PostgreSQL
-+-
 Reporter:  aivus|Owner:
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  InterfaceError,  |  Unreviewed
  postgresql |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 Yes, it's a duplicate of #15802. Until today I thought it was impossible,
 but I just had a new idea, so I'm reopened 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/063.04f6e1dd6e41282d65687a2f4d6d9146%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15802: Django stops functioning when the database (PostgreSQL) closes the connection

[Django]

#15802: Django stops functioning when the database (PostgreSQL) closes the
connection
-+-
 Reporter:  Rick.van.Hattem@…|Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  database, postgres,  |  Needs documentation:  0
  postgresql, connection, closed |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 I'm reopening this ticket because I want to think about reopening the
 connection automatically when no transaction is in progress.

 There's probably a bunch of issues with that technique, like retrying a
 query that failed.

 But since "connection closed" errors are a problem many users struggle
 with, it's worth making sure I haven't overlooked a solution.

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

Re: [Django] #15802: Django stops functioning when the database (PostgreSQL) closes the connection

[Django]

#15802: Django stops functioning when the database (PostgreSQL) closes the
connection
-+-
 Reporter:  Rick.van.Hattem@…|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  database, postgres,  |  Needs documentation:  0
  postgresql, connection, closed |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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

Re: [Django] #15802: Django stops functioning when the database (PostgreSQL) closes the connection

[Django]

#15802: Django stops functioning when the database (PostgreSQL) closes the
connection
-+-
 Reporter:  Rick.van.Hattem@…|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  database, postgres,  |  Needs documentation:  0
  postgresql, connection, closed |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by aaugustin):

 #23325 was a duplicate.

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

Re: [Django] #23315: Cannot resolve operation dependencies

[Django]

#23315: Cannot resolve operation dependencies
-+-
 Reporter:  gabejackson  |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  autodetector, circular dependency  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timgraham):

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


Comment:

 I'm looking into this. It seems to be a non-deterministic issue, perhaps
 ordering related.

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

Re: [Django] #23325: InterfaceError: connection already closed in PostgreSQL (was: InterfaceError: connection already closed in PostreSQL)

[Django]

#23325: InterfaceError: connection already closed in PostgreSQL
-+-
 Reporter:  aivus|Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  InterfaceError,  |  Unreviewed
  postgresql |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  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/063.bf42033b51bed1cdcb9ca4045f393946%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23325: InterfaceError: connection already closed in PostreSQL

[Django]

#23325: InterfaceError: connection already closed in PostreSQL
-+-
 Reporter:  aivus|Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  InterfaceError,  |  Unreviewed
  postgresql |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aivus):

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


Comment:

 Replying to [comment:1 timgraham]:
 > Why do you think this is a bug in Django? How do you expect Django to
 react when the database terminates the connection?
 I think Django should do reconnect, when connection is lost.

 I have worker, which work with database(Model.objects.all()) every 2
 minutes and I got "connection already closed" error from time to time

 Server restart - it's example.

 I think this is something like #15802

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

Re: [Django] #6342: Option to remove 'www.' from URLs

[Django]

#6342: Option to remove 'www.' from URLs
-+-
 Reporter:  corporeal|Owner:  nobody
|   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Core (Other) |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  www remove   |  decision needed
  global_settings middleware common  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by pjrobertson):

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


Comment:

 ...and for anybody looking for this middleware like me, here's a link to
 get you started:

 http://dryan.me/articles/remove-www-urls-django/

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

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

Re: [Django] #23322: CircularDependencyError in migrations

[Django]

#23322: CircularDependencyError in migrations
-+-
 Reporter:  gabejackson  |Owner:
 Type:  Bug  |  Markush2010
Component:  Migrations   |   Status:  assigned
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:  migrations,  |   Resolution:
  circular dependency| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Markush2010):

 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 Here's the pull request. Needs some tests though:
 https://github.com/django/django/pull/3093

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

Re: [Django] #23325: InterfaceError: connection already closed in PostreSQL

[Django]

#23325: InterfaceError: connection already closed in PostreSQL
-+-
 Reporter:  aivus|Owner:
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:  InterfaceError,  |  Unreviewed
  postgresql |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 Yes, unless I missed something, this is the expected behavior.

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

Re: [Django] #23302: Give a name to a migration from command line option

[Django]

#23302: Give a name to a migration from command line option
-+
 Reporter:  rsalmaso |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-2
 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
-+

Comment (by rsalmaso):

 PR updates with comments.

 If the 1.7 backport is too late please close its PR (I can maintain a
 private "fork" or continue to use mv until 1.8) and I'll add the `..
 versionadded:: 1.8` string.

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

Re: [Django] #23325: InterfaceError: connection already closed in PostreSQL

[Django]

#23325: InterfaceError: connection already closed in PostreSQL
-+-
 Reporter:  aivus|Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  InterfaceError,  |  Unreviewed
  postgresql |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timgraham):

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


Comment:

 Why do you think this is a bug in Django? How do you expect Django to
 react when the database terminates the connection?

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

Re: [Django] #20734: URL namespacing documentation should be clearer

[Django]

#20734: URL namespacing documentation should be clearer
--+
 Reporter:  EvilDMP   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.5
 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


Comment:

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

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

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

Re: [Django] #17707: Docs for URL namespaces should explain the motivation and use cases

[Django]

#17707: Docs for URL namespaces should explain the motivation and use cases
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #23324: sites framework docs - omits the site id from the Site model

[Django]

#23324: sites framework docs - omits the site id from the Site model
-+-
 Reporter:  kiddhustle   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  documentaion |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Does the attached patch make sense to you?

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

[Django] #23325: InterfaceError: connection already closed in PostreSQL

[Django]

#23325: InterfaceError: connection already closed in PostreSQL
-+-
 Reporter:  aivus|  Owner:
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:  1.6
  (models, ORM)  |   Keywords:  InterfaceError,
 Severity:  Normal   |  postgresql
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I have 1.6.5 django with psycopg 2.5.3.
 This exception happened when connection was closed by postgres.

 Related issue #21553
 {{{
 2014-08-19 13:32:46.414848 - ERROR:apscheduler.executors.default:Job
 "expire_key_notify (trigger: interval[0:01:00], next run at: 2014-08-19
 13:33:46 EEST)" raised an exception
 2014-08-19 13:32:46.414934 - Traceback (most recent call last):
 2014-08-19 13:32:46.415001 -   File "/home/user/projects/virtualenvs/test-
 system2/local/lib/python2.7/site-packages/apscheduler/executors/base.py",
 line 108, in run_job
 2014-08-19 13:32:46.415056 - retval = job.func(*job.args,
 **job.kwargs)
 2014-08-19 13:32:46.415105 -   File "./test/test_app/workflow/monitor.py",
 line 508, in expire_key_notify
 2014-08-19 13:32:46.415151 - for event in
 Event.objects.filter(done=False,
 event_after__lte=TimeManager.get_time()).all():
 2014-08-19 13:32:46.415199 -   File "/home/user/projects/virtualenvs/test-
 system2/local/lib/python2.7/site-packages/django/db/models/query.py", line
 96, in __iter__
 2014-08-19 13:32:46.415245 - self._fetch_all()
 2014-08-19 13:32:46.415293 -   File "/home/user/projects/virtualenvs/test-
 system2/local/lib/python2.7/site-packages/django/db/models/query.py", line
 854, in _fetch_all
 2014-08-19 13:32:46.415338 - self._result_cache =
 list(self.iterator())
 2014-08-19 13:32:46.415385 -   File "/home/user/projects/virtualenvs/test-
 system2/local/lib/python2.7/site-packages/django/db/models/query.py", line
 220, in iterator
 2014-08-19 13:32:46.415431 - for row in compiler.results_iter():
 2014-08-19 13:32:46.415524 -   File "/home/user/projects/virtualenvs/test-
 system2/local/lib/python2.7/site-
 packages/django/db/models/sql/compiler.py", line 713, in results_iter
 2014-08-19 13:32:46.415574 - for rows in self.execute_sql(MULTI):
 2014-08-19 13:32:46.415620 -   File "/home/user/projects/virtualenvs/test-
 system2/local/lib/python2.7/site-
 packages/django/db/models/sql/compiler.py", line 785, in execute_sql
 2014-08-19 13:32:46.415667 - cursor = self.connection.cursor()
 2014-08-19 13:32:46.415711 -   File "/home/user/projects/virtualenvs/test-
 system2/local/lib/python2.7/site-packages/django/db/backends/__init__.py",
 line 160, in cursor
 2014-08-19 13:32:46.415757 - cursor =
 self.make_debug_cursor(self._cursor())
 2014-08-19 13:32:46.415802 -   File "/home/user/projects/virtualenvs/test-
 system2/local/lib/python2.7/site-packages/django/db/backends/__init__.py",
 line 134, in _cursor
 2014-08-19 13:32:46.415848 - return self.create_cursor()
 2014-08-19 13:32:46.415896 -   File "/home/user/projects/virtualenvs/test-
 system2/local/lib/python2.7/site-packages/django/db/utils.py", line 99, in
 __exit__
 2014-08-19 13:32:46.415943 - six.reraise(dj_exc_type, dj_exc_value,
 traceback)
 2014-08-19 13:32:46.415992 -   File "/home/user/projects/virtualenvs/test-
 system2/local/lib/python2.7/site-packages/django/db/backends/__init__.py",
 line 134, in _cursor
 2014-08-19 13:32:46.416078 - return self.create_cursor()
 2014-08-19 13:32:46.416127 -   File "/home/user/projects/virtualenvs/test-
 system2/local/lib/python2.7/site-
 packages/django/db/backends/postgresql_psycopg2/base.py", line 137, in
 create_cursor
 2014-08-19 13:32:46.416176 - cursor = self.connection.cursor()
 2014-08-19 13:32:46.416227 - InterfaceError: connection already closed
 }}}

 Additional, I have other exception when postgres server was restarted

 {{{
 ERROR:apscheduler.executors.default:Job "sync_db_with_queue (trigger:
 interval[0:02:00], next run at: 2014-08-20 16:20:18 EEST)" raised an
 exception
 Traceback (most recent call last):
   File "/home/user/projects/.test-system/local/lib/python2.7/site-
 packages/apscheduler/executors/base.py", line 108, in run_job
 retval = job.func(*job.args, **job.kwargs)
   File "/home/user/projects/test-
 system/test/test_app/workflow/monitor.py", line 369, in sync_db_with_queue
 for task in
 
JobProcessReceipt.objects.filter(status=JobProcessReceipt.enum_receipt_status.queue,
 create_ts__lt=int(time.time()-30)):
   File "/home/user/projects/.test-system/local/lib/python2.7/site-
 packages/django/db/models/query.py", line 96, in __iter__
 self._fetch_all()
   File "/home/user/projects/.test-system/local/lib/python2.7/site-
 packages/django/db/models/query.py", line 857, in _fetch_all
 self._result_

[Django] #23324: sites framework docs - omits the site id from the Site model

[Django]

#23324: sites framework docs - omits the site id from the Site model
--+--
 Reporter:  kiddhustle|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.6
 Severity:  Normal|   Keywords:  documentaion
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+--
 The documentation for the sites framework omits the site id from the
 model.

 The site id is automatically added to the model by Django (the '''id
 attribute''') but no where in the documentation does it say that the user
 can access the '''current site_id''' via the model, only the ''domain''
 and ''name'' attributes are shown.

 It took me a good hour or so of searching for a way to get the current
 site id, before realising that like most model an 'id' attribute would be
 created for the Site model by Django (after browsing the Django source
 code).

 I should have guessed this earlier but it '''wasn't made obvious in the
 documentation'''.

 https://docs.djangoproject.com/en/1.6/ref/contrib/sites/

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

Re: [Django] #23315: Cannot resolve operation dependencies

[Django]

#23315: Cannot resolve operation dependencies
-+-
 Reporter:  gabejackson  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  autodetector, circular dependency  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timgraham):

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


Comment:

 The new test fails on Python 3.4:
 {{{
 ==
 ERROR [0.001s]: test_circular_dependency_mixed_addcreate
 (migrations.test_autodetector.AutodetectorTests)
 --
 Traceback (most recent call last):
   File "/home/jenkins/workspace/django-
 
master/database/sqlite3/python/python3.4/tests/migrations/test_autodetector.py",
 line 1099, in test_circular_dependency_mixed_addcreate
 changes = autodetector._detect_changes()
   File "/home/jenkins/workspace/django-
 master/database/sqlite3/python/python3.4/django/db/migrations/autodetector.py",
 line 172, in _detect_changes
 self.generate_created_models()
   File "/home/jenkins/workspace/django-
 master/database/sqlite3/python/python3.4/django/db/migrations/autodetector.py",
 line 497, in generate_created_models
 dep_app_label = field.rel.to._meta.app_label
 AttributeError: 'str' object has no attribute '_meta'
 }}}
 The string is `"a.person"` (but resolves to `` when the
 test passes).

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

Re: [Django] #23302: Give a name to a migration from command line option

[Django]

#23302: Give a name to a migration from command line option
-+
 Reporter:  rsalmaso |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-2
 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):

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


Comment:

 In my opinion this isn't a release blocking issue, so it doesn't qualify
 for backport to 1.7. I left some comments for improvement on the PR
 against 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/066.2b38e619bb6e0af6b03cc366b3888d68%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23322: CircularDependencyError in migrations

[Django]

#23322: CircularDependencyError in migrations
-+-
 Reporter:  gabejackson  |Owner:
 Type:  Bug  |  Markush2010
Component:  Migrations   |   Status:  assigned
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:  migrations,  |   Resolution:
  circular dependency| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bmispelon):

 * stage:  Unreviewed => Accepted


Comment:

 Accepting per previous comment.

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

Re: [Django] #23322: CircularDependencyError in migrations

[Django]

#23322: CircularDependencyError in migrations
-+-
 Reporter:  gabejackson  |Owner:
 Type:  Bug  |  Markush2010
Component:  Migrations   |   Status:  assigned
 Severity:  Release blocker  |  Version:  1.7-rc-2
 Keywords:  migrations,  |   Resolution:
  circular dependency| Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Markush2010):

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


Comment:

 I can confirm the bug. I'm working on a fix.

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

Re: [Django] #23323: Allow the use of translation.override as a decorator

[Django]

#23323: Allow the use of translation.override as a decorator
--+--
 Reporter:  tchaumeny |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Translations  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by tchaumeny):

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


Comment:

 Here is my pull request for this feature:
 https://github.com/django/django/pull/3088

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

[Django] #23323: Allow the use of translation.override as a decorator

[Django]

#23323: Allow the use of translation.override as a decorator
--+
 Reporter:  tchaumeny |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Translations  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 I think it would be nice if `translation.override` could be used as a
 decorator.

 Although a comment in
 https://code.djangoproject.com/ticket/16690#comment:2 suggested this was
 not useful, I have experienced several cases where it is. For instance, I
 have some functions which are sending mail and I want those mails to be
 translated in some default language which is not the one of the user doing
 the action. Having the function decorated is better in terms of
 readability than a long `with` statement which introduces heavy
 indentation.

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

Re: [Django] #23322: CircularDependencyError in migrations

[Django]

#23322: CircularDependencyError in migrations
-+-
 Reporter:  gabejackson  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:
  circular dependency|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by gabejackson):

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


Comment:

 Added a Graph of the Models if that helps anybody:
 https://github.com/gabejackson/django-migration-
 test/blob/circ_dep_1/models.pdf

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

[Django] #23322: CircularDependencyError in migrations

[Django]

#23322: CircularDependencyError in migrations
-+-
 Reporter:  gabejackson  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Migrations   |Version:  1.7-rc-2
 Severity:  Release  |   Keywords:  migrations, circular dependency
  blocker|  Has patch:  0
 Triage Stage:  Unreviewed   |  UI/UX:  0
Easy pickings:  0|
-+-
 django.db.migrations.graph.CircularDependencyError

 Test Project is located here: https://github.com/gabejackson/django-
 migration-test/tree/circ_dep_1

 Steps to reproduce:
 Install stable/1.7.x branch in venv
 ./manage.py makemigrations
 ... [OK]
 ./manage.py migrate

 {{{
 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File
 
"/Users/gabejackson/venv/django-1.7/src/django/django/core/management/__init__.py",
 line 385, in execute_from_command_line
 utility.execute()
   File
 
"/Users/gabejackson/venv/django-1.7/src/django/django/core/management/__init__.py",
 line 377, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File
 "/Users/gabejackson/venv/django-1.7/src/django/django/core/management/base.py",
 line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File
 "/Users/gabejackson/venv/django-1.7/src/django/django/core/management/base.py",
 line 338, in execute
 output = self.handle(*args, **options)
   File
 
"/Users/gabejackson/venv/django-1.7/src/django/django/core/management/commands/migrate.py",
 line 106, in handle
 plan = executor.migration_plan(targets)
   File
 
"/Users/gabejackson/venv/django-1.7/src/django/django/db/migrations/executor.py",
 line 49, in migration_plan
 for migration in self.loader.graph.forwards_plan(target):
   File
 "/Users/gabejackson/venv/django-1.7/src/django/django/db/migrations/graph.py",
 line 55, in forwards_plan
 return self.dfs(node, lambda x: self.dependencies.get(x, set()))
   File
 "/Users/gabejackson/venv/django-1.7/src/django/django/db/migrations/graph.py",
 line 121, in dfs
 return _dfs(start, get_children, [])
   File
 "/Users/gabejackson/venv/django-1.7/src/django/django/db/migrations/graph.py",
 line 113, in _dfs
 results = _dfs(n, get_children, path) + results
   File
 "/Users/gabejackson/venv/django-1.7/src/django/django/db/migrations/graph.py",
 line 113, in _dfs
 results = _dfs(n, get_children, path) + results
   File
 "/Users/gabejackson/venv/django-1.7/src/django/django/db/migrations/graph.py",
 line 113, in _dfs
 results = _dfs(n, get_children, path) + results
   File
 "/Users/gabejackson/venv/django-1.7/src/django/django/db/migrations/graph.py",
 line 113, in _dfs
 results = _dfs(n, get_children, path) + results
   File
 "/Users/gabejackson/venv/django-1.7/src/django/django/db/migrations/graph.py",
 line 105, in _dfs
 raise CircularDependencyError(path[path.index(start):] + [start])
 django.db.migrations.graph.CircularDependencyError: [(u'a',
 u'0001_initial'), ('c', u'0001_initial'), (u'b', u'0001_initial'), (u'a',
 u'0001_initial')]
 }}}

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

[django/django] 724d72: Added Chinese language aliases in tx client config

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 724d72e1a2eb898eedf9bd307c20918910cd2ade
  
https://github.com/django/django/commit/724d72e1a2eb898eedf9bd307c20918910cd2ade
  Author: Claude Paroz 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M .tx/config

  Log Message:
  ---
  Added Chinese language aliases in tx client config

Transifex doesn't have zh_Hans/zh_Hant locales.
Forward port of c586fcd4eade5 from stable/1.7.x


  Commit: efa67b897b6ed5c6bbee1aa2646f4ba7ea6e2bc2
  
https://github.com/django/django/commit/efa67b897b6ed5c6bbee1aa2646f4ba7ea6e2bc2
  Author: Claude Paroz 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/conf/locale/af/LC_MESSAGES/django.mo
M django/conf/locale/af/LC_MESSAGES/django.po
M django/conf/locale/ar/LC_MESSAGES/django.mo
M django/conf/locale/ar/LC_MESSAGES/django.po
A django/conf/locale/ast/LC_MESSAGES/django.mo
A django/conf/locale/ast/LC_MESSAGES/django.mo
A django/conf/locale/ast/LC_MESSAGES/django.po
M django/conf/locale/az/LC_MESSAGES/django.mo
M django/conf/locale/az/LC_MESSAGES/django.po
M django/conf/locale/be/LC_MESSAGES/django.mo
M django/conf/locale/be/LC_MESSAGES/django.po
M django/conf/locale/bg/LC_MESSAGES/django.mo
M django/conf/locale/bg/LC_MESSAGES/django.po
M django/conf/locale/bn/LC_MESSAGES/django.mo
M django/conf/locale/bn/LC_MESSAGES/django.po
M django/conf/locale/br/LC_MESSAGES/django.mo
M django/conf/locale/br/LC_MESSAGES/django.po
M django/conf/locale/bs/LC_MESSAGES/django.mo
M django/conf/locale/bs/LC_MESSAGES/django.po
M django/conf/locale/ca/LC_MESSAGES/django.mo
M django/conf/locale/ca/LC_MESSAGES/django.po
M django/conf/locale/cs/LC_MESSAGES/django.mo
M django/conf/locale/cs/LC_MESSAGES/django.po
M django/conf/locale/cy/LC_MESSAGES/django.mo
M django/conf/locale/cy/LC_MESSAGES/django.po
M django/conf/locale/da/LC_MESSAGES/django.mo
M django/conf/locale/da/LC_MESSAGES/django.po
M django/conf/locale/de/LC_MESSAGES/django.mo
M django/conf/locale/de/LC_MESSAGES/django.po
M django/conf/locale/el/LC_MESSAGES/django.mo
M django/conf/locale/el/LC_MESSAGES/django.po
A django/conf/locale/en_AU/LC_MESSAGES/django.mo
A django/conf/locale/en_AU/LC_MESSAGES/django.mo
A django/conf/locale/en_AU/LC_MESSAGES/django.po
M django/conf/locale/en_GB/LC_MESSAGES/django.mo
M django/conf/locale/en_GB/LC_MESSAGES/django.po
M django/conf/locale/eo/LC_MESSAGES/django.mo
M django/conf/locale/eo/LC_MESSAGES/django.po
M django/conf/locale/es/LC_MESSAGES/django.mo
M django/conf/locale/es/LC_MESSAGES/django.po
M django/conf/locale/es_AR/LC_MESSAGES/django.mo
M django/conf/locale/es_AR/LC_MESSAGES/django.po
M django/conf/locale/es_MX/LC_MESSAGES/django.mo
M django/conf/locale/es_MX/LC_MESSAGES/django.po
M django/conf/locale/es_VE/LC_MESSAGES/django.mo
M django/conf/locale/es_VE/LC_MESSAGES/django.po
M django/conf/locale/et/LC_MESSAGES/django.mo
M django/conf/locale/et/LC_MESSAGES/django.po
M django/conf/locale/eu/LC_MESSAGES/django.mo
M django/conf/locale/eu/LC_MESSAGES/django.po
M django/conf/locale/fa/LC_MESSAGES/django.mo
M django/conf/locale/fa/LC_MESSAGES/django.po
M django/conf/locale/fi/LC_MESSAGES/django.mo
M django/conf/locale/fi/LC_MESSAGES/django.po
M django/conf/locale/fr/LC_MESSAGES/django.mo
M django/conf/locale/fr/LC_MESSAGES/django.po
A django/conf/locale/io/LC_MESSAGES/django.mo
A django/conf/locale/io/LC_MESSAGES/django.po
A django/conf/locale/mr/LC_MESSAGES/django.mo
A django/conf/locale/mr/LC_MESSAGES/django.po
A django/contrib/admin/locale/ast/LC_MESSAGES/django.mo
A django/contrib/admin/locale/ast/LC_MESSAGES/django.po
A django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo
A django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po
A django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo
A django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po
A django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo
A django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po
A django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo
A django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po
A django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo
A django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po

  Log Message:
  ---
  Fetched translations from Transifex

Forward port of 49280a73ea5 from stable/1.7.x


Compare: https://github.com/django/django/compare/12cf10cacd62...efa67b897b6e

-- 
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 vi

[Django] #23321: Remove .mo files from the Django Git repository

[Django]

#23321: Remove .mo files from the Django Git repository
+
   Reporter:  claudep   |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Internationalization  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Binary/generated files are no good candidates to be included in a Git
 repository. They unnecessarily bloat the repository without added value.
 It would be nice to compile those .mo files at package build time.

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

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

[django/django] c586fc: [1.7.x] Added Chinese language aliases in tx clien...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: c586fcd4eade52fad7528f322a8dff034f68b577
  
https://github.com/django/django/commit/c586fcd4eade52fad7528f322a8dff034f68b577
  Author: Claude Paroz 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M .tx/config

  Log Message:
  ---
  [1.7.x] Added Chinese language aliases in tx client config

Transifex doesn't have zh_Hans/zh_Hant locales.


  Commit: 49280a73ea533bca0b870d1b135bb9e4a7ce989b
  
https://github.com/django/django/commit/49280a73ea533bca0b870d1b135bb9e4a7ce989b
  Author: Claude Paroz 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M django/conf/locale/af/LC_MESSAGES/django.mo
M django/conf/locale/af/LC_MESSAGES/django.po
M django/conf/locale/ar/LC_MESSAGES/django.mo
M django/conf/locale/ar/LC_MESSAGES/django.po
A django/conf/locale/ast/LC_MESSAGES/django.mo
A django/conf/locale/ast/LC_MESSAGES/django.mo
A django/conf/locale/ast/LC_MESSAGES/django.po
M django/conf/locale/az/LC_MESSAGES/django.mo
M django/conf/locale/az/LC_MESSAGES/django.po
M django/conf/locale/be/LC_MESSAGES/django.mo
M django/conf/locale/be/LC_MESSAGES/django.po
M django/conf/locale/bg/LC_MESSAGES/django.mo
M django/conf/locale/bg/LC_MESSAGES/django.po
M django/conf/locale/bn/LC_MESSAGES/django.mo
M django/conf/locale/bn/LC_MESSAGES/django.po
M django/conf/locale/br/LC_MESSAGES/django.mo
M django/conf/locale/br/LC_MESSAGES/django.po
M django/conf/locale/bs/LC_MESSAGES/django.mo
M django/conf/locale/bs/LC_MESSAGES/django.po
M django/conf/locale/ca/LC_MESSAGES/django.mo
M django/conf/locale/ca/LC_MESSAGES/django.po
M django/conf/locale/cs/LC_MESSAGES/django.mo
M django/conf/locale/cs/LC_MESSAGES/django.po
M django/conf/locale/cy/LC_MESSAGES/django.mo
M django/conf/locale/cy/LC_MESSAGES/django.po
M django/conf/locale/da/LC_MESSAGES/django.mo
M django/conf/locale/da/LC_MESSAGES/django.po
M django/conf/locale/de/LC_MESSAGES/django.mo
M django/conf/locale/de/LC_MESSAGES/django.po
M django/conf/locale/el/LC_MESSAGES/django.mo
M django/conf/locale/el/LC_MESSAGES/django.po
A django/conf/locale/en_AU/LC_MESSAGES/django.mo
A django/conf/locale/en_AU/LC_MESSAGES/django.mo
A django/conf/locale/en_AU/LC_MESSAGES/django.po
M django/conf/locale/en_GB/LC_MESSAGES/django.mo
M django/conf/locale/en_GB/LC_MESSAGES/django.po
M django/conf/locale/eo/LC_MESSAGES/django.mo
M django/conf/locale/eo/LC_MESSAGES/django.po
M django/conf/locale/es/LC_MESSAGES/django.mo
M django/conf/locale/es/LC_MESSAGES/django.po
M django/conf/locale/es_AR/LC_MESSAGES/django.mo
M django/conf/locale/es_AR/LC_MESSAGES/django.po
M django/conf/locale/es_MX/LC_MESSAGES/django.mo
M django/conf/locale/es_MX/LC_MESSAGES/django.po
M django/conf/locale/es_VE/LC_MESSAGES/django.mo
M django/conf/locale/es_VE/LC_MESSAGES/django.po
M django/conf/locale/et/LC_MESSAGES/django.mo
M django/conf/locale/et/LC_MESSAGES/django.po
M django/conf/locale/eu/LC_MESSAGES/django.mo
M django/conf/locale/eu/LC_MESSAGES/django.po
M django/conf/locale/fa/LC_MESSAGES/django.mo
M django/conf/locale/fa/LC_MESSAGES/django.po
M django/conf/locale/fi/LC_MESSAGES/django.mo
M django/conf/locale/fi/LC_MESSAGES/django.po
M django/conf/locale/fr/LC_MESSAGES/django.mo
M django/conf/locale/fr/LC_MESSAGES/django.po
A django/conf/locale/io/LC_MESSAGES/django.mo
A django/conf/locale/io/LC_MESSAGES/django.po
A django/conf/locale/mr/LC_MESSAGES/django.mo
A django/conf/locale/mr/LC_MESSAGES/django.po
A django/contrib/admin/locale/ast/LC_MESSAGES/django.mo
A django/contrib/admin/locale/ast/LC_MESSAGES/django.po
A django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo
A django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po
A django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo
A django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po
A django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo
A django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po
A django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo
A django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po
A django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo
A django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po

  Log Message:
  ---
  [1.7.x] Fetched translations from Transifex


Compare: https://github.com/django/django/compare/cba018242527...49280a73ea53

-- 
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/dj

Re: [Django] #8391: slugify template filter poorly encodes non-English strings

[Django]

#8391: slugify template filter poorly encodes non-English strings
-+
 Reporter:  bjornkri |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  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 claudep):

 Note that slugify2 is now here: https://github.com/mitar/django-
 missing/blob/master/missing/templatetags/url_tags.py

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

Re: [Django] #23320: FloatField not converting values to float()

[Django]

#23320: FloatField not converting values to float()
-+-
 Reporter:  pjrobertson  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.7-rc-2
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Old description:

> Apologies for creating an issue if this is the expected behaviour (FWIW
> there were no ideas on IRC):
>
> Is the behaviour outlined in this snippet expected:
> https://dpaste.de/BAck
>
> I'd have expected the FloatField to convert values to a float in the
> return object as well (I can verify that the `to_python` method is being
> run, because the number is saved to the database correctly.
>

> Is the recommended way of solving this to subclass FloatField and use?
>

> {{{
> class MyFloatField(with_metaclass(models.SubBaseField,
> models.FloadField)):
>...
> }}}

New description:

 Apologies for creating an issue if this is the expected behaviour (FWIW
 there were no ideas on IRC):

 Is the behaviour outlined in this snippet expected:
 {{{#!python
 # models.py
 from django.db import models

 class Fl(models.Model):

 float = models.FloatField()


 # ./manage.py shell
 >>> from models import Fl
 >>> a = Fl.objects.create(float=' 1.0 ')
 >>> a
 
 >>> a.float
 ' 1.0 '
 }}}

 I'd have expected the FloatField to convert values to a float in the
 return object as well (I can verify that the `to_python` method is being
 run, because the number is saved to the database correctly.


 Is the recommended way of solving this to subclass FloatField and use?


 {{{
 class MyFloatField(with_metaclass(models.SubBaseField,
 models.FloadField)):
...
 }}}

--

Comment (by bmispelon):

 (pulled in the code from dpaste so that this report still makes sense in 4
 weeks after the link expires)

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

[django/django] cba018: [1.7.x] Fixed typo in 1.7 release notes

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: cba018242527bb6bc3c0fd1a7e35495b6dcc25e4
  
https://github.com/django/django/commit/cba018242527bb6bc3c0fd1a7e35495b6dcc25e4
  Author: Claude Paroz 
  Date:   2014-08-20 (Wed, 20 Aug 2014)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  [1.7.x] Fixed typo in 1.7 release notes

Backport of 12cf10cacd6 from master.


-- 
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/53f447633fca3_414f3ffd16e112b81036d1%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.