-
The augmented arithmetic operations on PgNumeric instances will update the object directly,
instead of creating a new one.
This leads to unexpected results such as:
$ cat t.py
from pyPgSQL.PgSQL import PgNumeric
a = PgNumeric(1.0)
b = a
b += 1
print a, b
$ python t.py
2.0 2.0
Here we see b is incremented, but both a and b
are changed, because the __iadd__...
2007-07-17 22:56:07 UTC in Python Interface to PostgreSQL
-
Configuration: pyPgSQL-2.5.1, python 2.5, freebsd 6.0.
Use of the magic toggleShowQuery attribute causes a
seg fault in strlen(). This is caused by messed up reference counts. The attached patch fixes the problem.
2006-12-18 18:41:28 UTC in Python Interface to PostgreSQL
-
To be clear, here's a simple example that demonstrates the bug.
We assume Db credentials are in the environment:
from pyPgSQL import PgSQL
db = PgSQL.connect()
cur = db.cursor()
cur.execute("select interval '2 years 3 days 12:34:56.78'")
cur.fetchall()
2006-12-06 20:46:03 UTC in Python Interface to PostgreSQL
-
PgSQL.py 2.5.1 uses int() to parse the time part of a postgres interval string. When the seconds part contains a decimal, int() will throw a ValueError.
The attached patch just discards the decimal part, since mx.DateTime.RelativeTime stores seconds as an integer.
2006-12-05 23:59:11 UTC in Python Interface to PostgreSQL
-
ConfigParser considers leading white space before
options and comments to be syntax errors, which is a
bit harsh, and limits the utility of the module when
parsing files originally written for other programs,
such as Samba's smb.conf.
The attached patch ignores leading white space on
options, and skips comments with leading w.s.
2006-07-18 21:17:05 UTC in Python
-
Logged In: YES
user_id=203927
Oops, forgot the patch...
2005-11-16 19:15:21 UTC in mod_gzip
-
RFC 2616 says HTTP headers are case-insensitive.
Mod_gzip 1.3.26.1a does not ignore case on the first
letter of the header. The effect is that, if the
response contains the (legal) header:
content-length: 123
mod_gzip will pass it through, and add its own
Content-Length header.
The attached patch simply checks for both cases when
examining the first character of the header line.
2005-11-16 19:11:25 UTC in mod_gzip
-
Logged In: YES
user_id=203927
Thanks for the quick response.
Perhaps my original post was unclear,
but the patch I included does precisely as you suggest:
it indents the second call.
2005-11-08 17:34:32 UTC in Python
-
Visual inspection of _connect_unixsocket() in
Lib/logging/handlers.py
shows that, in the absence of an exception, a DGRAM
socket will always be connected twice. This is likely
harmless, but also pointless.
The attached patch against today's CVS simply omits the
second connect() call.
2005-11-07 20:14:49 UTC in Python
-
kenlalonde committed patchset 2061 of module Webware to the Webware for Python CVS repository, changing 1 files.
2005-03-14 23:40:55 UTC in Webware for Python