[Django] #23073: Oracle 11.2.0.1: Number columns (incl. Booleans) defined with default break introspection

[Django]

#23073: Oracle 11.2.0.1: Number columns (incl. Booleans) defined with default 
break
introspection
-+
   Reporter:  shai   |  Owner:  shai
   Type:  Uncategorized  | Status:  new
  Component:  Migrations |Version:  master
   Severity:  Normal |   Keywords:  oracle
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 It seems that on this specific version of Oracle server, if you define a
 number column with a default, it gets precision 0. This, in turn, means it
 will be introspected as an `IntegerField`, even if it was a `BooleanField`
 or a `BigIntegerField` to begin with.

 I am not quite sure yet about this description, but that seems to be what
 I get from tests.

 I suspect this can be worked-around by changing the alter-column command
 which removes the default to also redefine the type. I am not sure
 supporting one specific, superseded, Oracle version, is worth the hassle.
 The point going for it is that this is the (Oracle 11) version one can
 download from Oracle for free, and so this is the version we are trying to
 use for our CI (and others may want to do the same).

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

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

Re: [Django] #23071: Can't create migration for apps that have ForeignKeys to each other

[Django]

#23071: Can't create migration for apps that have ForeignKeys to each other
-+--
 Reporter:  dekkers  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   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 dekkers):

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


Comment:

 https://github.com/django/django/pull/2938

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

[Django] #23072: Release tarball is missing django/contrib/formtools/tests/wizard/wizardtests/templates/other_wizard_form.html

[Django]

#23072: Release tarball is missing
django/contrib/formtools/tests/wizard/wizardtests/templates/other_wizard_form.html
-+--
 Reporter:  rhertzog |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Packaging|Version:  1.7-rc-1
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  0|  UI/UX:  0
-+--
 And since the file is missing the test suite is failing in
 
django.contrib.formtools.tests.wizard.wizardtests.tests.WizardTestKwargs.test_template
 with a "TemplateDoesNotExist: other_wizard_form.html" exception.

 A simple fix is:
 {{{
 $ git diff
 diff --git a/MANIFEST.in b/MANIFEST.in
 index 01aa49a..cbd641c 100644
 --- a/MANIFEST.in
 +++ b/MANIFEST.in
 @@ -24,6 +24,7 @@ recursive-include django/contrib/auth/tests/templates *
  recursive-include django/contrib/comments/templates *
  recursive-include django/contrib/formtools/templates *
  recursive-include django/contrib/formtools/tests/templates *
 +recursive-include
 django/contrib/formtools/tests/wizard/wizardtests/templates *
  recursive-include django/contrib/flatpages/fixtures *
  recursive-include django/contrib/flatpages/tests/templates *
  recursive-include django/contrib/gis/static *
 }}}

 The problem also exists on the master branch.

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

[Django] #23071: Can't create migration for apps that have ForeignKeys to each other

[Django]

#23071: Can't create migration for apps that have ForeignKeys to each other
-+--
 Reporter:  dekkers  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Migrations   |Version:  1.7-rc-1
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+--
 ForeignKey's to other apps create a dependency on {{{__latest__}}}
 migration of that app. Because of this we can't create migrations where we
 have ForeignKey relations that go both ways, because that would result in
 app1 depending on {{{__latest__}}} of app2 and app2 depending on
 {{{__latest__}}} of app1. Way to reproduce:

 Create the following model in myapp1:
 {{{
 class Model1(models.Model):
 field = models.CharField(max_length=10)
 }}}

 And the following model in myapp2:
 {{{
 class Model2(models.Model):
 field = models.CharField(max_length=10)
 }}}

 We run makemigations creating both initial migrations. We then add the
 following model in myapp1:
 {{{
 class Model3(models.Model):
 model2 = models.ForeignKey('myapp2.Model2')
 }}}
 We run makemigrations again, this will create a myapp1 migration that
 depends on {{{__latest__}}} of myapp2.

 Then we add the following model to myapp2:
 {{{
 class Model4(models.Model):
 model1 = models.ForeignKey('myapp1.Model1')
 }}}
 We then run makemigrations again, this will create a myapp2 migration that
 depends on {{{__latest__}}} of myapp1. Running migrate then gives us a
 circular dependency error:
 {{{
 django.db.migrations.graph.CircularDependencyError: [('myapp1',
 u'0002_model3'), ('myapp2', u'0002_model4'), ('myapp1', u'0002_model3')]
 }}}

 I think the correct way to create dependency would be to create an
 explicit dependency on the latest migration of the other app at the time
 of creating the new ForeigKey instead of using {{{__latest__}}}. This will
 mean that the second myapp1 migration will depend on myapp2's
 0001_initial, and the second myapp2 migration will depend on myapp1's
 0002_model3.

 I tested this and it seems to work fine.

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

