Re: [Django] #24070: Mention the topic of the tutorial parts beside them

[Django]

#24070: Mention the topic of the tutorial parts beside them
--+
 Reporter:  iambibhas |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
--+

Comment (by iambibhas):

 Clean and simple. I just added the nested list so that the parts
 hyperlinks were next to each other, and it was a tiny bit easier to
 navigate. But yeah, it took too much space. This looks good 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/067.812fac8bb036328da65871c896d15a7d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13165: Display edit link beside add button for ForeignKey fields in admin

[Django]

#13165: Display edit link beside add button for ForeignKey fields in admin
-+-
 Reporter:  DrMeers  |Owner:  charettes
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin foreign key| Triage Stage:  Accepted
  edit link  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by charettes):

 * needs_better_patch:  1 => 0


Comment:

 Added what was missing to ship with 1.8. Review would be greatly
 appreciated.

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

Re: [Django] #21281: Make override_settings act at class level when used as a TestCase decorator

[Django]

#21281: Make override_settings act at class level when used as a TestCase 
decorator
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  master
 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
--+

Comment (by tchaumeny):

 After some investigation, that seems to be a consequence of a duplicated
 `super(..., cls).setUpClass()` in `LiveServerTestCase`:
 
https://github.com/django/django/blob/52f0b2b62262743d5f935ddae29428e661b5d8ea/django/test/testcases.py#L1210
 and
 
https://github.com/django/django/blob/52f0b2b62262743d5f935ddae29428e661b5d8ea/django/test/testcases.py#L1258
 (looks like I introduced that)

 If I remove one of those lines, the test passes 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/067.43db54756b23788c1ec02b31ac27a4b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23749: Document how to get the database alias in migrations

[Django]

#23749: Document how to get the database alias in migrations
-+-
 Reporter:  alfredperlstein  |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  migrations dbrouter  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by MarkusH):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #15940: use strict mode with mysql

[Django]

#15940: use strict mode with mysql
-+-
 Reporter:  foxwhisper   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 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 morgo):

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

Re: [Django] #23749: Document how to get the database alias in migrations

[Django]

#23749: Document how to get the database alias in migrations
--+
 Reporter:  alfredperlstein   |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  migrations dbrouter   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by splbio):

 OK, it is pushed, Thank you Markus.

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

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

Re: [Django] #15940: use strict mode with mysql

[Django]

#15940: use strict mode with mysql
-+-
 Reporter:  foxwhisper   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 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
-+-

Comment (by morgo):

 I work on the MySQL team at Oracle.  We have been changing the defaults to
 be more strict over new releases.  Here is a summary of what has happened:

 - MySQL 5.6 (GA Feb 2013) enabled sql mode `STRICT_TRANS_TABLES` for new
 installations.  What this means is that all config files have this sql
 mode setting, but if a my.cnf file existing prior to installing, or a user
 moves the config file it won't be enabled.

 - MySQL 5.7 (in development) will enable `STRICT_TRANS_TABLES` and
 `ONLY_FULL_GROUP_BY` as compiled defaults.  The SQL modes
 `ERROR_FOR_DIVISION_BY_ZERO`, `NO_ZERO_DATE` and `NO_ZERO_IN_DATE` are
 also folded into the "STRICT" definition.  Thus STRICT is now more strict.
 To show an example from 5.7 DMR5:


 {{{
 CREATE TABLE test (a int unsigned);
 INSERT INTO test VALUES (-1);
 ERROR 1264 (22003): Out of range value for column 'a' at row 1
 insert into test values (0/0);
 ERROR 1365 (22012): Division by 0

 CREATE TABLE test2 (a varchar(10));
 INSERT INTO test2 VALUES ('abcdefghijklmnopqrstuvwxyz');
 ERROR 1406 (22001): Data too long for column 'a' at row 1

 CREATE TABLE test3 (a datetime);
 INSERT INTO test3 VALUES ('-00-00 00:00:00');
 ERROR 1292 (22007): Incorrect datetime value: '-00-00 00:00:00' for
 column 'a' at row 1
 }}}

 - Since MySQL 5.5 (Dec 2010) InnoDB is the default storage engine, so for
 most installs there shouldn't be a difference between strict all versus
 strict_trans''actional''.  Since a DML statement could modify multiple
 rows, and an sql violation could occur mid-modification on any row.
 Producing errors on non-transactional tables is always tricky, hence the
 ability to control these behaviors independently (STRICT for transactional
 tables versus ALL tables).

 Explicitly setting sql modes that Django is compatible with on connection
 sounds like a good idea to me.  Other projects (Wordpress, Drupal,
 Magento) are also doing this.

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

