{{{
def _reset_sequences(self, db_name):
...
cursor = conn.cursor()
for sql in sql_list:
cursor.execute(sql)
}}}
This pattern exists multiple time throughout Django. Using a context
manager helps ensure resources are closed deterministically and that
errors aren't hidden.
--
Ticket URL: <https://code.djangoproject.com/ticket/28853>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/9394 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/28853#comment:1>
* component: Uncategorized => Database layer (models, ORM)
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/28853#comment:2>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/28853#comment:3>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"7a6fbf36b1fdb8978ea0842075ccce83bcd63789" 7a6fbf3]:
{{{
#!CommitTicketReference repository=""
revision="7a6fbf36b1fdb8978ea0842075ccce83bcd63789"
Fixed #28853 -- Updated connection.cursor() uses to use a context manager.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28853#comment:4>