Re: [Django] #22415: Migrate problems concerning foreignkeys to self

[Django]

#22415: Migrate problems concerning foreignkeys to self
---+---
 Reporter:  roughdesignapps@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.7-alpha-2
 Severity:  Normal |   Resolution:  needsinfo
 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 loic84):

 roughdesignapps@ when you use `python manage.py makemigrations `
 everything works as excepted?

 `python manage.py makemigrations` deliberately ignore any app that doesn't
 have a `migrations` directory, this is because using the migration
 framework is optional. To start using migrations with a given app, you
 indeed need to use `python manage.py makemigrations `, or you can
 manually create an empty `migrations` directory in your app before running
 `python manage.py makemigrations`.

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

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

Re: [Django] #22419: typofix for multi-db.txt

[Django]

#22419: typofix for multi-db.txt
---+--
 Reporter:  schmiddy@… |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"593e72c141f52b9f581b65314f421d70c6abde02"]:
 {{{
 #!CommitTicketReference repository=""
 revision="593e72c141f52b9f581b65314f421d70c6abde02"
 [1.7.x] Fixed #22419 -- Typo in docs/topics/db/multi-db.txt.

 Thanks Josh Kupershmidt.

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

Re: [Django] #22419: typofix for multi-db.txt

[Django]

#22419: typofix for multi-db.txt
---+--
 Reporter:  schmiddy@… |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"5b2d17d910d84e26ef229f0379bce66979f97e07"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5b2d17d910d84e26ef229f0379bce66979f97e07"
 [1.5.x] Fixed #22419 -- Typo in docs/topics/db/multi-db.txt.

 Thanks Josh Kupershmidt.

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

Re: [Django] #22419: typofix for multi-db.txt

[Django]

#22419: typofix for multi-db.txt
---+--
 Reporter:  schmiddy@… |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"d501c79f7b1635a01af13e094da47ac19c4365be"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d501c79f7b1635a01af13e094da47ac19c4365be"
 [1.6.x] Fixed #22419 -- Typo in docs/topics/db/multi-db.txt.

 Thanks Josh Kupershmidt.

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

[django/django] d501c7: [1.6.x] Fixed #22419 -- Typo in docs/topics/db/mul...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: d501c79f7b1635a01af13e094da47ac19c4365be
  
https://github.com/django/django/commit/d501c79f7b1635a01af13e094da47ac19c4365be
  Author: Tim Graham 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M docs/topics/db/multi-db.txt

  Log Message:
  ---
  [1.6.x] Fixed #22419 -- Typo in docs/topics/db/multi-db.txt.

Thanks Josh Kupershmidt.

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

[django/django] 5b2d17: [1.5.x] Fixed #22419 -- Typo in docs/topics/db/mul...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 5b2d17d910d84e26ef229f0379bce66979f97e07
  
https://github.com/django/django/commit/5b2d17d910d84e26ef229f0379bce66979f97e07
  Author: Tim Graham 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M docs/topics/db/multi-db.txt

  Log Message:
  ---
  [1.5.x] Fixed #22419 -- Typo in docs/topics/db/multi-db.txt.

Thanks Josh Kupershmidt.

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

[django/django] c487b1: Fixed #22419 -- Typo in docs/topics/db/multi-db.tx...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c487b1e2308968b659c2509e5dd40e56ebe4e63b
  
https://github.com/django/django/commit/c487b1e2308968b659c2509e5dd40e56ebe4e63b
  Author: Tim Graham 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M docs/topics/db/multi-db.txt

  Log Message:
  ---
  Fixed #22419 -- Typo in docs/topics/db/multi-db.txt.

Thanks Josh Kupershmidt.


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

[django/django] 593e72: [1.7.x] Fixed #22419 -- Typo in docs/topics/db/mul...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 593e72c141f52b9f581b65314f421d70c6abde02
  
https://github.com/django/django/commit/593e72c141f52b9f581b65314f421d70c6abde02
  Author: Tim Graham 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M docs/topics/db/multi-db.txt

  Log Message:
  ---
  [1.7.x] Fixed #22419 -- Typo in docs/topics/db/multi-db.txt.

Thanks Josh Kupershmidt.

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

Re: [Django] #22419: typofix for multi-db.txt

[Django]

#22419: typofix for multi-db.txt
---+--
 Reporter:  schmiddy@… |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"c487b1e2308968b659c2509e5dd40e56ebe4e63b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c487b1e2308968b659c2509e5dd40e56ebe4e63b"
 Fixed #22419 -- Typo in docs/topics/db/multi-db.txt.

 Thanks Josh Kupershmidt.
 }}}

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

Re: [Django] #22415: Migrate problems concerning foreignkeys to self

[Django]

#22415: Migrate problems concerning foreignkeys to self
---+---
 Reporter:  roughdesignapps@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.7-alpha-2
 Severity:  Normal |   Resolution:  needsinfo
 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 roughdesignapps@…):

 I update django to master and removed {{{app_label}}}.
 It still does not find any changes.

 A model sample:
 {{{
 class LegalDocumentSet(models.Model):

 objects = DocumentManager()
 country = models.ForeignKey(Country)
 country.help_text = "The country for which the documents are."
 published = models.BooleanField(default=False)
 published.help_text = """If the document is not published,
 it will not be shown on the website."""
 imprint = models.TextField()
 terms_and_conditions = models.TextField()
 cancellation_policy = models.TextField()

 def __str__(self):
 "@rtype:   str"
 return str(self.country)

 }}}
 With {{{DocumentManager}}} being a simple subclass of models.Manager with
 only one method 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/083.6c782335d65cf0cbf8e3f25c929c4bb1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22051: Running `makemigrations` twice in a row fails

[Django]

#22051: Running `makemigrations` twice in a row fails
-+
 Reporter:  bmispelon|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  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 andrewgodwin):

 * status:  closed => new
 * 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/067.d1ad6e01669d1972ce66d693f635cd06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22415: Migrate problems concerning foreignkeys to self

[Django]

#22415: Migrate problems concerning foreignkeys to self
---+---
 Reporter:  roughdesignapps@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.7-alpha-2
 Severity:  Normal |   Resolution:  needsinfo
 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 loic84):

 Sorry I've added an extra hyphen, it should be `python -Wall`, it tells
 python to print all warnings, most notably `PendingDeprecationWarning`
 which are normally silenced.

 Can you double check that the package name of your app is `foodapp`? Also
 you may want to try commenting out the `app_label = 'foodapp'` line, if I
 remember well a recent commit made it unnecessary for submodules of the
 `models` package.

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

Re: [Django] #21202: Atomic masks fatal database errors and instead propagates "connection already closed"

[Django]