Re: [Django] #23749: Document how to get the database alias in migrations

[Django]

#23749: Document how to get the database alias in migrations
--+
 Reporter:  alfredperlstein   |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  migrations dbrouter   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by splbio):

 Oh, it applies, OK.  I'll push it shortly thank 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/073.0fafb18f127717021c4d9ce24b1456df%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23749: Document how to get the database alias in migrations

[Django]

#23749: Document how to get the database alias in migrations
--+
 Reporter:  alfredperlstein   |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  migrations dbrouter   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by splbio):

 Which version of the pull request was this made against?  It seems to be
 done against an older version and will not apply cleanly.

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

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

Re: [Django] #23749: Document how to get the database alias in migrations

[Django]

#23749: Document how to get the database alias in migrations
--+
 Reporter:  alfredperlstein   |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  migrations dbrouter   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by MarkusH):

 {{{#!diff
 diff --git a/docs/ref/schema-editor.txt b/docs/ref/schema-editor.txt
 index 54dd3bf..c503296 100644
 --- a/docs/ref/schema-editor.txt
 +++ b/docs/ref/schema-editor.txt
 @@ -158,9 +158,9 @@ below.

  .. attribute:: SchemaEditor.connection

 -A connection object to the database. A useful attribute of the
 -connection is ``alias`` which can be used to determine the name of
 -the database being accessed.
 +A connection object to the database. A useful attribute of the connection
 is
 +``alias`` which can be used to determine the name of the database being
 +accessed.

 -This in turn is useful when doing data migrations for
 -:ref:`migrations with multiple database backends `.
 +This in turn is useful when doing data migrations for :ref:`migrations
 with
 +multiple database backends `.
 diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
 index 746f4d2..a743bf2 100644
 --- a/docs/topics/migrations.txt
 +++ b/docs/topics/migrations.txt
 @@ -472,71 +472,72 @@ backwards will raise an exception.
  Data migrations and multiple databases
  ~~

 -One of the challenges that can be encountered is figuring out whether
 -or not to run a migration when using multiple databases.
 -
 -For example, you may want to **only** run a migration against a
 -particular database.
 -
 -In order to do that you can filter inside of your data migration
 -by looking at the ``schema_editor.connection.alias`` attribute.
 -However it is better to have your ``dbrouter`` leverage the same
 -``allow_migrate`` call by making the following method in your
 -router::
 -
 -class MyRouter(object):
 -
 -def allow_migrate(self, db, model):
 -# your typical migration code here
 -
 -def runpython_ok(self, apps, schema_editor, model):
 -db = schema_editor.connection.alias
 -if self.allow_migrate(db, model):
 -return True
 -return False
 -
 -Then to leverage this in your migrations, do the following::
 -
 -# -*- coding: utf-8 -*-
 -from __future__ import unicode_literals
 -
 -from django.db import models, migrations
 -from myappname.dbrouter import MyRouter
 -import sys
 -
 -def forwards(apps, schema_editor):
 -# only run this for the correct databases
 -MyModel = apps.get_model("myappname", "MyModel")
 -if not MyRouter().runpython_ok(apps, schema_editor, MyModel):
 -return
 -
 -"""
 -This is a global configuration model so there should be only
 -row.
 -Get the first one -or- create the initial one.
 -Only set the default ports if it has not been set by user
 -already.
 -"""
 -try:
 -my_model = MyModel.objects.order_by("-id").first()
 -except IndexError:
 -my_model = MyModel.objects.create()
 -if my_model.my_model_ports == "":
 -my_model.my_model_ports = "80, 8080, 3128"
 -my_model.save()
 -
 -def backwards(apps, schema_editor):
 -pass
 -
 -class Migration(migrations.Migration):
 -
 -dependencies = [
 -# Dependencies to other migrations
 -]
 -
 -operations = [
 -migrations.RunPython(forwards, backwards),
 -]
 +One of the challenges that can be encountered is figuring out whether or
 not to
 +run a migration when using multiple databases.
 +
 +For example, you may want to **only** run a migration against a
 particular
 +database.
 +
 +In order to do that you can check the connection alias inside a
 ``RunPython``
 +forwards and backwards operation by looking at the
 +``schema_editor.connection.alias`` attribute.
 +
 +# -*- coding: utf-8 -*-
 +from __future__ import unicode_literals
 +
 +from django.db import migrations
 +
 +def forwards(apps, schema_editor):
 +if not schema_editor.connection.alias == 'master-db':
 +return
 +# Your migration code goes here
 +
 +class 

Re: [Django] #24059: app_label not handled when set to the same project name in all the django app

[Django]

#24059: app_label not handled when set to the same project name in all the 
django
app
+--
 Reporter:  foxmask |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by foxmask):

 Replying to [comment:4 shaib]:
 > In the second paragraph in my previous comment I explained that once you
 set the model's app_label, Django treats it as if it belonged to the other
 app. Again: Your model with `app_label = 'foobar'` belongs to the `foobar`
 app, and the fact that it is defined in `foxmask/models.py` does not
 matter.
 >
 > If this is still not clear to you, as I said, please use Django's
 support channels.
 I tested with db_table and it's ok. Now I have another problem
 (OperationalError: no such table: xxx) , but with this current test case,
 the problem I have in production, is not here. So thanks at least for
 showing the path to the 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/065.2d1b570521d6f0cabb72ea7b76088f53%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24068: management commands' OutputWrapper adds newline wrapped inside style

[Django]

#24068: management commands' OutputWrapper adds newline wrapped inside style
-+-
 Reporter:  MarkusH  |Owner:  MarkusH
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Let's focus our efforts on #21429 instead. We can merge
 [https://github.com/django/django/pull/3823 PR 3823] to fix the particular
 problem.

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

Re: [Django] #24070: Mention the topic of the tutorial parts beside them

[Django]

#24070: Mention the topic of the tutorial parts beside them
--+
 Reporter:  iambibhas |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):

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


Comment:

 How about something a little less verbose like the attached?

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

Re: [Django] #24071: Error with sqlmigrate

[Django]

#24071: Error with sqlmigrate
+--
 Reporter:  djbug   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:  duplicate
 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 claudep):

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


Comment:

 Duplicate of #23909 (should be fixed very soon in 1.7.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/063.bbd517074da94df9078571c69f92ed2d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16526: Add a tutorial on caching

[Django]

#16526: Add a tutorial on caching
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

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


Comment:

 Fine with me.

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

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

Re: [Django] #16970: calling as_view of CBV in URLConf needs better documentation and examples

[Django]

#16970: calling as_view of CBV in URLConf needs better documentation and 
examples
---+
 Reporter:  pydanny|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.3
 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 timgraham):

 I don't think that ticket ended up adding any clarification regarding the
 issues presented here.

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

