python-pgsql - stacktrace when using arrays
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-pgsql (Ubuntu) |
Fix Released
|
Medium
|
Luca Falavigna |
Bug Description
Binary package hint: python-pgsql
The following code causes a stacktrace in python-pgsql :
------
import PgSQL
conn = PgSQL.connect(
cur.execute("SELECT ARRAY[now()]")
res = cur.fetchall()
------
Here is the stacktrace (test.py is the test file containing the above code):
------
Traceback (most recent call last):
File "/usr/lib/
res = cur.fetchall()
File "/usr/lib/
_list.
File "/usr/lib/
_r.
File "/usr/lib/
return self.handleArra
File "/usr/lib/
if _fvt != PG_INTERVAL:
NameError: global name '_fvt' is not defined
------
This bug is present in edgy, feisty and gutsy, but not in dapper. It was not tested in hardy.
We can conclude the following :
* the bug appeared in version 2.5.1 (since edgy)
* the bug is not caused from the upgrade of python 2.4 to python 2.5 (since the bug is in edgy, which uses python 2.4)
This bug is pretty strange, since '_fvt' seems to be used in the live above the error (line 998).
Reported upstream: http:// sourceforge. net/tracker/ index.php? func=detail& aid=1854028& group_id= 16528&atid= 116528.