#21202: Atomic masks fatal database errors and instead propagates "connection
already closed"
-+-
 Reporter:  intgr|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.6-beta-1
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"2ad0bc132a6f70a128d8e1fec689c6a474ddde89"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2ad0bc132a6f70a128d8e1fec689c6a474ddde89"
 [1.7.x] Fixed #21202 -- Maintained atomicity when the server disconnects.

 Thanks intgr for the report.

 This commit doesn't include a test because I don't know how to emulate a
 database disconnection in a cross-database compatible way.

 Also simplified a 'backends' test that was constrained by this problem.

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

Re: [Django] #21239: Closing connection inside atomic block breaks atomicity

[Django]

#21239: Closing connection inside atomic block breaks atomicity
-+-
 Reporter:  marcin@… |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  atomic close |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"2e42c859da42a871244aca36162a0aad2b63c02b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2e42c859da42a871244aca36162a0aad2b63c02b"
 [1.7.x] Fixed #21239 -- Maintained atomicity when closing the connection.

 Refs #15802 -- Reverted #7c657b24 as BaseDatabaseWrapper.close() now
 has a proper "finally" clause that may need to preserve self.connection.

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

Re: [Django] #22291: transactions.atomic (with savepoints) doesn't work correctly with deadlocks in mysql

[Django]

#22291: transactions.atomic (with savepoints) doesn't work correctly with 
deadlocks
in mysql
-+-
 Reporter:  err  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 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
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"1bcc8eb0f64831b24c2769e033a10e530c8ed140"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1bcc8eb0f64831b24c2769e033a10e530c8ed140"
 [1.7.x] Increased robustness of 58161e4e. Refs #22291.

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

Re: [Django] #22321: Missing DB errors wrapping around _set_autocommit

[Django]

#22321: Missing DB errors wrapping around _set_autocommit
-+-
 Reporter:  alexkoshelev |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"5f22bda3827f32289793b90a387d8c77d602a859"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5f22bda3827f32289793b90a387d8c77d602a859"
 [1.7.x] Fixed #22321 -- Wrapped exceptions in _set_autocommit.

 Refs #21202.

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

Re: [Django] #22291: transactions.atomic (with savepoints) doesn't work correctly with deadlocks in mysql

[Django]

#22291: transactions.atomic (with savepoints) doesn't work correctly with 
deadlocks
in mysql
-+-
 Reporter:  err  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 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
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"7e89434084d7952d107aef1c41f2019a73310634"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7e89434084d7952d107aef1c41f2019a73310634"
 [1.7.x] Fixed #22291 -- Avoided shadowing deadlock exceptions on MySQL.

 Thanks err for the report.

 Backport of 58161e4e 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/061.e8197da63e1462c637db71b4abcec614%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 7e8943: [1.7.x] Fixed #22291 -- Avoided shadowing deadlock...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 7e89434084d7952d107aef1c41f2019a73310634
  
https://github.com/django/django/commit/7e89434084d7952d107aef1c41f2019a73310634
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/transaction.py
M tests/transactions/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22291 -- Avoided shadowing deadlock exceptions on MySQL.

Thanks err for the report.

Backport of 58161e4e from master.


  Commit: 5f22bda3827f32289793b90a387d8c77d602a859
  
https://github.com/django/django/commit/5f22bda3827f32289793b90a387d8c77d602a859
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/backends/mysql/base.py
M django/db/backends/oracle/base.py
M django/db/backends/postgresql_psycopg2/base.py
M django/db/backends/sqlite3/base.py

  Log Message:
  ---
  [1.7.x] Fixed #22321 -- Wrapped exceptions in _set_autocommit.

Refs #21202.

Backport of 3becac84 from master


  Commit: 2e42c859da42a871244aca36162a0aad2b63c02b
  
https://github.com/django/django/commit/2e42c859da42a871244aca36162a0aad2b63c02b
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/backends/__init__.py
M django/db/backends/postgresql_psycopg2/base.py
M django/db/transaction.py
M tests/transactions/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #21239 -- Maintained atomicity when closing the connection.

Refs #15802 -- Reverted #7c657b24 as BaseDatabaseWrapper.close() now
has a proper "finally" clause that may need to preserve self.connection.

Backport of 25860096 from master.


  Commit: 2ad0bc132a6f70a128d8e1fec689c6a474ddde89
  
https://github.com/django/django/commit/2ad0bc132a6f70a128d8e1fec689c6a474ddde89
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/transaction.py
M tests/backends/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #21202 -- Maintained atomicity when the server disconnects.

Thanks intgr for the report.

This commit doesn't include a test because I don't know how to emulate a
database disconnection in a cross-database compatible way.

Also simplified a 'backends' test that was constrained by this problem.

Backport of 81761508 from master


  Commit: 1bcc8eb0f64831b24c2769e033a10e530c8ed140
  
https://github.com/django/django/commit/1bcc8eb0f64831b24c2769e033a10e530c8ed140
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/transaction.py

  Log Message:
  ---
  [1.7.x] Increased robustness of 58161e4e. Refs #22291.

Backport of ee837b9a from master


Compare: https://github.com/django/django/compare/ae78227de374...1bcc8eb0f648

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

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

[Django]

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