Re: [Django] #21281: Make override_settings act at class level when used as a TestCase decorator

[Django]

#21281: Make override_settings act at class level when used as a TestCase 
decorator
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  master
 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 timgraham):

 * status:  closed => new
 * has_patch:  1 => 0
 * resolution:  fixed =>
 * severity:  Normal => Release blocker
 * stage:  Ready for checkin => Accepted


Comment:

 I found a regression here that causes `override_settings()` to leak when
 used on a subclass test class. See
 `DateTimePickerShortcutsSeleniumFirefoxTests` in `admin_widgets` (we
 didn't notice it at the time because that's a selenium test which isn't
 run on Jenkins).

 Here's a simple test script which fails on the second test.
 {{{
 from unittest import TestCase
 from django.conf import settings
 from django.contrib.admin.tests import AdminSeleniumWebDriverTestCase
 from django.test import override_settings

 @override_settings(TIME_ZONE='Asia/Singapore')
 class Test(AdminSeleniumWebDriverTestCase):
 def test(self):
 assert True

 class Test2(TestCase):
 def test(self):
 self.assertEqual(settings.TIME_ZONE, "America/Chicago")
 }}}

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

Re: [Django] #23749: Document how to get the database alias in migrations

[Django]

#23749: Document how to get the database alias in migrations
--+
 Reporter:  alfredperlstein   |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  migrations dbrouter   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by splbio):

 Replying to [comment:18 MarkusH]:
 > Replying to [comment:17 claudep]:
 > > #23879 is somewhat related. See this POC branch:
 https://github.com/wrwrwr/django/compare/feature/always-test-gis-and-
 postgres
 >
 > TBH, I don't see any relation to the issue here. It's not about running
 on a specific vendor, it's about different databases, probably even of the
 same vendor.

 +1

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

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