Re: [Django] #23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907: missing right parenthesis when used with select_for_update.

[Django]

#23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907:
missing right parenthesis when used with select_for_update.
-+-
 Reporter:  michael.miller@… |Owner:  shai
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.7-rc-1
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle sql compiler  |  Needs documentation:  0
  ORA-00907  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by shai):

 * owner:  nobody => shai
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


Comment:

 Accepting for now on the quality of submission. Will investigate later. As
 an initial point, indeed, the `select_for_update` tests do not seem to
 include a test for using `get()` with `select_for_update`.

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

[Django] #23070: Instances of callable classes with __slots__ attributes in settings causes a failure to draw the 500 template

[Django]

#23070: Instances of callable classes with __slots__ attributes in settings 
causes
a failure to draw the 500 template
---+--
 Reporter:  colons |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.7-rc-1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 In a fresh django project, adding the following snippet to your settings
 files prevents the 500 page from rendering:

 {{{
 class Class(object):
 __slots__ = ['attr']

 def __init__(self, attr):
 self.attr = attr

 def __call__(self):
 pass

 INSTANCE = Class(1)
 }}}

 The error that prevents the 500 error page from rendering is:

 {{{
 Traceback (most recent call last):
   File
 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/wsgiref/handlers.py",
 line 85, in run
 self.result = application(self.environ, self.start_response)
   File "venv/lib/python2.7/site-
 packages/django/contrib/staticfiles/handlers.py", line 64, in __call__
 return self.application(environ, start_response)
   File "venv/lib/python2.7/site-packages/django/core/handlers/wsgi.py",
 line 191, in __call__
 response = self.get_response(request)
   File "venv/lib/python2.7/site-packages/django/core/handlers/base.py",
 line 198, in get_response
 response = self.handle_uncaught_exception(request, resolver,
 sys.exc_info())
   File "venv/lib/python2.7/site-packages/django/core/handlers/base.py",
 line 241, in handle_uncaught_exception
 return debug.technical_500_response(request, *exc_info)
   File "venv/lib/python2.7/site-packages/django/views/debug.py", line 79,
 in technical_500_response
 html = reporter.get_traceback_html()
   File "venv/lib/python2.7/site-packages/django/views/debug.py", line 337,
 in get_traceback_html
 c = Context(self.get_traceback_data(), use_l10n=False)
   File "venv/lib/python2.7/site-packages/django/views/debug.py", line 315,
 in get_traceback_data
 'settings': get_safe_settings(),
   File "venv/lib/python2.7/site-packages/django/views/debug.py", line 65,
 in get_safe_settings
 settings_dict[k] = cleanse_setting(k, getattr(settings, k))
   File "venv/lib/python2.7/site-packages/django/views/debug.py", line 55,
 in cleanse_setting
 cleansed.do_not_call_in_templates = True
 AttributeError: 'Class' object has no attribute 'do_not_call_in_templates
 }}}

 For me, this is a problem because I'm upgrading a project that stores what
 time of the week certain things happen with instances of dateutil's
 weekday object in the settings. Reproduced in 1.7c1 and current master,
 never happened in 1.6. I can probably work around it, but it'll be
 upsettingly inelegant.

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

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

Re: [Django] #23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907: missing right parenthesis when used with select_for_update.

[Django]

#23061: Oracle SQL compiler adding outer pagination selects causing ORA-00907:
missing right parenthesis when used with select_for_update.
-+-
 Reporter:  michael.miller@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7-rc-1
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  oracle sql compiler  |  Unreviewed
  ORA-00907  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by michael.miller@…):

 Just tried this with the latest development snapshot from github. Still
 experiencing the same error.

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

[Django] #23069: Can't rename model with ManyToMany relation

[Django]

#23069: Can't rename model with ManyToMany relation
-+--
 Reporter:  dekkers  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Migrations   |Version:  1.7-rc-1
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+--
 Given the following models:

 {{{
 class Model1(models.Model):
 field = models.CharField(max_length=10)
 many = models.ManyToManyField('Model2')


 class Model2(models.Model):
 field = models.CharField(max_length=10)
 }}}

 If I rename either Model1 or Model2 to Model3 I get the following error
 when running makemigrations:

 {{{
 CommandError: System check identified some issues:

 ERRORS:
 myapp1.Model3.many: (fields.E304) Reverse accessor for 'Model3.many'
 clashes with reverse accessor for 'Model3.field'.
 HINT: Add or change a related_name argument to the definition for
 'Model3.many' or 'Model3.field'.
 myapp2.Model3.field: (fields.E304) Reverse accessor for 'Model3.field'
 clashes with reverse accessor for 'Model3.many'.
 HINT: Add or change a related_name argument to the definition for
 'Model3.field' or 'Model3.many'.
 }}}

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