Comment (by Aymeric Augustin ):

 In [changeset:"2e42c859da42a871244aca36162a0aad2b63c02b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2e42c859da42a871244aca36162a0aad2b63c02b"
 [1.7.x] Fixed #21239 -- Maintained atomicity when closing the connection.

 Refs #15802 -- Reverted #7c657b24 as BaseDatabaseWrapper.close() now
 has a proper "finally" clause that may need to preserve self.connection.

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

Re: [Django] #21202: Atomic masks fatal database errors and instead propagates "connection already closed"

[Django]

#21202: Atomic masks fatal database errors and instead propagates "connection
already closed"
-+-
 Reporter:  intgr|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.6-beta-1
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"5f22bda3827f32289793b90a387d8c77d602a859"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5f22bda3827f32289793b90a387d8c77d602a859"
 [1.7.x] Fixed #22321 -- Wrapped exceptions in _set_autocommit.

 Refs #21202.

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

Re: [Django] #22321: Missing DB errors wrapping around _set_autocommit

[Django]

#22321: Missing DB errors wrapping around _set_autocommit
-+-
 Reporter:  alexkoshelev |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"746cded010c7ba3e2bf2df4cde32dcc9b75cb0d3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="746cded010c7ba3e2bf2df4cde32dcc9b75cb0d3"
 [1.6.x] Fixed #22321 -- Wrapped exceptions in _set_autocommit.

 Refs #21202.

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

Re: [Django] #21202: Atomic masks fatal database errors and instead propagates "connection already closed"

[Django]

#21202: Atomic masks fatal database errors and instead propagates "connection
already closed"
-+-
 Reporter:  intgr|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.6-beta-1
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"1d3d2b9a2458cbf11b7e828fb59b3f2cb73d14fe"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1d3d2b9a2458cbf11b7e828fb59b3f2cb73d14fe"
 [1.6.x] Fixed #21202 -- Maintained atomicity when the server disconnects.

 Thanks intgr for the report.

 This commit doesn't include a test because I don't know how to emulate a
 database disconnection in a cross-database compatible way.

 Also simplified a 'backends' test that was constrained by this problem.

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

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

[Django]

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

Comment (by Aymeric Augustin ):

 In [changeset:"4ea02bdb0dc6776fc29d8164e417469c9ba10f18"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4ea02bdb0dc6776fc29d8164e417469c9ba10f18"
 [1.6.x] Fixed #21239 -- Maintained atomicity when closing the connection.

 Refs #15802 -- Reverted #7c657b24 as BaseDatabaseWrapper.close() now
 has a proper "finally" clause that may need to preserve self.connection.

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

Re: [Django] #21202: Atomic masks fatal database errors and instead propagates "connection already closed"

[Django]

#21202: Atomic masks fatal database errors and instead propagates "connection
already closed"
-+-
 Reporter:  intgr|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.6-beta-1
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"746cded010c7ba3e2bf2df4cde32dcc9b75cb0d3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="746cded010c7ba3e2bf2df4cde32dcc9b75cb0d3"
 [1.6.x] Fixed #22321 -- Wrapped exceptions in _set_autocommit.

 Refs #21202.

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

Re: [Django] #22291: transactions.atomic (with savepoints) doesn't work correctly with deadlocks in mysql

[Django]

#22291: transactions.atomic (with savepoints) doesn't work correctly with 
deadlocks
in mysql
-+-
 Reporter:  err  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 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
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"80f6cbbadbd33574c8b949a8fbc77a5e94398e54"]:
 {{{
 #!CommitTicketReference repository=""
 revision="80f6cbbadbd33574c8b949a8fbc77a5e94398e54"
 [1.6.x] Increased robustness of 58161e4e. Refs #22291.

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

Re: [Django] #22291: transactions.atomic (with savepoints) doesn't work correctly with deadlocks in mysql

[Django]

#22291: transactions.atomic (with savepoints) doesn't work correctly with 
deadlocks
in mysql
-+-
 Reporter:  err  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 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
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"9afedbef4207a86d17d9525664bcd06f403cc6f9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9afedbef4207a86d17d9525664bcd06f403cc6f9"
 [1.6.x] Fixed #22291 -- Avoided shadowing deadlock exceptions on MySQL.

 Thanks err for the report.

 Backport of 58161e4e 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/061.050b44afad6a6e859082117d7090c2bd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21239: Closing connection inside atomic block breaks atomicity

[Django]

#21239: Closing connection inside atomic block breaks atomicity
-+-
 Reporter:  marcin@… |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  atomic close |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"4ea02bdb0dc6776fc29d8164e417469c9ba10f18"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4ea02bdb0dc6776fc29d8164e417469c9ba10f18"
 [1.6.x] Fixed #21239 -- Maintained atomicity when closing the connection.

 Refs #15802 -- Reverted #7c657b24 as BaseDatabaseWrapper.close() now
 has a proper "finally" clause that may need to preserve self.connection.

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

[django/django] 9afedb: [1.6.x] Fixed #22291 -- Avoided shadowing deadlock...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 9afedbef4207a86d17d9525664bcd06f403cc6f9
  
https://github.com/django/django/commit/9afedbef4207a86d17d9525664bcd06f403cc6f9
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/transaction.py
M tests/transactions/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #22291 -- Avoided shadowing deadlock exceptions on MySQL.

Thanks err for the report.

Backport of 58161e4e from master.


  Commit: 746cded010c7ba3e2bf2df4cde32dcc9b75cb0d3
  
https://github.com/django/django/commit/746cded010c7ba3e2bf2df4cde32dcc9b75cb0d3
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/backends/mysql/base.py
M django/db/backends/oracle/base.py
M django/db/backends/postgresql_psycopg2/base.py
M django/db/backends/sqlite3/base.py

  Log Message:
  ---
  [1.6.x] Fixed #22321 -- Wrapped exceptions in _set_autocommit.

Refs #21202.

Backport of 3becac84 from master


  Commit: 4ea02bdb0dc6776fc29d8164e417469c9ba10f18
  
https://github.com/django/django/commit/4ea02bdb0dc6776fc29d8164e417469c9ba10f18
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/backends/__init__.py
M django/db/backends/postgresql_psycopg2/base.py
M django/db/transaction.py
M tests/transactions/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #21239 -- Maintained atomicity when closing the connection.

Refs #15802 -- Reverted #7c657b24 as BaseDatabaseWrapper.close() now
has a proper "finally" clause that may need to preserve self.connection.

Backport of 25860096 from master.


  Commit: 1d3d2b9a2458cbf11b7e828fb59b3f2cb73d14fe
  
https://github.com/django/django/commit/1d3d2b9a2458cbf11b7e828fb59b3f2cb73d14fe
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/transaction.py
M tests/backends/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #21202 -- Maintained atomicity when the server disconnects.

Thanks intgr for the report.

This commit doesn't include a test because I don't know how to emulate a
database disconnection in a cross-database compatible way.

Also simplified a 'backends' test that was constrained by this problem.

Backport of 81761508 from master


  Commit: 80f6cbbadbd33574c8b949a8fbc77a5e94398e54
  
https://github.com/django/django/commit/80f6cbbadbd33574c8b949a8fbc77a5e94398e54
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/transaction.py

  Log Message:
  ---
  [1.6.x] Increased robustness of 58161e4e. Refs #22291.

Backport of ee837b9a from master


Compare: https://github.com/django/django/compare/de95867284dd...80f6cbbadbd3

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

Re: [Django] #22415: Migrate problems concerning foreignkeys to self

[Django]

#22415: Migrate problems concerning foreignkeys to self
---+---
 Reporter:  roughdesignapps@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.7-alpha-2
 Severity:  Normal |   Resolution:  needsinfo
 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 roughdesignapps@…):

 I am using a models folder with __init__.py importing the other .py files
 and
 {{{
 class Meta:
 app_label = 'foodapp'
 }}}
 in the models.

 I will be able to try reproducing against the master branch in an hour or
 so.

 I'm sorry, I actually have no idea what {{{python --Wall}}} is, Google
 does not help me there and my command prompt won't execute {{{python
 --Wall}}}.

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

Re: [Django] #22419: typofix for multi-db.txt

[Django]