Re: [Django] #16970: calling as_view of CBV in URLConf needs better documentation and examples

[Django]

#16970: calling as_view of CBV in URLConf needs better documentation and 
examples
---+
 Reporter:  pydanny|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.3
 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 iambibhas):

 * cc: me@… (added)


Comment:

 #16807 was fixed long time back. Is this ticket still relevant?

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

Re: [Django] #16526: Add a tutorial on caching

[Django]

#16526: Add a tutorial on caching
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.3
 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 iambibhas):

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

Re: [Django] #16526: Add a tutorial on caching

[Django]

#16526: Add a tutorial on caching
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.3
 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 iambibhas):

 3 years since this ticket was created. The
 [https://docs.djangoproject.com/en/1.7/topics/cache/ caching doc] is at a
 much better state now and is fairly introductory. I think we can skip
 having a separate tutorial for caching. Even if we create a tutorial under
 "Advanced Tutorials", we'd mostly be copy-pasting things from
 topics/cache. Don't think that's a good idea.

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

Re: [Django] #23749: Document how to get the database alias in migrations

[Django]

#23749: Document how to get the database alias in migrations
--+
 Reporter:  alfredperlstein   |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  migrations dbrouter   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by MarkusH):

 Replying to [comment:17 claudep]:
 > #23879 is somewhat related. See this POC branch:
 https://github.com/wrwrwr/django/compare/feature/always-test-gis-and-
 postgres

 TBH, I don't see any relation to the issue here. It's not about running on
 a specific vendor, it's about different databases, probably even of the
 same vendor.

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

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

Re: [Django] #23879: We should use test-skipping, not conditional discovery in runtests.py

[Django]

#23879: We should use test-skipping, not conditional discovery in runtests.py
--+
 Reporter:  carljm|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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 MarkusH):

 The general idea to have some vendor specifics in the migration code base
 sounds good. But I have to agree with Carl on the problems that arise from
 not loading a migration. I think the skipping of vendor miss-matches
 should happen during the actual migrate process. This still allows
 dependency resolutions and state changes independent from the vendor.

 Moving the vendor part into operations would furthermore give us some
 flexibility for advanced database features. E.g. once `contrib.postgres`
 got support for views, these views could be generated within the same
 migration, one operation could be
 `django.contrib.postgres.operations.CreateView` (with a PostgreSQL vendor
 marker) while a `RunSQL` operation would run everywhere but on PostgreSQL.

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

Re: [Django] #23749: Document how to get the database alias in migrations

[Django]

#23749: Document how to get the database alias in migrations
--+
 Reporter:  alfredperlstein   |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  migrations dbrouter   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by claudep):

 #23879 is somewhat related. See this POC branch:
 https://github.com/wrwrwr/django/compare/feature/always-test-gis-and-
 postgres

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

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