Re: [Django] #23060: UnicodeDecodeError in debug templatetag

[Django]

#23060: UnicodeDecodeError in debug templatetag
-+
 Reporter:  anonymous|Owner:  qingfeng
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+

Comment (by claudep):

 Template tags/filters tests are located in tests/template_tests.

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

[django/django] b4cf7e: Fixed typo in PermissionsMixin.groups.help_text.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b4cf7e3d1de2d9700812872b04f6fe8eb88e8bff
  
https://github.com/django/django/commit/b4cf7e3d1de2d9700812872b04f6fe8eb88e8bff
  Author: Iain Dawson 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/contrib/auth/models.py

  Log Message:
  ---
  Fixed typo in PermissionsMixin.groups.help_text.


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

[django/django] 205090: [1.6.x] Replaced instances of 'his/her' with 'thei...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 205090bc7173eff649dd7ef69805f9a760534b01
  
https://github.com/django/django/commit/205090bc7173eff649dd7ef69805f9a760534b01
  Author: Iain Dawson 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/contrib/auth/forms.py
M django/contrib/auth/models.py
M docs/internals/contributing/committing-code.txt
M docs/ref/contrib/auth.txt
M docs/topics/auth/customizing.txt
M docs/topics/auth/default.txt

  Log Message:
  ---
  [1.6.x] Replaced instances of 'his/her' with 'their'.

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

[django/django] 59fec1: [1.7.x] Replaced instances of 'his/her' with 'thei...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 59fec1ca9b3c426466f0c613a5ecf2badb992460
  
https://github.com/django/django/commit/59fec1ca9b3c426466f0c613a5ecf2badb992460
  Author: Iain Dawson 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/contrib/auth/forms.py
M django/contrib/auth/models.py
M docs/internals/contributing/committing-code.txt
M docs/ref/contrib/auth.txt
M docs/topics/auth/customizing.txt
M docs/topics/auth/default.txt

  Log Message:
  ---
  [1.7.x] Replaced instances of 'his/her' with 'their'.

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

[django/django] 8fbf13: Replaced instances of 'his/her' with 'their'.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8fbf13a6c85d68b996bc09cb6e8c969e5e32005b
  
https://github.com/django/django/commit/8fbf13a6c85d68b996bc09cb6e8c969e5e32005b
  Author: Iain Dawson 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/contrib/auth/forms.py
M django/contrib/auth/models.py
M docs/internals/contributing/committing-code.txt
M docs/ref/contrib/auth.txt
M docs/topics/auth/customizing.txt
M docs/topics/auth/default.txt

  Log Message:
  ---
  Replaced instances of 'his/her' with 'their'.


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

Re: [Django] #23068: Update docs to use django-admin instead of django-admin.py

[Django]

#23068: Update docs to use django-admin instead of django-admin.py
-+-
 Reporter:  timo |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.7-rc-1
Component:  Documentation|   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Double submit of #23067

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

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

Re: [Django] #23037: clarification on windows install and setup detail

[Django]

#23037: clarification on windows install and setup detail
---+--
 Reporter:  jomtung@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  windows| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 I created #23068 for updating to `django-admin`.

 I think we want to recommend using pip to install Django, even the
 development version, e.g.
 https://docs.djangoproject.com/en/dev/topics/install/#installing-the-
 development-version

 Unless there is some reason that doesn't work, let's avoid adding more
 Windows specific instructions.

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

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

[Django] #23067: Update docs to use django-admin instead of django-admin.py

[Django]

#23067: Update docs to use django-admin instead of django-admin.py
+--
   Reporter:  timo  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  1.7-rc-1
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+--
 Refs #21827 and the switch to setuptools in [66f546b].

 I don't think there's a reason not to make the change, although we're
 likely to get tickets from people using the wrong version of 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/047.e8416a92027d4541e7e0e8ebd31a6357%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23068: Update docs to use django-admin instead of django-admin.py

[Django]

#23068: Update docs to use django-admin instead of django-admin.py
+--
   Reporter:  timo  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  1.7-rc-1
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+--
 Refs #21827 and the switch to setuptools in [66f546b].

 I don't think there's a reason not to make the change, although we're
 likely to get tickets from people using the wrong version of 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/047.2780201d35ec23c7dbcc2e8b149e4578%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[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:   |  Owner:  nobody
  david.greisen@…| Status:  new
 Type:  Bug  |Version:  master
Component:   |   Keywords:  remoteUserBackend
  contrib.auth   |  RemoteUserMiddleware
 Severity:  Normal   |  Has patch:  0
 Triage Stage:   |  UI/UX:  0
  Unreviewed |
Easy pickings:  1|
-+-
 Currently, when remoteUserBackend fails to authenticate the
 username passed in the header, and create_unknown_user==False,
 RemoteUserMiddleware does nothing. Thus, if a different user
 was logged in, that user will remain logged in despite the failed
 attempt to log in a new user.

 This is a security issue.

 https://github.com/django/django/pull/2936 fixes this problem
 by logging out the request if the user returned
 by the middleware is None (a failed login attempt).

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

Re: [Django] #23014: Renaming a field in a unique_together fails

[Django]

#23014: Renaming a field in a unique_together fails
-+
 Reporter:  melinath |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   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 timo):

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