#22419: typofix for multi-db.txt
---+--
 Reporter:  schmiddy@… |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Josh Kupershmidt ):

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

[Django] #22419: typofix for multi-db.txt

[Django]

#22419: typofix for multi-db.txt
---+
 Reporter:  schmiddy@… |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  0
---+
 Simple typofix for docs:

 "to more that one database" -> "to more than one database"

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

Re: [Django] #22415: Migrate problems concerning foreignkeys to self

[Django]

#22415: Migrate problems concerning foreignkeys to self
---+---
 Reporter:  roughdesignapps@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.7-alpha-2
 Severity:  Normal |   Resolution:  needsinfo
 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 loic84):

 roughdesignapps@ could you try with `python --Wall`? Are you using an
 `AppConfig` with a custom `label` by any chance?

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

Re: [Django] #22417: Django 1.7 DB connection fails due to requesting database "postgres"

[Django]

#22417: Django 1.7 DB connection fails due to requesting database "postgres"
---+--
 Reporter:  Jon F   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-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
---+--

Comment (by Jon F):

 Yes, this is something that can be fixed by editing the PostgreSQL
 configuration (the pg_hba.conf file).  And if it's only needed for running
 the unit tests, then it's probably not a big deal to change it.  Most
 people who care about security are going to be using different database
 servers for test and production, and they only have to change permissions
 on the test server.

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

Re: [Django] #21202: Atomic masks fatal database errors and instead propagates "connection already closed"

[Django]

#21202: Atomic masks fatal database errors and instead propagates "connection
already closed"
-+-
 Reporter:  intgr|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.6-beta-1
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"8176150850b2e34b2afe1dc107e184eb4c6cd668"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8176150850b2e34b2afe1dc107e184eb4c6cd668"
 Fixed #21202 -- Maintained atomicity when the server disconnects.

 Thanks intgr for the report.

 This commit doesn't include a test because I don't know how to emulate a
 database disconnection in a cross-database compatible way.

 Also simplified a 'backends' test that was constrained by this 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/063.9aa919144d46f8f0f70c9492d8fa8d3e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[Django]

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

Comment (by Aymeric Augustin ):

 In [changeset:"25860096f981b0b3026b38329e4b69c72b1d8db9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="25860096f981b0b3026b38329e4b69c72b1d8db9"
 Fixed #21239 -- Maintained atomicity when closing the connection.

 Refs #15802 -- Reverted #7c657b24 as BaseDatabaseWrapper.close() now
 has a proper "finally" clause that may need to preserve self.connection.
 }}}

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

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

Re: [Django] #22291: transactions.atomic (with savepoints) doesn't work correctly with deadlocks in mysql

[Django]

#22291: transactions.atomic (with savepoints) doesn't work correctly with 
deadlocks
in mysql
-+-
 Reporter:  err  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 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
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"ee837b9a0d08fea1e499bec3b094851a1bbe"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ee837b9a0d08fea1e499bec3b094851a1bbe"
 Increased robustness of 58161e4e. Refs #22291.
 }}}

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

Re: [Django] #21202: Atomic masks fatal database errors and instead propagates "connection already closed"

[Django]

#21202: Atomic masks fatal database errors and instead propagates "connection
already closed"
-+-
 Reporter:  intgr|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Database layer   |  1.6-beta-1
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"3becac84845cee8f12a5fb7f68c87cbaf029c6a0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3becac84845cee8f12a5fb7f68c87cbaf029c6a0"
 Fixed #22321 -- Wrapped exceptions in _set_autocommit.

 Refs #21202.
 }}}

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

Re: [Django] #22321: Missing DB errors wrapping around _set_autocommit

[Django]

#22321: Missing DB errors wrapping around _set_autocommit
-+-
 Reporter:  alexkoshelev |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"3becac84845cee8f12a5fb7f68c87cbaf029c6a0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3becac84845cee8f12a5fb7f68c87cbaf029c6a0"
 Fixed #22321 -- Wrapped exceptions in _set_autocommit.

 Refs #21202.
 }}}

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

Re: [Django] #21239: Closing connection inside atomic block breaks atomicity

[Django]

#21239: Closing connection inside atomic block breaks atomicity
-+-
 Reporter:  marcin@… |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  atomic close |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"25860096f981b0b3026b38329e4b69c72b1d8db9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="25860096f981b0b3026b38329e4b69c72b1d8db9"
 Fixed #21239 -- Maintained atomicity when closing the connection.

 Refs #15802 -- Reverted #7c657b24 as BaseDatabaseWrapper.close() now
 has a proper "finally" clause that may need to preserve self.connection.
 }}}

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

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

[django/django] 3becac: Fixed #22321 -- Wrapped exceptions in _set_autocom...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3becac84845cee8f12a5fb7f68c87cbaf029c6a0
  
https://github.com/django/django/commit/3becac84845cee8f12a5fb7f68c87cbaf029c6a0
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/backends/mysql/base.py
M django/db/backends/oracle/base.py
M django/db/backends/postgresql_psycopg2/base.py
M django/db/backends/sqlite3/base.py

  Log Message:
  ---
  Fixed #22321 -- Wrapped exceptions in _set_autocommit.

Refs #21202.


  Commit: 25860096f981b0b3026b38329e4b69c72b1d8db9
  
https://github.com/django/django/commit/25860096f981b0b3026b38329e4b69c72b1d8db9
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/backends/__init__.py
M django/db/backends/postgresql_psycopg2/base.py
M django/db/transaction.py
M tests/transactions/tests.py

  Log Message:
  ---
  Fixed #21239 -- Maintained atomicity when closing the connection.

Refs #15802 -- Reverted #7c657b24 as BaseDatabaseWrapper.close() now
has a proper "finally" clause that may need to preserve self.connection.


  Commit: 8176150850b2e34b2afe1dc107e184eb4c6cd668
  
https://github.com/django/django/commit/8176150850b2e34b2afe1dc107e184eb4c6cd668
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/transaction.py
M tests/backends/tests.py

  Log Message:
  ---
  Fixed #21202 -- Maintained atomicity when the server disconnects.

Thanks intgr for the report.

This commit doesn't include a test because I don't know how to emulate a
database disconnection in a cross-database compatible way.

Also simplified a 'backends' test that was constrained by this problem.


  Commit: ee837b9a0d08fea1e499bec3b094851a1bbe
  
https://github.com/django/django/commit/ee837b9a0d08fea1e499bec3b094851a1bbe
  Author: Aymeric Augustin 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/db/transaction.py

  Log Message:
  ---
  Increased robustness of 58161e4e. Refs #22291.


Compare: https://github.com/django/django/compare/d5031ecf881e...ee837b9a

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