[Django] #24071: Error with sqlmigrate

[Django]

#24071: Error with sqlmigrate
+
 Reporter:  djbug   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I have an app where I create a simple table and then add a partial index
 directly in SQL using RunSQL & migrations. I get an error with
 `sqlmigrate` when I use it on a custom migration.

 The command is : `manage.py sqlmigrate myapp 0002_custom.py`

 0002_custom.py files looks like this:



 {{{
 class Migration(migrations.Migration):

 dependencies = [
 ('myapp', '0001_initial'),
 ]

 operations = [
 migrations.RunSQL(
 sql = 'CREATE UNIQUE INDEX test_idx ON book (name,
 publisher_id) WHERE publisher_id IS NOT NULL;',
 )
 ]

 }}}

 Here's the error:

 {{{
 (django1_7) C:\djangoproject>python manage.py sqlmigrate myapp 0002

 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "C:\virtualenv\django1_7\lib\site-
 packages\django\core\management\__init__.py", line 385, in
 execute_from_command_line
 utility.execute()
   File "C:\virtualenv\django1_7\lib\site-
 packages\django\core\management\__init__.py", line 377, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "C:\virtualenv\django1_7\lib\site-
 packages\django\core\management\base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "C:\virtualenv\django1_7\lib\site-
 packages\django\core\management\commands\sqlmigrate.py", line 30, in
 execute
 return super(Command, self).execute(*args, **options)
   File "C:\virtualenv\django1_7\lib\site-
 packages\django\core\management\base.py", line 338, in execute
 output = self.handle(*args, **options)
   File "C:\virtualenv\django1_7\lib\site-
 packages\django\core\management\commands\sqlmigrate.py", line 61, in
 handle
 sql_statements = executor.collect_sql(plan)
   File "C:\virtualenv\django1_7\lib\site-
 packages\django\db\migrations\executor.py", line 77, in collect_sql
 migration.apply(project_state, schema_editor, collect_sql=True)
   File "C:\virtualenv\django1_7\lib\site-
 packages\django\db\migrations\migration.py", line 107, in apply
 operation.database_forwards(self.app_label, schema_editor,
 project_state, new_state)
   File "C:\virtualenv\django1_7\lib\site-
 packages\django\db\migrations\operations\special.py", line 69, in
 database_forwards
 schema_editor.execute(statement, params=None)
   File "C:\virtualenv\django1_7\lib\site-
 packages\django\db\backends\schema.py", line 96, in execute
 self.collected_sql.append((sql % tuple(map(self.quote_value, params)))
 + ";")
 TypeError: argument 2 to map() must support iteration

 }}}

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

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

[Django] #24070: Mention the topic of the tutorial parts beside them

[Django]

#24070: Mention the topic of the tutorial parts beside them
---+
 Reporter:  iambibhas  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 Right now the tutorial parts are mention on the front page like this -

 > Tutorial: Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6

 Given that I have gone through them once, I'm still not sure which one of
 them is the part that talks about writing views, or using the template
 system. I think it'd be helpful to mention beside that part numbers what
 they talk about.

 This could be an issue between encouraging new users to jump between parts
 and the convenience to find a certain topic. We could try to find a middle
 ground. The only time a user needs to go through those parts sequentially
 is the very first time. After that they may choose to jump between parts.
 We could choose to make it easier in that case.

 I'm attaching a patch to show what we could mention.

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

Re: [Django] #23940: Disallow/warn on fields named exact

[Django]

#23940: Disallow/warn on fields named exact
-+-
 Reporter:  zhiyajun11   |Owner:  nicwest
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by nicwest):

 I created a pull request here: https://github.com/django/django/pull/3831

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

Re: [Django] #23861: Fields referenced in migrations cannot be (re)moved, even if migrations have been squashed

[Django]