Comment:

 After this fix, I get infinite migrations when running `makemigrations`
 for auth & contenttypes.

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

Re: [Django] #23055: Filters don't use ModelAdmin get_queryset()

[Django]

#23055: Filters don't use ModelAdmin get_queryset()
-+-
 Reporter:  ramiro   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin filters| Triage Stage:  Accepted
  list_filter multi-db get_queryset  |  Needs documentation:  0
  modeladmin |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #23006: test.Client: provide os.environ with request.meta for consistency

[Django]

#23006: test.Client: provide os.environ with request.meta for consistency
---+--
 Reporter:  blueyed|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 What I found in a quick search: according to
 [http://legacy.python.org/dev/peps/pep-0333/#environ-variables PEP 333],
 "the environ dictionary may also contain arbitrary operating-system
 "environment variables" (it's a "may", not a "must").

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

Re: [Django] #23065: Migration Error when removing unique constraint

[Django]

#23065: Migration Error when removing unique constraint
+--
 Reporter:  anonymous   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-rc-1
 Severity:  Normal  |   Resolution:
 Keywords:  migrations  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by timo):

 I couldn't reproduce this (adding and removing a unique constraint. Does a
 unique constraint exist in the database? Maybe it has a different name?
 More details with steps to reproduce would be helpful.

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

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

Re: [Django] #23063: send email 1.6.5 OK, 1.7c1 malformed packet in wireshark

[Django]

#23063: send email 1.6.5 OK, 1.7c1 malformed packet in wireshark
-+-
 Reporter:  contact@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:
 Keywords:  send_mail, smtp, | Triage Stage:
  malformed, packet  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 Could you bisect to determine the commit that introduced the regression?

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

Re: [Django] #23060: UnicodeDecodeError in debug templatetag

[Django]

#23060: UnicodeDecodeError in debug templatetag
-+
 Reporter:  anonymous|Owner:  qingfeng
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+

Comment (by qingfeng):

 Replying to [comment:4 claudep]:
 > I left some comments on the pull request. Also tests are needed.

 OK, I added a test, this test in which directory is better? thanks

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

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

Re: [Django] #23060: UnicodeDecodeError in debug templatetag

[Django]

#23060: UnicodeDecodeError in debug templatetag
-+
 Reporter:  anonymous|Owner:  qingfeng
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+
Changes (by claudep):

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


Comment:

 I left some comments on the pull request. Also tests are needed.

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

Re: [Django] #23060: UnicodeDecodeError in debug templatetag

[Django]

#23060: UnicodeDecodeError in debug templatetag
-+
 Reporter:  anonymous|Owner:  qingfeng
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.7-rc-1
 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
-+

Comment (by qingfeng):

 pullrequest: https://github.com/django/django/pull/2933

 pls, review, thanks

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

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

Re: [Django] #23060: UnicodeDecodeError in debug templatetag

[Django]

#23060: UnicodeDecodeError in debug templatetag
-+
 Reporter:  anonymous|Owner:  qingfeng
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.7-rc-1
 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 qingfeng):

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


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

Re: [Django] #23064: GDAL 1.11 Support for Win

[Django]

#23064: GDAL 1.11 Support for Win
--+
 Reporter:  anonymous |Owner:  claudep
 Type:  Cleanup/optimization  |   Status:  closed
Component:  GIS   |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Claude Paroz ):

 In [changeset:"6e41ae1a4e924908fc07ef6b4ce28feb31c994fd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6e41ae1a4e924908fc07ef6b4ce28feb31c994fd"
 [1.7.x] Fixed #23064 -- Added lib detection support for GDAL 1.10/1.11

 Note that GDAL 1.11 is not yet officially supported, until someone
 has tested it and can confirm it has no issues with Django.
 Backport of 3f1412ff7b 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/067.b024b9a0c2963e4d8126af013785e4a3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 6e41ae: [1.7.x] Fixed #23064 -- Added lib detection suppor...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 6e41ae1a4e924908fc07ef6b4ce28feb31c994fd
  
https://github.com/django/django/commit/6e41ae1a4e924908fc07ef6b4ce28feb31c994fd
  Author: Claude Paroz 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/contrib/gis/gdal/libgdal.py
M docs/ref/contrib/gis/install/geolibs.txt

  Log Message:
  ---
  [1.7.x] Fixed #23064 -- Added lib detection support for GDAL 1.10/1.11

Note that GDAL 1.11 is not yet officially supported, until someone
has tested it and can confirm it has no issues with Django.
Backport of 3f1412ff7b 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/53cd48ff8b912_2a22fa5d3474844%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23064: GDAL 1.11 Support for Win

[Django]

#23064: GDAL 1.11 Support for Win
--+
 Reporter:  anonymous |Owner:  claudep
 Type:  Cleanup/optimization  |   Status:  closed
Component:  GIS   |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 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 Claude Paroz ):

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