Re: [Django] #22415: Migrate problems concerning foreignkeys to self

[Django]

#22415: Migrate problems concerning foreignkeys to self
---+---
 Reporter:  roughdesignapps@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.7-alpha-2
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by charettes):

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


Comment:

 Thanks for reporting this issue.

 Could you try reproducing against the master branch and provide and
 provide a sample of your .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/083.53bc3a5e338f7c788b510efa6129b207%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22383: Add the required tag to the input fields which are required for database entry

[Django]

#22383: Add the required tag to the input fields which are required for database
entry
-+---
 Reporter:  abhishek.garg@…  |Owner:  anubhav9042
 Type:  New feature  |   Status:  assigned
Component:  Forms|  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 anubhav9042):

 https://groups.google.com/forum/#!topic/django-developers/obw18wSc4xU

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

Re: [Django] #22417: Django 1.7 DB connection fails due to requesting database "postgres"

[Django]

#22417: Django 1.7 DB connection fails due to requesting database "postgres"
---+--
 Reporter:  Jon F   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-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):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * component:  Migrations => Testing framework
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 This is actually due to #16969, not migrations. I guess I came to the
 wrong conclusion that all users should have access to the `postgres`
 database. Is the permissions something you can fix? (in which case the fix
 may be simply to document the requirement as you noted)

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

Re: [Django] #21227: Selenium tests terminate with [Errno 10054]

[Django]

#21227: Selenium tests terminate with [Errno 10054]
---+
 Reporter:  marfire|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  selenium   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timo):

 #22252 was a duplicate.

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

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

Re: [Django] #22252: ConnectionResetError: [WinError 10054] in LiveServerTestCase with Selenium on Windows

[Django]

#22252: ConnectionResetError: [WinError 10054]  in LiveServerTestCase with 
Selenium
on Windows
---+--
 Reporter:  hjwp   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.6
 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 timo):

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


Comment:

 Duplicate of #21227

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

[django/django] ae7822: [1.7.x] Fixed #21353 -- Noted that description is ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: ae78227de3740cce7e2b460b2845f19443c4d090
  
https://github.com/django/django/commit/ae78227de3740cce7e2b460b2845f19443c4d090
  Author: Tim Graham 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M docs/ref/contrib/admin/index.txt

  Log Message:
  ---
  [1.7.x] Fixed #21353 -- Noted that description is ignored for TabularInlines.

Thanks nofinator for the report.

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

Re: [Django] #21353: 'description' key in InlineModelAdmin fieldsets is ignored

[Django]

#21353: 'description' key in InlineModelAdmin fieldsets is ignored
---+
 Reporter:  nofinator  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"de95867284ddf84bb4ca5e5946bae96d5d23babf"]:
 {{{
 #!CommitTicketReference repository=""
 revision="de95867284ddf84bb4ca5e5946bae96d5d23babf"
 [1.6.x] Fixed #21353 -- Noted that description is ignored for
 TabularInlines.

 Thanks nofinator for the report.

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

Re: [Django] #21353: 'description' key in InlineModelAdmin fieldsets is ignored

[Django]

#21353: 'description' key in InlineModelAdmin fieldsets is ignored
---+
 Reporter:  nofinator  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"ae78227de3740cce7e2b460b2845f19443c4d090"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ae78227de3740cce7e2b460b2845f19443c4d090"
 [1.7.x] Fixed #21353 -- Noted that description is ignored for
 TabularInlines.

 Thanks nofinator for the report.

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

[django/django] de9586: [1.6.x] Fixed #21353 -- Noted that description is ...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: de95867284ddf84bb4ca5e5946bae96d5d23babf
  
https://github.com/django/django/commit/de95867284ddf84bb4ca5e5946bae96d5d23babf
  Author: Tim Graham 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M docs/ref/contrib/admin/index.txt

  Log Message:
  ---
  [1.6.x] Fixed #21353 -- Noted that description is ignored for TabularInlines.

Thanks nofinator for the report.

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

Re: [Django] #21353: 'description' key in InlineModelAdmin fieldsets is ignored

[Django]

#21353: 'description' key in InlineModelAdmin fieldsets is ignored
---+
 Reporter:  nofinator  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"d5031ecf881eaefe7ada1c35228b35a1852dd343"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d5031ecf881eaefe7ada1c35228b35a1852dd343"
 Fixed #21353 -- Noted that description is ignored for TabularInlines.

 Thanks nofinator for the report.
 }}}

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

[django/django] d5031e: Fixed #21353 -- Noted that description is ignored ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d5031ecf881eaefe7ada1c35228b35a1852dd343
  
https://github.com/django/django/commit/d5031ecf881eaefe7ada1c35228b35a1852dd343
  Author: Tim Graham 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M docs/ref/contrib/admin/index.txt

  Log Message:
  ---
  Fixed #21353 -- Noted that description is ignored for TabularInlines.

Thanks nofinator for the report.


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

Re: [Django] #21048: Error page should not invoke callables passed through WSGI META structure

[Django]

#21048: Error page should not invoke callables passed through WSGI META 
structure
--+
 Reporter:  ericbuehl |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 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 timo):

 * component:  Uncategorized => Core (Other)


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

Re: [Django] #22209: Django internals call len(queryset) instead of queryset.count()

[Django]

#22209: Django internals call len(queryset) instead of queryset.count()
-+-
 Reporter:  gcc  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * component:  Uncategorized => Database layer (models, ORM)
 * easy:  1 => 0


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

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

Re: [Django] #21773: development server sometimes takes a long time to restart after source has been changed

[Django]

#21773: development server sometimes takes a long time to restart after source 
has
been changed
-+-
 Reporter:  clime|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.6
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * component:  Uncategorized => Core (Management commands)


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

Re: [Django] #22050: defer('related__subfield') and select_related() on proxy model raises error

[Django]

#22050: defer('related__subfield') and select_related() on proxy model raises 
error
-+-
 Reporter:  lovasb   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  defer,proxy,query|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * component:  Uncategorized => Database layer (models, ORM)


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

Re: [Django] #21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to the DB backend

[Django]

#21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to 
the
DB backend
-+-
 Reporter:  gcbirzan |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * component:  Uncategorized => Database layer (models, ORM)


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

Re: [Django] #21481: Install 1.6 Django-admin.py bug in Mac OS X 10.9

[Django]

#21481: Install 1.6 Django-admin.py bug in Mac OS X 10.9
--+
 Reporter:  mdc@… |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Packaging |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:  install   | 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):

 * component:  Uncategorized => Packaging
 * type:  Bug => Cleanup/optimization


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

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

[django/django] b4681b: [1.7.x] Fixed #22364 -- Sanitized getpass input in...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: b4681be154dd7194041e94f3eb6d7f24217b9a1b
  