#23861: Fields referenced in migrations cannot be (re)moved, even if migrations
have been squashed
-+-
 Reporter:  spookylukey  |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => assigned
 * owner:  nobody => timgraham
 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 [https://github.com/django/django/pull/3832 PR] with work in progress.
 Tests to come.

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

Re: [Django] #23940: Disallow/warn on fields named exact

[Django]

#23940: Disallow/warn on fields named exact
-+-
 Reporter:  zhiyajun11   |Owner:  nicwest
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by nicwest):

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

Re: [Django] #24064: Spatialite tests could use or create real database

[Django]

#24064: Spatialite tests could use or create real database
-+-
 Reporter:  coldmind |Owner:  coldmind
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"839f431ef5b927c8b07ce33483b3a7b0dd17b761"]:
 {{{
 #!CommitTicketReference repository=""
 revision="839f431ef5b927c8b07ce33483b3a7b0dd17b761"
 Fixed #24064 -- Prevented database access at compile time in spatialite
 models.
 }}}

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

Re: [Django] #9104: FieldDoesNotExist is defined in "confusing" place.

[Django]

#9104: FieldDoesNotExist is defined in "confusing" place.
-+-
 Reporter:  telenieko|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Design
 |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"8958170755b37ce346ae5257c1000bd936faa3b0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8958170755b37ce346ae5257c1000bd936faa3b0"
 Fixed #9104 -- Moved FieldDoesNotExist to core.exceptions
 }}}

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

Re: [Django] #14834: Colour issues in CSS - particularly documentation

[Django]

#14834: Colour issues in CSS - particularly documentation
---+-
 Reporter:  cogat  |Owner:  cogat
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.2
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  sprintdec2010  | 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):

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


Comment:

 After the redesign this is superseded by
 https://github.com/django/djangoproject.com/issues/198 and tickets in that
 tracker.

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

Re: [Django] #23745: Migrations migrate is slow

[Django]

#23745: Migrations migrate is slow
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"a159b1facd222c20dde12f1e0117643af528d511"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a159b1facd222c20dde12f1e0117643af528d511"
 Replaced migration state render() by apps cached property

 Refs #23745.
 }}}

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

Re: [Django] #23745: Migrations migrate is slow

[Django]

#23745: Migrations migrate is slow
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"1aa3e09c2043c88a760e8b73fb95dc8f1ffef50e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1aa3e09c2043c88a760e8b73fb95dc8f1ffef50e"
 Fixed #23745 -- Reused states as much as possible in migrations

 Thanks Tim Graham and Markus Holtermann for the reviews.
 }}}

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

Re: [Django] #23745: Migrations migrate is slow

[Django]

#23745: Migrations migrate is slow
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"2a9c4b4901d385f68a2c3f9cf98b7a776c2976f0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2a9c4b4901d385f68a2c3f9cf98b7a776c2976f0"
 Passed around the state between migrations

 Refs #23745.
 }}}

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

Re: [Django] #23745: Migrations migrate is slow

[Django]

#23745: Migrations migrate is slow
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"057305e588ac90474fef47e2fb2890552a543731"]:
 {{{
 #!CommitTicketReference repository=""
 revision="057305e588ac90474fef47e2fb2890552a543731"
 Added ignore_swappable to StateApps

 Refs #23745.
 }}}

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

Re: [Django] #23749: Document how to get the database alias in migrations

[Django]

#23749: Document how to get the database alias in migrations
--+
 Reporter:  alfredperlstein   |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  migrations dbrouter   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #23919: Cleanups for when we drop Python 2 compatibility

[Django]

#23919: Cleanups for when we drop Python 2 compatibility
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by timgraham:

Old description:

> This is a tracking ticket of things that we can remove when we drop
> Python 2 compatibility (in a few years or so). Please edit the
> description of the ticket as you come across new items.
>
> * `django.dispatch.weakref_backports`
> * `django.utils.2to3_fixes`
> * `django.utils.lru_cache`
> * `django.utils.html_parser.use_workaround`
> * `django.utils.decorators.ContextDecorator`
> * `django.utils.six`
> * Change `inspect.getargspec()` (deprecated since 3.0) to
> `inspect.getfullargspec()`
> * `@python_2_unicode_compatible`
> * `from __future__ import unicode_literals`
> * Lots of workarounds in `django.http.cookie`
> * `str()` stuff for environment variables, e.g.
> 0bfb53866199f366ed140d49938fd185e5898156
> * `django.core.mail.message.make_msgid()` #23905
> * Functions in `django.utils.http` like `urlquote_plus` -- I think the
> versions of these functions on Python 3 don't have the unicode characters
> bug we are working around.

