|
9 | 9 | <para>
|
10 | 10 | The <application>PL/Python</application> procedural language allows
|
11 | 11 | <productname>PostgreSQL</productname> functions to be written in the
|
12 |
| - <ulink url="http://www.python.org">Python language</ulink>. |
| 12 | + <ulink url="https://www.python.org">Python language</ulink>. |
13 | 13 | </para>
|
14 | 14 |
|
15 | 15 | <para>
|
|
89 | 89 | </itemizedlist>
|
90 | 90 |
|
91 | 91 | This scheme is analogous to the recommendations in <ulink
|
92 |
| - url="http://www.python.org/dev/peps/pep-0394/">PEP 394</ulink> regarding the |
| 92 | + url="https://www.python.org/dev/peps/pep-0394/">PEP 394</ulink> regarding the |
93 | 93 | naming and transitioning of the <command>python</command> command.
|
94 | 94 | </para>
|
95 | 95 |
|
|
165 | 165 |
|
166 | 166 | <para>
|
167 | 167 | See also the
|
168 |
| - document <ulink url="http://docs.python.org/py3k/whatsnew/3.0.html">What's |
| 168 | + document <ulink url="https://docs.python.org/3/whatsnew/3.0.html">What's |
169 | 169 | New In Python 3.0</ulink> for more information about porting to
|
170 | 170 | Python 3.
|
171 | 171 | </para>
|
@@ -1116,7 +1116,7 @@ $$ LANGUAGE plpythonu;
|
1116 | 1116 | batch of rows, never larger than the parameter value. Once all rows are
|
1117 | 1117 | exhausted, <literal>fetch</literal> starts returning an empty result
|
1118 | 1118 | object. Cursor objects also provide an
|
1119 |
| - <ulink url="http://docs.python.org/library/stdtypes.html#iterator-types">iterator |
| 1119 | + <ulink url="https://docs.python.org/library/stdtypes.html#iterator-types">iterator |
1120 | 1120 | interface</ulink>, yielding one row at a time until all rows are
|
1121 | 1121 | exhausted. Data fetched that way is not returned as result objects, but
|
1122 | 1122 | rather as dictionaries, each dictionary corresponding to a single result
|
@@ -1167,7 +1167,7 @@ $$ LANGUAGE plpythonu;
|
1167 | 1167 | <para>
|
1168 | 1168 | Do not confuse objects created by <literal>plpy.cursor</literal> with
|
1169 | 1169 | DB-API cursors as defined by
|
1170 |
| - the <ulink url="http://www.python.org/dev/peps/pep-0249/">Python |
| 1170 | + the <ulink url="https://www.python.org/dev/peps/pep-0249/">Python |
1171 | 1171 | Database API specification</ulink>. They don't have anything in common
|
1172 | 1172 | except for the name.
|
1173 | 1173 | </para>
|
@@ -1297,7 +1297,7 @@ $$ LANGUAGE plpythonu;
|
1297 | 1297 | helper object to manage explicit subtransactions that gets created
|
1298 | 1298 | with the <literal>plpy.subtransaction()</literal> function.
|
1299 | 1299 | Objects created by this function implement the
|
1300 |
| - <ulink url="http://docs.python.org/library/stdtypes.html#context-manager-types"> |
| 1300 | + <ulink url="https://docs.python.org/library/stdtypes.html#context-manager-types"> |
1301 | 1301 | context manager interface</ulink>. Using explicit subtransactions
|
1302 | 1302 | we can rewrite our function as:
|
1303 | 1303 | <programlisting>
|
@@ -1373,7 +1373,7 @@ $$ LANGUAGE plpythonu;
|
1373 | 1373 | Although context managers were implemented in Python 2.5, to use
|
1374 | 1374 | the <literal>with</literal> syntax in that version you need to
|
1375 | 1375 | use a <ulink
|
1376 |
| - url="http://docs.python.org/release/2.5/ref/future.html">future |
| 1376 | + url="https://docs.python.org/release/2.5/ref/future.html">future |
1377 | 1377 | statement</ulink>. Because of implementation details, however,
|
1378 | 1378 | you cannot use future statements in PL/Python functions.
|
1379 | 1379 | </para>
|
|
0 commit comments