https://github.com/django/django/commit/b4681be154dd7194041e94f3eb6d7f24217b9a1b
  Author: John Paulett 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/contrib/auth/management/commands/changepassword.py
M docs/releases/1.6.3.txt

  Log Message:
  ---
  [1.7.x] Fixed #22364 -- Sanitized getpass input in changepassword.

Python 2 getpass on Windows does not accept unicode, even
when containing on ASCII characters. Related #190807.

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

Re: [Django] #22364: changepassword fails on Windows

[Django]

#22364: changepassword fails on Windows
--+
 Reporter:  jpaulett  |Owner:  jpaulett
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.6
 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
--+

Comment (by Tim Graham ):

 In [changeset:"129cb7e2228cf076104eb5de69e6063f1bf34dd9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="129cb7e2228cf076104eb5de69e6063f1bf34dd9"
 [1.6.x] Fixed #22364 -- Sanitized getpass input in changepassword.

 Python 2 getpass on Windows does not accept unicode, even
 when containing on ASCII characters. Related #190807.

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

Re: [Django] #22364: changepassword fails on Windows

[Django]

#22364: changepassword fails on Windows
--+
 Reporter:  jpaulett  |Owner:  jpaulett
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.6
 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
--+

Comment (by Tim Graham ):

 In [changeset:"b4681be154dd7194041e94f3eb6d7f24217b9a1b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b4681be154dd7194041e94f3eb6d7f24217b9a1b"
 [1.7.x] Fixed #22364 -- Sanitized getpass input in changepassword.

 Python 2 getpass on Windows does not accept unicode, even
 when containing on ASCII characters. Related #190807.

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

[django/django] 129cb7: [1.6.x] Fixed #22364 -- Sanitized getpass input in...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 129cb7e2228cf076104eb5de69e6063f1bf34dd9
  
https://github.com/django/django/commit/129cb7e2228cf076104eb5de69e6063f1bf34dd9
  Author: John Paulett 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/contrib/auth/management/commands/changepassword.py
M docs/releases/1.6.3.txt

  Log Message:
  ---
  [1.6.x] Fixed #22364 -- Sanitized getpass input in changepassword.

Python 2 getpass on Windows does not accept unicode, even
when containing on ASCII characters. Related #190807.

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

Re: [Django] #22364: changepassword fails on Windows

[Django]

#22364: changepassword fails on Windows
--+
 Reporter:  jpaulett  |Owner:  jpaulett
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.6
 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"b5a9166f7e0e21ae0f2cc8f218b422bc2c116fb0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b5a9166f7e0e21ae0f2cc8f218b422bc2c116fb0"
 Fixed #22364 -- Sanitized getpass input in changepassword.

 Python 2 getpass on Windows does not accept unicode, even
 when containing on ASCII characters. Related #190807.
 }}}

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

[django/django] b5a916: Fixed #22364 -- Sanitized getpass input in changep...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b5a9166f7e0e21ae0f2cc8f218b422bc2c116fb0
  
https://github.com/django/django/commit/b5a9166f7e0e21ae0f2cc8f218b422bc2c116fb0
  Author: John Paulett 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/contrib/auth/management/commands/changepassword.py
M docs/releases/1.6.3.txt

  Log Message:
  ---
  Fixed #22364 -- Sanitized getpass input in changepassword.

Python 2 getpass on Windows does not accept unicode, even
when containing on ASCII characters. Related #190807.


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

[django/django] ea5a98: Refactored some code in SelectDateWidget.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ea5a98470467d5a53f10caf77510c77504f733dd
  
https://github.com/django/django/commit/ea5a98470467d5a53f10caf77510c77504f733dd
  Author: Tomasz Wysocki 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/forms/extras/widgets.py

  Log Message:
  ---
  Refactored some code in SelectDateWidget.


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

Re: [Django] #20086: UserCreationForm does not support custom models.

[Django]

#20086: UserCreationForm does not support custom models.
--+
 Reporter:  efrinut@… |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.5
 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
--+

Comment (by anonymous):

 Solved

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

Re: [Django] #20086: UserCreationForm does not support custom models.

[Django]

#20086: UserCreationForm does not support custom models.
--+
 Reporter:  efrinut@… |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.5
 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 anonymous):

 * has_patch:  0 => 1
 * resolution:  invalid => fixed
 * 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/075.37f369ce6107fdff4774570a9040a828%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22418: Remove app_name attribute of AdminSite

[Django]

#22418: Remove app_name attribute of AdminSite
---+--
 Reporter:  vzima  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.6
 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 timo):

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


Comment:

 Duplicate of #21132, feel free to leave your thoughts there.

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

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

Re: [Django] #20550: Add an option to preserve the database between test runs

[Django]

#20550: Add an option to preserve the database between test runs
---+
 Reporter:  aaugustin  |Owner:  gchp
 Type:  New feature|   Status:  assigned
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 gchp):

 aaugustin, thanks for this. I haven't had a huge amount of time to work on
 this lately, just getting bits here and there. This is very helpful
 though, 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.86281945776d241ea549e1f9e42be7e1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22418: Remove app_name attribute of AdminSite

[Django]

#22418: Remove app_name attribute of AdminSite
---+
 Reporter:  vzima  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Since the admin application uses single application namespace `admin`
 which is hardcoded it is ridiculous to have an option which can alter this
 value.

 This attribute causes confusion between developers, see #19002 #19554.

 I attach patch which shows failures in `admin_views` tests in Django 1.6.

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

Re: [Django] #22194: Add ability to introspect available tags

[Django]

#22194: Add ability to introspect available tags
-+-
 Reporter:  russellm |Owner:  Elvard
 Type:  New feature  |   Status:  closed
Component:  Core (System |  Version:
  checks)|  1.7-alpha-1
 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
-+-

Comment (by Tim Graham ):

 In [changeset:"ddd25b280f69ffcb5eb7ab2695c6094256090947"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ddd25b280f69ffcb5eb7ab2695c6094256090947"
 [1.7.x] Fixed #22194 -- Added --list-tags option to check command.

 Thanks Elvard for the patch.

 Backport of 395d75ea6b 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/066.e55e8d258045c6fdfe193c6b5396aa72%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 395d75: Fixed #22194 -- Added --list-tags option to check ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 395d75ea6bd1ee5259fd5a3b3ac1b028739a22d2
  
https://github.com/django/django/commit/395d75ea6bd1ee5259fd5a3b3ac1b028739a22d2
  Author: Tim Graham 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/core/checks/registry.py
M django/core/management/commands/check.py
M docs/ref/django-admin.txt
M tests/check_framework/tests.py

  Log Message:
  ---
  Fixed #22194 -- Added --list-tags option to check command.

Thanks Elvard for the patch.


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

Re: [Django] #22194: Add ability to introspect available tags

[Django]

#22194: Add ability to introspect available tags
-+-
 Reporter:  russellm |Owner:  Elvard
 Type:  New feature  |   Status:  closed
Component:  Core (System |  Version:
  checks)|  1.7-alpha-1
 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:"395d75ea6bd1ee5259fd5a3b3ac1b028739a22d2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="395d75ea6bd1ee5259fd5a3b3ac1b028739a22d2"
 Fixed #22194 -- Added --list-tags option to check command.

 Thanks Elvard for the patch.
 }}}

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