Comment:

 In [changeset:"3f1412ff7bbfd7b1a15b7ed8c574ee8ba5aa6309"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3f1412ff7bbfd7b1a15b7ed8c574ee8ba5aa6309"
 Fixed #23064 -- Added lib detection support for GDAL 1.10/1.11

 Note that GDAL 1.11 is not yet officially supported, until someone
 has tested it and can confirm it has no issues with 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/067.826460482614c057747cf281b5c9454e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 3f1412: Fixed #23064 -- Added lib detection support for GD...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3f1412ff7bbfd7b1a15b7ed8c574ee8ba5aa6309
  
https://github.com/django/django/commit/3f1412ff7bbfd7b1a15b7ed8c574ee8ba5aa6309
  Author: Claude Paroz 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/contrib/gis/gdal/libgdal.py
M docs/ref/contrib/gis/install/geolibs.txt

  Log Message:
  ---
  Fixed #23064 -- Added lib detection support for GDAL 1.10/1.11

Note that GDAL 1.11 is not yet officially supported, until someone
has tested it and can confirm it has no issues with Django.


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

Re: [Django] #23064: GDAL 1.11 Support for Win

[Django]

#23064: GDAL 1.11 Support for Win
--+
 Reporter:  anonymous |Owner:  claudep
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  GIS   |  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 claudep):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => claudep
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #23065: Migration Error when removing unique constraint

[Django]

#23065: Migration Error when removing unique constraint
+--
 Reporter:  anonymous   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-rc-1
 Severity:  Normal  |   Resolution:
 Keywords:  migrations  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by anonymous):

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


Comment:

 Oh, i can probably say the model looked liek this,


 {{{
 class Permission(models.Model):
 sys_name = models.CharField(_('System Name'), unique = True,
 max_length = 20)
 name = models.CharField(_('Name'), unique = True, max_length = 50)

 def __unicode__(self):
 return self.name
 }}}

 I wanted to remove the unique constraint from name.

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

[Django] #23065: Migration Error when removing unique constraint

[Django]

