@@ -206,7 +206,8 @@ def fetchall(self, sql, parameters=None):
206206 yield row
207207
208208 def get_cursor (self , * a , ** kw ):
209- """Return a :py:class:`~postgres.CursorContextManager` that uses our connection pool.
209+ """Return a :py:class:`~postgres.CursorContextManager` that uses our
210+ connection pool.
210211
211212 This is what :py:meth:`~postgres.Postgres.execute`,
212213 :py:meth:`~postgres.Postgres.fetchone`, and
@@ -219,7 +220,8 @@ def get_cursor(self, *a, **kw):
219220 return CursorContextManager (self .pool , * a , ** kw )
220221
221222 def get_transaction (self , * a , ** kw ):
222- """Return a :py:class:`~postgres.TransactionContextManager` that uses our connection pool.
223+ """Return a :py:class:`~postgres.TransactionContextManager` that uses
224+ our connection pool.
223225
224226 Use this when you want a series of statements to be part of one
225227 transaction, but you don't need fine-grained control over the
@@ -229,7 +231,8 @@ def get_transaction(self, *a, **kw):
229231 return TransactionContextManager (self .pool , * a , ** kw )
230232
231233 def get_connection (self ):
232- """Return a :py:class:`~postgres.ConnectionContextManager` that uses our connection pool.
234+ """Return a :py:class:`~postgres.ConnectionContextManager` that uses
235+ our connection pool.
233236
234237 Use this when you want to take advantage of connection pooling, but
235238 otherwise need full control, for example, to do complex things with
@@ -296,7 +299,8 @@ def __exit__(self, *exc_info):
296299
297300
298301class TransactionContextManager (object ):
299- """Instantiated once per :py:func:`~postgres.Postgres.get_transaction` call.
302+ """Instantiated once per :py:func:`~postgres.Postgres.get_transaction`
303+ call.
300304
301305 The return value of :py:func:`TransactionContextManager.__enter__` is a
302306 :py:class:`psycopg2.extras.RealDictCursor`. Any positional and keyword
0 commit comments