[django/django] ddd25b: [1.7.x] Fixed #22194 -- Added --list-tags option t...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: ddd25b280f69ffcb5eb7ab2695c6094256090947
  
https://github.com/django/django/commit/ddd25b280f69ffcb5eb7ab2695c6094256090947
  Author: Tim Graham 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/core/checks/registry.py
M django/core/management/commands/check.py
M docs/ref/django-admin.txt
M tests/check_framework/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22194 -- Added --list-tags option to check command.

Thanks Elvard for the patch.

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

[Django] #22417: Django 1.7 DB connection fails due to requesting database "postgres"

[Django]

#22417: Django 1.7 DB connection fails due to requesting database "postgres"
-+
 Reporter:  Jon F |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Migrations   |Version:  1.7-beta-1
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I'm trying Django 1.7 Beta 1 with the PostgreSQL back end.

 When I run my unit tests under Django 1.7b1, one of the very first things
 it does is try to connect to the "postgres" database, using the
 credentials configured in my settings.  But in my PostgreSQL
 configuration, that user doesn't have access to the "postgres" database,
 so it fails with an error message.  Django 1.6 does what I would expect:
 it only connects to the database that's configured in DATABASES.

 The error message is:

 {{{
 Creating test database for alias 'default'...
 Traceback (most recent call last):
   File "./manage.py", line 8, in 
 execute_from_command_line(sys.argv)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/__init__.py", line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/commands/test.py", line 50, in
 run_from_argv
 super(Command, self).run_from_argv(argv)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/commands/test.py", line 71, in execute
 super(Command, self).execute(*args, **options)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/base.py", line 337, in execute
 output = self.handle(*args, **options)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/commands/test.py", line 88, in handle
 failures = test_runner.run_tests(test_labels)
   File "/usr/local/lib/python2.7/dist-packages/django/test/runner.py",
 line 147, in run_tests
 old_config = self.setup_databases()
   File "/usr/local/lib/python2.7/dist-packages/django/test/runner.py",
 line 109, in setup_databases
 return setup_databases(self.verbosity, self.interactive, **kwargs)
   File "/usr/local/lib/python2.7/dist-packages/django/test/runner.py",
 line 297, in setup_databases
 verbosity, autoclobber=not interactive)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/backends/creation.py", line 354, in create_test_db
 self._create_test_db(verbosity, autoclobber)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/backends/creation.py", line 409, in _create_test_db
 with self._nodb_connection.cursor() as cursor:
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/backends/__init__.py", line 159, in cursor
 cursor = utils.CursorWrapper(self._cursor(), self)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/backends/__init__.py", line 129, in _cursor
 self.ensure_connection()
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/backends/__init__.py", line 124, in ensure_connection
 self.connect()
   File "/usr/local/lib/python2.7/dist-packages/django/db/utils.py", line
 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/backends/__init__.py", line 124, in ensure_connection
 self.connect()
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/backends/__init__.py", line 113, in connect
 self.connection = self.get_new_connection(conn_params)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/backends/postgresql_psycopg2/base.py", line 135, in
 get_new_connection
 return Database.connect(**conn_params)
   File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179,
 in connect
 connection_factory=connection_factory, async=async)
 django.db.utils.OperationalError: FATAL:  Peer authentication failed for
 user "ligada"
 }}}

 When you try to connect to a PostgreSQL database, it searches pg_hba.conf
 using your connection method, username, and the name of the database
 you're connecting to, to decide whether or not to allow the connection,
 and whether to require a password or not.  I gave my DB user the minimum
 possible rights - that's just good security practise.  So that user was
 only allowed to connect to my app database & the app_test database, it
 wasn't allowed to connect to the "postgres" database.  Adding an extra
 line to pg_hba.conf to allow that user to access the "postgres" database
 has worked around this issue.

 I am guessing that this 

Re: [Django] #22195: Use constants to define built-in tags

[Django]