#23065: Migration Error when removing unique constraint
+
 Reporter:  anonymous   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7-rc-1
 Severity:  Normal  |   Keywords:  migrations
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I try to make a migration which simple removes "unique = True" from a
 field. and get the error below.

 Note this is nothing to do with Django's standard auth module, but a
 custom implementation, as far as I can see that should have nothing to do
 with it.

 This is a private project so I can't give many more details than this. I'm
 using Postgres and the current 1.7 rc.

 {{{
 python manage.py makemigrations
 Migrations for 'Auth':
   0003_auto_20140721_1413.py:
 - Alter field name on permission
 (env)samuel || python manage.py migrate
 Operations to perform:
   Synchronize unmigrated apps: bootstrapform, django_jinja, admin_tools,
 theming, dashboard
   Apply all migrations: Schedule, admin, sessions, auth, contenttypes,
 Accounts, Auth, CRM
 Synchronizing apps without migrations:
   Creating tables...
   Installing custom SQL...
   Installing indexes...
 Running migrations:
   Applying Auth.0003_auto_20140721_1413...Traceback (most recent call
 last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 385, in
 execute_from_command_line
 utility.execute()
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 377, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 337, in execute
 output = self.handle(*args, **options)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/core/management/commands/migrate.py", line 160, in handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/db/migrations/executor.py", line 62, in migrate
 self.apply_migration(migration, fake=fake)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/db/migrations/executor.py", line 96, in apply_migration
 migration.apply(project_state, schema_editor)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/db/migrations/migration.py", line 107, in apply
 operation.database_forwards(self.app_label, schema_editor,
 project_state, new_state)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/db/migrations/operations/fields.py", line 131, in
 database_forwards
 schema_editor.alter_field(from_model, from_field, to_field)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/db/backends/schema.py", line 506, in alter_field
 self._alter_field(model, old_field, new_field, old_type, new_type,
 old_db_params, new_db_params, strict)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/db/backends/schema.py", line 525, in _alter_field
 "name": constraint_name,
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/db/backends/schema.py", line 98, in execute
 cursor.execute(sql, params)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 81, in execute
 return super(CursorDebugWrapper, self).execute(sql, params)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 65, in execute
 return self.cursor.execute(sql, params)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/db/utils.py", line 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/path/to/project/env/local/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 65, in execute
 return self.cursor.execute(sql, params)
 django.db.utils.ProgrammingError: constraint "auth_permission_name_key" of
 relation "Auth_permission" does not exist

 }}}

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

[Django] #23064: GDAL 1.11 Support for Win

[Django]

#23064: GDAL 1.11 Support for Win
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  GIS|Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 Support recent versions of GDAL (1.10 and 1.11) for win32 machines.  This
 can be done by adding "gdal110" and "gdal111" to line 25 on
 django/contrib/gis/gdal/libgdal.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/052.471ad2280a5247a9267fe2e10caff2e4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23063: send email 1.6.5 OK, 1.7c1 malformed packet in wireshark

[Django]

#23063: send email 1.6.5 OK, 1.7c1 malformed packet in wireshark
-+-
 Reporter:  contact@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:
 Keywords:  send_mail, smtp, | Triage Stage:
  malformed, packet  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

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

[Django] #23063: send email 1.6.5 OK, 1.7c1 malformed packet in wireshark

[Django]

#23063: send email 1.6.5 OK, 1.7c1 malformed packet in wireshark
--+
 Reporter:|  Owner:  nobody
  contact@…   | Status:  new
 Type:|Version:  1.7-rc-1
  Uncategorized   |   Keywords:  send_mail, smtp, malformed, packet
Component:  Core  |  Has patch:  0
  (Mail)  |  UI/UX:  0
 Severity:  Normal|
 Triage Stage:|
  Unreviewed  |
Easy pickings:  0 |
--+
 Hello,

 I'm working on a 1.7c1 application with Django, and my emails are not
 sent.

 My settings are:
 EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
 EMAIL_HOST = 'ns0.ovh.net'
 EMAIL_PORT = 587
 EMAIL_HOST_USER = #USER#
 EMAIL_HOST_PASSWORD = #PASSWORD#
 EMAIL_USE_SSL = False

 I tested my account with telnet, and smtplib, and everything goes smooth.

 The code I run:
 > mail.send_mail('susu', 'body body', from_email, [to_email])

 Under 1.6.5, the email is sent. Under wireshark, the data package is good.
 Under 1.7c1, the email is not sent. I open my wireshark, and look at the
 data packet. It shows that the packet is malformed.

 If I dump via filebased backend, there's no difference except the
 timestamp and message-id between the two versions.

 I copy you my packet dump from wireshark:
 http://wikisend.com/download/667092/wireshark_smtp_packet_1-6-5_good.txt
 http://wikisend.com/download/569376/wireshark_smtp_packet_1-7-1_bad.txt

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

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

Re: [Django] #23062: Document how to create initial superuser without syncdb command (was: how to create initial superuser without syncdb command)

[Django]

#23062: Document how to create initial superuser without syncdb command
--+
 Reporter:  manelclos@…   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7-rc-1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by erikr):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Documentation
 * needs_tests:   => 0
 * needs_docs:   => 1
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 This can (and could always) be done with `./manage.py createsuperuser`.
 Perhaps it would be useful to mention that fact in the appropriate place
 in the docs.

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

[Django] #23062: how to create initial superuser without syncdb command

[Django]

#23062: how to create initial superuser without syncdb command
---+--
 Reporter:  manelclos@…|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.7-rc-1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 Hi,

 In Django 1.7, after startproject, you will now run migrate, but this
 won't ask to create the superuser. Is there any new command / option
 planned? Saying migrate is an alias or the replacement for syncdb is
 confusing as it does not behaves in the same way.

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

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

Re: [Django] #23014: Renaming a field in a unique_together fails

[Django]

#23014: Renaming a field in a unique_together fails
-+
 Reporter:  melinath |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:  fixed
 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 Andrew Godwin ):

 In [changeset:"e2220c1c086675e5c3a87d2f09cb71e6562ad733"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e2220c1c086675e5c3a87d2f09cb71e6562ad733"
 [1.7.x] Fixed #23014: Renaming not atomic with unique together
 }}}

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

[django/django] e2220c: [1.7.x] Fixed #23014: Renaming not atomic with uni...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: e2220c1c086675e5c3a87d2f09cb71e6562ad733
  
https://github.com/django/django/commit/e2220c1c086675e5c3a87d2f09cb71e6562ad733
  Author: Andrew Godwin 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/db/backends/sqlite3/schema.py