New description:

 This is a tracking ticket of things that we can remove when we drop Python
 2 compatibility (in a few years or so). Please edit the description of the
 ticket as you come across new items.

 * `django.dispatch.weakref_backports`
 * `django.utils.2to3_fixes`
 * `django.utils.lru_cache`
 * `django.utils.html_parser.use_workaround`
 * `django.utils.decorators.ContextDecorator`
 * `django.utils.six`
 * Change `inspect.getargspec()` (deprecated since 3.0) to
 `inspect.getfullargspec()`
 * `@python_2_unicode_compatible`
 * `from __future__ import unicode_literals`
 * Lots of workarounds in `django.http.cookie`
 * `str()` stuff for environment variables, e.g.
 0bfb53866199f366ed140d49938fd185e5898156
 * `django.core.mail.message.make_msgid()` #23905
 * Functions in `django.utils.http` like `urlquote_plus` -- I think the
 versions of these functions on Python 3 don't have the unicode characters
 bug we are working around.
 * Inheriting from `object` in `django.core.servers.basehttp` (and perhaps
 other places) ala 4ee06ec3fc8e94d164afbd2f9c880c60c658a9ac

--

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

Re: [Django] #24069: Regression in ServerHandler.handler_error

[Django]

#24069: Regression in ServerHandler.handler_error
--+
 Reporter:  pelme |Owner:  pelme
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"4ee06ec3fc8e94d164afbd2f9c880c60c658a9ac"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4ee06ec3fc8e94d164afbd2f9c880c60c658a9ac"
 Fixed #24069 -- Made ServerHandler a new style class to fix super() call.
 }}}

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

Re: [Django] #24069: Regression in ServerHandler.handler_error

[Django]

#24069: Regression in ServerHandler.handler_error
--+
 Reporter:  pelme |Owner:  pelme
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  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 claudep):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #22341: Split django.db.models.fields.related into multiple modules.

[Django]

#22341: Split django.db.models.fields.related into multiple modules.
-+-
 Reporter:  loic84   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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):

 * keywords:  1.8-alpha =>
 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 from Loic on the PR: "I think we are going to postpone this refactor some
 more."

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

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

Re: [Django] #24064: Spatialite tests could use or create real database

[Django]

#24064: Spatialite tests could use or create real database
-+-
 Reporter:  coldmind |Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Release blocker  |   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 coldmind):

 * needs_better_patch:  1 => 0


Comment:

 Tests are passing now, please review

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

Re: [Django] #24031: Implement a Case/When expression

[Django]

#24031: Implement a Case/When expression
-+-
 Reporter:  jarshwah |Owner:  michalmo
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  1.8-alpha| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by michalmo):

 * cc: michal.modzelewski@… (added)
 * owner:  nobody => michalmo
 * 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/066.b12bf0c2c4a511962087710d82aa0a31%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12663: Formalize, refactor, and document Model._meta

[Django]

#12663: Formalize, refactor, and document Model._meta
-+-
 Reporter:  MadeR|Owner:  pirosb3
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  1.8-alpha| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by collinanderson):

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

Re: [Django] #24031: Implement a Case/When expression

[Django]

#24031: Implement a Case/When expression
-+-
 Reporter:  jarshwah |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  1.8-alpha| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jarshwah):

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


Comment:

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

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

Re: [Django] #24069: Regression in ServerHandler.handler_error

[Django]