#22195: Use constants to define built-in tags
-+-
 Reporter:  russellm |Owner:  Elvard
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Core (System |  1.7-alpha-1
  checks)|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"32e62374506827723423471a115e6b25313ed887"]:
 {{{
 #!CommitTicketReference repository=""
 revision="32e62374506827723423471a115e6b25313ed887"
 [1.7.x] Fixed #22195 -- Used constants to define built-in tags for check
 framework.

 Thanks Elvard for the patch.

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

[django/django] 32e623: [1.7.x] Fixed #22195 -- Used constants to define b...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 32e62374506827723423471a115e6b25313ed887
  
https://github.com/django/django/commit/32e62374506827723423471a115e6b25313ed887
  Author: Tim Graham 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/contrib/admin/apps.py
M django/contrib/auth/apps.py
M django/contrib/contenttypes/apps.py
M django/core/checks/__init__.py
M django/core/checks/compatibility/django_1_6_0.py
M django/core/checks/model_checks.py
M django/core/checks/registry.py

  Log Message:
  ---
  [1.7.x] Fixed #22195 -- Used constants to define built-in tags for check 
framework.

Thanks Elvard for the patch.

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

[django/django] b513fa: Fixed #22195 -- Used constants to define built-in ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b513fa5fc6f10a6e224d602bfac8f850040cef7c
  
https://github.com/django/django/commit/b513fa5fc6f10a6e224d602bfac8f850040cef7c
  Author: Tim Graham 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M django/contrib/admin/apps.py
M django/contrib/auth/apps.py
M django/contrib/contenttypes/apps.py
M django/core/checks/__init__.py
M django/core/checks/compatibility/django_1_6_0.py
M django/core/checks/model_checks.py
M django/core/checks/registry.py

  Log Message:
  ---
  Fixed #22195 -- Used constants to define built-in tags for check framework.

Thanks Elvard for the patch.


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

Re: [Django] #21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout passed

[Django]

#21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout 
passed
-+-
 Reporter:  ekeydar@…|Owner:  err
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  mysql|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 Replying to [comment:22 aaugustin]:
 > Unless I missed something, this only affects people that have management
 commands running for more than 8 hours (or MySQL's connection timeout if
 it has been changed from the default). Is that correct?
 As far as I can tell I think this is correct. At least this is the place
 where I was hitting this bug in my environment (before downgrading to 1.5
 again because of 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/075.4f801b5e70e8554f5b44b53dd504a171%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 0b4330: [1.7.x] Fixed #22412 -- More nuanced advice re tem...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 0b43308e2de5dcac67b530bb03376655dfb61cef
  
https://github.com/django/django/commit/0b43308e2de5dcac67b530bb03376655dfb61cef
  Author: Carl Meyer 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M docs/howto/custom-template-tags.txt

  Log Message:
  ---
  [1.7.x] Fixed #22412 -- More nuanced advice re template filters and 
exceptions.

Thanks Tim for review.

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

Re: [Django] #22412: Clarify expectation around template filters and exceptions

[Django]

#22412: Clarify expectation around template filters and exceptions
-+-
 Reporter:  carljm   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"0b43308e2de5dcac67b530bb03376655dfb61cef"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0b43308e2de5dcac67b530bb03376655dfb61cef"
 [1.7.x] Fixed #22412 -- More nuanced advice re template filters and
 exceptions.

 Thanks Tim for review.

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

[django/django] 728fd2: [1.6.x] Fixed #22412 -- More nuanced advice re tem...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 728fd27c005e98868a3be74949f306038e30e427
  
https://github.com/django/django/commit/728fd27c005e98868a3be74949f306038e30e427
  Author: Carl Meyer 
  Date:   2014-04-10 (Thu, 10 Apr 2014)

  Changed paths:
M docs/howto/custom-template-tags.txt

  Log Message:
  ---
  [1.6.x] Fixed #22412 -- More nuanced advice re template filters and 
exceptions.

Thanks Tim for review.

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

[Django] #22416: Migrate can't create ManyToManyField for Model wigrated in the same run

[Django]

#22416: Migrate can't create ManyToManyField for Model wigrated in the same run
--+-
 Reporter:  roughdesignapps@… |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Migrations|Version:  1.7-alpha-2
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 I have a fresh database and created the inital migrations.

 When trying to apply the migrations with 'migrate ', I get
 {{{
 django.db.utils.ProgrammingError: (1146, "Table
 '.django_content_type' doesn't exist")
 }}}
 Makes sense so far as django_content_type is from another app.

 Running 'migrate' (without app name) runs through my first app OK.
 When it runs through the migrations for the second app, I get
 {{{
 ValueError: Related model 'appname.Modelname' cannot be resolved
 }}}
 I checked the spelling in the migrations inital file, it's fine.

 The Model with the field which gives the error contains 2
 ManyToManyFields, let's call them A and B for convenience. They are
 identical except for the model they reference.

 Field A relates to a model from a third app,
 which has not been handled by migrations by then.
 Field B relates to a model from the first app.

 In the migrations file (and the model), Field A is mentioned first and
 gives no errors.
 Field B is mentioned after Field A and raises the ValueError.

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

[Django] #22415: Migrate problems concerning foreignkeys to self

[Django]

#22415: Migrate problems concerning foreignkeys to self
---+-
 Reporter:  roughdesignapps@…  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Migrations |Version:  1.7-alpha-2
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 Running 'python manage.py makemigrations ' creates migrations for
 the app,

 However, when I use 'python manage.py makemigrations',
 it does not find any tables/changes and no migrations are created.

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

Re: [Django] #22413: Allow model instance attributes in ModelAdmin.fields

[Django]

#22413: Allow model instance attributes in ModelAdmin.fields
-+-
 Reporter:  moritzs  |Owner:  moritzs
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  ModelAdmin instance  | Triage Stage:
  attribute field|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by moritzs):

 Replying to [comment:4 timo]:
 > Thanks for the proposal, but I don't feel this is a common enough use-
 case to justify the additional complexity. I don't think we should
 encourage writing really complex `__getattr__` methods. As noted earlier,
 you can add proper methods or properties if you need something in
 `fields`.

 How does this add complexity to django? It doesn't break or change the
 behaviour of `ModelAdmin`.
 Besides, I really consider
 {{{
 class MyModel(models.Model):
 # ... fields

 def __getattr__(self, name):
 # ... do_something
 }}}
 more pythonic than
 {{{
 class MyModel(models.Model):
 # ... fields

 @property
 def field1_do_something(self):
 return do_something(self.field1)

 @property
 def field2_do_something(self):
 return do_something(self.field2)

 ...
 }}}

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

Re: [Django] #3214: [patch] raw sql file doesn't recognize quotes correctly

[Django]

#3214: [patch] raw sql file doesn't recognize quotes correctly
-+-
 Reporter:  shaunc  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  rawsql migrations|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * keywords:  rawsql => rawsql migrations
 * needs_better_patch:  1 => 0
 * has_patch:  1 => 0
 * severity:  Normal => Release blocker


Comment:

 This ticket never tells which backend support multiple statements in
 `cursor.execute()` and which don't. It would be interesting to check that
 on the four officially supported databases before going any further...

 

 If indeed some backends need splitting, in order to close this ticket, we
 must implement a similar approach as #22401 in `RunSQL._split_sql`.

 Splitting occurs only when explicitly setting `multiple=True`, which
 Django itself never does, even in the test suite. We should add a test for
 that (and skip it when sqlparse isn't available.

 The patch will be easier if we include it in 1.7 because we won't need a
 deprecation path. Therefore, marking as a release blocker.

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

Re: [Django] #3214: [patch] raw sql file doesn't recognize quotes correctly

[Django]

#3214: [patch] raw sql file doesn't recognize quotes correctly
-+-
 Reporter:  shaunc  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  rawsql   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by wdoekes):

 Assuming sqlparse does the job, this can indeed be closed. 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/086.980afb35d3fa8c2bd89b23a0482f48a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #3214: [patch] raw sql file doesn't recognize quotes correctly

[Django]

#3214: [patch] raw sql file doesn't recognize quotes correctly
-+-
 Reporter:  shaunc  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  rawsql   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 At least parts of this must have been fixed in #22401, see
 071c9337750b296d198cced56f3ffad0e176afb6.

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

Re: [Django] #21553: InterfaceError in Postgres

[Django]

#21553: InterfaceError in Postgres
-+-
 Reporter:  anonymous|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Replying to [comment:12 maikhoepfel]:

 > I tried to reproduce this locally, but did not manage so far. The
 downtimes were caused by Heroku restarting the PostgreSQL service, from
 which Django should be able to recover gracefully.

 If you tested with runserver, it opens a new connection for each request,
 because connections are thread local and it uses a new thread for each
 connection. You must use `./manage.py runserver --nothreading` to test
 this feature.

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