M django/db/migrations/autodetector.py
M django/db/migrations/operations/fields.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  [1.7.x] Fixed #23014: Renaming not atomic with unique together


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

Re: [Django] #23014: Renaming a field in a unique_together fails

[Django]

#23014: Renaming a field in a unique_together fails
-+
 Reporter:  melinath |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:  fixed
 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 Andrew Godwin ):

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


Comment:

 In [changeset:"e24e9e0438cf3ba6c557558f68587d135a85e126"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e24e9e0438cf3ba6c557558f68587d135a85e126"
 Fixed #23014: Renaming not atomic with unique together
 }}}

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

[django/django] e24e9e: Fixed #23014: Renaming not atomic with unique toge...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e24e9e0438cf3ba6c557558f68587d135a85e126
  
https://github.com/django/django/commit/e24e9e0438cf3ba6c557558f68587d135a85e126
  Author: Andrew Godwin 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/db/backends/sqlite3/schema.py
M django/db/migrations/autodetector.py
M django/db/migrations/operations/fields.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  Fixed #23014: Renaming not atomic with unique together


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

Re: [Django] #23009: migrations may generate too long identifiers for the database

[Django]

#23009: migrations may generate too long identifiers for the database
-+
 Reporter:  twiggers |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:  fixed
 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 Andrew Godwin ):

 In [changeset:"88135a8cf7d587b88e47f1223cf01c7698b52b74"]:
 {{{
 #!CommitTicketReference repository=""
 revision="88135a8cf7d587b88e47f1223cf01c7698b52b74"
 [1.7.x] Fixed #23009: Shorten FK identifiers in add_field and make
 consistent
 }}}

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

[django/django] 88135a: [1.7.x] Fixed #23009: Shorten FK identifiers in ad...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 88135a8cf7d587b88e47f1223cf01c7698b52b74
  
https://github.com/django/django/commit/88135a8cf7d587b88e47f1223cf01c7698b52b74
  Author: Andrew Godwin 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/db/backends/schema.py
M tests/schema/models.py
M tests/schema/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #23009: Shorten FK identifiers in add_field and make consistent


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

Re: [Django] #23009: migrations may generate too long identifiers for the database

[Django]

#23009: migrations may generate too long identifiers for the database
-+
 Reporter:  twiggers |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:  fixed
 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 Andrew Godwin ):

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


Comment:

 In [changeset:"7dacc6ae4657ecc18bd92a94b50950871f914168"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7dacc6ae4657ecc18bd92a94b50950871f914168"
 Fixed #23009: Shorten FK identifiers in add_field and make consistent
 }}}

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

[django/django] 7dacc6: Fixed #23009: Shorten FK identifiers in add_field ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7dacc6ae4657ecc18bd92a94b50950871f914168
  
https://github.com/django/django/commit/7dacc6ae4657ecc18bd92a94b50950871f914168
  Author: Andrew Godwin 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/db/backends/schema.py
M tests/schema/models.py
M tests/schema/tests.py

  Log Message:
  ---
  Fixed #23009: Shorten FK identifiers in add_field and make consistent


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

Re: [Django] #22975: Cannot rename model keeping db table name

[Django]

#22975: Cannot rename model keeping db table name
-+
 Reporter:  rhcarvalho   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  migrations   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Andrew Godwin ):

 In [changeset:"f57e84392e9aea19f8f9dc31f1e5351de356ce34"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f57e84392e9aea19f8f9dc31f1e5351de356ce34"
 [1.7.x] Fixed #22975: Don't call rename SQL if not needed
 }}}

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

[django/django] dcb4ed: Fixed #22975: Don't call rename SQL if not needed

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: dcb4ed517082d13ccf7da9bd5d16c77bcecbf139
  
https://github.com/django/django/commit/dcb4ed517082d13ccf7da9bd5d16c77bcecbf139
  Author: Andrew Godwin 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/db/backends/schema.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  Fixed #22975: Don't call rename SQL if not needed


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

Re: [Django] #22975: Cannot rename model keeping db table name

[Django]

#22975: Cannot rename model keeping db table name
-+
 Reporter:  rhcarvalho   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  migrations   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"dcb4ed517082d13ccf7da9bd5d16c77bcecbf139"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dcb4ed517082d13ccf7da9bd5d16c77bcecbf139"
 Fixed #22975: Don't call rename SQL if not needed
 }}}

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

[django/django] f57e84: [1.7.x] Fixed #22975: Don't call rename SQL if not...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: f57e84392e9aea19f8f9dc31f1e5351de356ce34
  
https://github.com/django/django/commit/f57e84392e9aea19f8f9dc31f1e5351de356ce34
  Author: Andrew Godwin 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/db/backends/schema.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  [1.7.x] Fixed #22975: Don't call rename SQL if not needed


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