#24069: Regression in ServerHandler.handler_error
--+--
 Reporter:  pelme |Owner:  pelme
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by pelme):

 For reference, here is a traceback where this fails:

 The `TestLiveServer.test_serve_static_dj17_without_staticfiles_app`
 failure from https://travis-ci.org/pytest-dev/pytest-django/jobs/45674534
 shows this error in action. It is obscured by the exception munging that
 is done within `simple_server`, though.

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

Re: [Django] #24069: Regression in ServerHandler.handler_error

[Django]

#24069: Regression in ServerHandler.handler_error
--+--
 Reporter:  pelme |Owner:  pelme
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by pelme):

 Here is a PR that makes ServerHandler a new style class which fixes the
 issue:

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

 I am not sure how this can be tested. It is hard to test this since
 simple_server does some very nasty error handling (`except:` in a bunch of
 places and relies on `sys.exc_info`).

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

Re: [Django] #24069: Regression in ServerHandler.handler_error

[Django]

#24069: Regression in ServerHandler.handler_error
--+--
 Reporter:  pelme |Owner:  pelme
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by pelme):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => pelme
 * needs_docs:   => 0


Old description:

> 9253042d53d61b23b3f727a00c41e8089be73836 which # - silence broken
> pipe errors introduced a regression in the error handling on Python 2.x.
>
> In Python 2.x, `simple_server.ServerHandler` is and old style class. This
> makes it an error using super() to access the super class.
>
> The solution is simple: explicitly call
> `simple_server.ServerHandler.handle_error()`.

New description:

 9253042d53d61b23b3f727a00c41e8089be73836 which # - silence broken pipe
 errors introduced a regression in the error handling on Python 2.x.

 In Python 2.x, `simple_server.ServerHandler` is and old style class. This
 makes it an error using super() to access the super class.

 The solution is simple: explicitly call
 `simple_server.ServerHandler.handle_error()` or inherit from object.

--

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

[Django] #24069: Regression in ServerHandler.handler_error

[Django]

#24069: Regression in ServerHandler.handler_error
--+
 Reporter:  pelme |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Other)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 9253042d53d61b23b3f727a00c41e8089be73836 which # - silence broken pipe
 errors introduced a regression in the error handling on Python 2.x.

 In Python 2.x, `simple_server.ServerHandler` is and old style class. This
 makes it an error using super() to access the super class.

 The solution is simple: explicitly call
 `simple_server.ServerHandler.handle_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/048.0433d509219382e3124ee9b1fc671736%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23749: Document how to get the database alias in migrations

[Django]

#23749: Document how to get the database alias in migrations
--+
 Reporter:  alfredperlstein   |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  migrations dbrouter   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by MarkusH):

 * has_patch:  0 => 1


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

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

Re: [Django] #9104: FieldDoesNotExist is defined in "confusing" place.

[Django]

#9104: FieldDoesNotExist is defined in "confusing" place.
-+-
 Reporter:  telenieko|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
 |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 Of course, my "trick" about a `FieldDoesNotExist.py` file only works if we
 want to loudly fail with an explicit message. Still looking for a way to
 raise a warning without ever calling the symbol (might be impossible...).

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

Re: [Django] #9104: FieldDoesNotExist is defined in "confusing" place.

[Django]

#9104: FieldDoesNotExist is defined in "confusing" place.
-+-
 Reporter:  telenieko|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
 |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 Even if it is not documented, searching for `FieldDoesNotExist` on github
 for example reveals many usages of this import location in the wild, hence
 I think we should provide some deprecation path.

 It should be possible for example to create a
 `django/db/models/fields/FieldDoesNotExist.py` module to trigger the
 deprecation warning on old import location (don't know if there is a
 cleaner way to deprecate import locations).

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

Re: [Django] #24030: default id field not migrated correctly

[Django]

#24030: default id field not migrated correctly
+
 Reporter:  brian   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   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 claudep):

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


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

Re: [Django] #24066: Django 1.6 Postgis 2.x detection broken

[Django]

#24066: Django 1.6 Postgis 2.x detection broken
---+--
 Reporter:  Matthias84 |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  GIS|  Version:  1.6
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  postgis detection  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by claudep):

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


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

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