Re: [Django] #23039: Django 1.7.x test serialization on unmanaged models

[Django]

#23039: Django 1.7.x test serialization on unmanaged models
---+
 Reporter:  gvangool   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.7-rc-1
 Severity:  Release blocker|   Resolution:  fixed
 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 Andrew Godwin ):

 In [changeset:"ff8d715a0a62eb4d70e6c2bf38fa1113ed2899e5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ff8d715a0a62eb4d70e6c2bf38fa1113ed2899e5"
 [1.7.x] Fixed #23039: Don't try to serialize unmanaged models in tests
 }}}

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

Re: [Django] #23039: Django 1.7.x test serialization on unmanaged models

[Django]

#23039: Django 1.7.x test serialization on unmanaged models
---+
 Reporter:  gvangool   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.7-rc-1
 Severity:  Release blocker|   Resolution:  fixed
 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 Andrew Godwin ):

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


Comment:

 In [changeset:"2984b30ce84eccedfcc5b5241d12720913d0b80a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2984b30ce84eccedfcc5b5241d12720913d0b80a"
 Fixed #23039: Don't try to serialize unmanaged models in tests
 }}}

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

[django/django] ff8d71: [1.7.x] Fixed #23039: Don't try to serialize unman...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: ff8d715a0a62eb4d70e6c2bf38fa1113ed2899e5
  
https://github.com/django/django/commit/ff8d715a0a62eb4d70e6c2bf38fa1113ed2899e5
  Author: Andrew Godwin 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/db/backends/creation.py
M tests/migration_test_data_persistence/models.py

  Log Message:
  ---
  [1.7.x] Fixed #23039: Don't try to serialize unmanaged models in tests


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

[django/django] 2984b3: Fixed #23039: Don't try to serialize unmanaged mod...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2984b30ce84eccedfcc5b5241d12720913d0b80a
  
https://github.com/django/django/commit/2984b30ce84eccedfcc5b5241d12720913d0b80a
  Author: Andrew Godwin 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/db/backends/creation.py
M tests/migration_test_data_persistence/models.py

  Log Message:
  ---
  Fixed #23039: Don't try to serialize unmanaged models in tests


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

Re: [Django] #23043: Fix or document inconsistent handling of field defaults by migrations

[Django]

#23043: Fix or document inconsistent handling of field defaults by migrations
-+
 Reporter:  timo |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:  fixed
 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 Andrew Godwin ):

 In [changeset:"2fb1939a9efae24560d41fbb7f6a280a1d2e8d06"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2fb1939a9efae24560d41fbb7f6a280a1d2e8d06"
 [1.7.x] Fixed #23043: alter_field drops defaults too
 }}}

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

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

[django/django] 5875b8: Fixed #23043: alter_field drops defaults too

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5875b8d1bf709b54f91a143304826d57f2fd
  
https://github.com/django/django/commit/5875b8d1bf709b54f91a143304826d57f2fd
  Author: Andrew Godwin 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/db/backends/schema.py

  Log Message:
  ---
  Fixed #23043: alter_field drops defaults too


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

Re: [Django] #23043: Fix or document inconsistent handling of field defaults by migrations

[Django]

#23043: Fix or document inconsistent handling of field defaults by migrations
-+
 Reporter:  timo |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Release blocker  |   Resolution:  fixed
 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 Andrew Godwin ):

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


Comment:

 In [changeset:"5875b8d1bf709b54f91a143304826d57f2fd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5875b8d1bf709b54f91a143304826d57f2fd"
 Fixed #23043: alter_field drops defaults too
 }}}

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

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

[django/django] 2fb193: [1.7.x] Fixed #23043: alter_field drops defaults t...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 2fb1939a9efae24560d41fbb7f6a280a1d2e8d06
  
https://github.com/django/django/commit/2fb1939a9efae24560d41fbb7f6a280a1d2e8d06
  Author: Andrew Godwin 
  Date:   2014-07-21 (Mon, 21 Jul 2014)

  Changed paths:
M django/db/backends/schema.py

  Log Message:
  ---
  [1.7.x] Fixed #23043: alter_field drops defaults too


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

Re: [Django] #23060: UnicodeDecodeError in debug templatetag

[Django]

#23060: UnicodeDecodeError in debug templatetag
-+
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.7-rc-1
 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 claudep):

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


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

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

Re: [Django] #23028: Add unique_together support to inspectdb

[Django]

#23028: Add unique_together support to inspectdb
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"70c54a3694975c43a2e0e22c4a90c3cbe1eb54e4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="70c54a3694975c43a2e0e22c4a90c3cbe1eb54e4"
 Fixed #23028: Added unique_togther support to inspectdb.
 }}}

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