Your message dated Sat, 26 Mar 2005 18:16:34 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#300324: fixed in python-mysqldb 1.2.0-4
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 18 Mar 2005 23:55:14 +0000
>From [EMAIL PROTECTED] Fri Mar 18 15:55:14 2005
Return-path: <[EMAIL PROTECTED]>
Received: from fungible.com (lobus.fungible.com) [64.161.114.2]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DCRJB-0001ok-00; Fri, 18 Mar 2005 15:55:13 -0800
Received: from lobus.fungible.com (localhost [127.0.0.1])
by lobus.fungible.com (8.13.1/8.13.1/Debian-17) with ESMTP id
j2INtAET002116
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Fri, 18 Mar 2005 15:55:10 -0800
Received: (from [EMAIL PROTECTED])
by lobus.fungible.com (8.13.1/8.13.1/Submit) id j2INtA5b002112;
Fri, 18 Mar 2005 15:55:10 -0800
From: Tim Freeman <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
Date: Fri, 18 Mar 2005 15:53:12 -0700
From-Tims-Fingers: true
To: [EMAIL PROTECTED]
Subject: python-mysqldb: Python True is mysql false when inserting
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: python-mysqldb
Version: 1.1.6-1
Severity: normal
*** Please type your report below this line ***
Using python2.3-mysqldb against mysql-server 4.1.9-2, I can run this program
import MySQLdb
import MySQLdb.converters
_conversions = MySQLdb.converters.conversions.copy()
# To make the bug go away, comment in the next line.
#_conversions[bool] = lambda x, d: int(x)
conn = MySQLdb.connect(host='x', user='x', passwd='x', db='x',
conv = _conversions)
cursor = conn.cursor()
cursor.execute("drop table if exists foo");
cursor.execute("create table foo (x boolean)");
# Inserting a print statement strategically into the MySQLdb package shows
# that the next execute does this mysql:
# insert into foo(x) values ('True');
# which, when I do it directly from the mysql command line, inserts a 0 into
# foo, not a 1.
cursor.execute("insert into foo (x) values (%s)", (True,))
cursor.execute("select * from foo")
(value,) = cursor.fetchone()
print "Value is %r" % (value,) # prints 0, should print True or 1.
assert value
and it hits the assert because inserting True inserts a 0 into the database.
There's a workaround commented out at the top of the script.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (700, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-386
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages python-mysqldb depends on:
ii python 2.3.4-5 An interactive high-level object-o
ii python2.3-mysqldb 1.1.6-1 A Python interface to MySQL
-- no debconf information
---------------------------------------
Received: (at 300324-close) by bugs.debian.org; 26 Mar 2005 23:30:28 +0000
>From [EMAIL PROTECTED] Sat Mar 26 15:30:27 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DFKjb-0005AP-00; Sat, 26 Mar 2005 15:30:27 -0800
Received: from joerg by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DFKWA-0001yz-00; Sat, 26 Mar 2005 18:16:34 -0500
From: Jonas Meurer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: lisa $Revision: 1.30 $
Subject: Bug#300324: fixed in python-mysqldb 1.2.0-4
Message-Id: <[EMAIL PROTECTED]>
Sender: Joerg Jaspert <[EMAIL PROTECTED]>
Date: Sat, 26 Mar 2005 18:16:34 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 4
Source: python-mysqldb
Source-Version: 1.2.0-4
We believe that the bug you reported is fixed in the latest version of
python-mysqldb, which is due to be installed in the Debian FTP archive:
python-mysqldb_1.2.0-4.diff.gz
to pool/main/p/python-mysqldb/python-mysqldb_1.2.0-4.diff.gz
python-mysqldb_1.2.0-4.dsc
to pool/main/p/python-mysqldb/python-mysqldb_1.2.0-4.dsc
python-mysqldb_1.2.0-4_all.deb
to pool/main/p/python-mysqldb/python-mysqldb_1.2.0-4_all.deb
python-mysqldb_1.2.0.orig.tar.gz
to pool/main/p/python-mysqldb/python-mysqldb_1.2.0.orig.tar.gz
python2.3-mysqldb_1.2.0-4_i386.deb
to pool/main/p/python-mysqldb/python2.3-mysqldb_1.2.0-4_i386.deb
python2.4-mysqldb_1.2.0-4_i386.deb
to pool/main/p/python-mysqldb/python2.4-mysqldb_1.2.0-4_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Meurer <[EMAIL PROTECTED]> (supplier of updated python-mysqldb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 26 Mar 2005 16:48:30 +0100
Source: python-mysqldb
Binary: python2.4-mysqldb python-mysqldb python2.3-mysqldb
Architecture: source all i386
Version: 1.2.0-4
Distribution: unstable
Urgency: low
Maintainer: Jonas Meurer <[EMAIL PROTECTED]>
Changed-By: Jonas Meurer <[EMAIL PROTECTED]>
Description:
python-mysqldb - A Python interface to MySQL
python2.3-mysqldb - A Python interface to MySQL
python2.4-mysqldb - A Python interface to MySQL
Closes: 297472 297472 299168 299168 300324 301402
Changes:
python-mysqldb (1.2.0-4) unstable; urgency=low
.
* rebuild with sources included
.
python-mysqldb (1.2.0-3) unstable; urgency=low
.
* python2.4 packages are built (closes: #301402)
* remind scripts to ack NMU (closes: #299168, #297472)
.
python-mysqldb (1.2.0-2) unstable; urgency=low
.
* fix bool convertion: patches/01_converters_boolean
- take boolean vars into account (closes: #300324)
- reintroduced dpatch in build scripts
* add build support for mysql 4.1: patches/02_mysql_41
- simply enable in patches/00list to build packages
with libmysqlclient14-dev from mysql-dfsg-4.1
- disabled by default to prevent segfaults if
used with mysql 4.0 libraries.
.
python-mysqldb (1.2.0-1) unstable; urgency=low
.
* new upstream release
- add 2.4 to, remove 2.2 freom supported python versions,
MySQLdb-Python 1.2.0 doesn't support Python 2.2 any more.
- redesign documentation management as upstream ships a lot
more docs than in previous releases.
* Acknowledge NMU:
- rebuild against libmysqlclient12-dev (closes: #299168, #297472)
Files:
de73be529722721e97f7a142d5ad8fc6 696 python optional python-mysqldb_1.2.0-4.dsc
12012f5dc33bea887cbc65a6a2358912 254659 python optional
python-mysqldb_1.2.0.orig.tar.gz
52d8e6f833ce9dffdd8a435f27c30272 6229 python optional
python-mysqldb_1.2.0-4.diff.gz
ef064ae29b6d11827f974adb1e89cf89 121602 python optional
python-mysqldb_1.2.0-4_all.deb
0540eee48879cb04277e6ff22df53fa8 46064 python optional
python2.3-mysqldb_1.2.0-4_i386.deb
e9fdfcce5de10447a2af21865036d2b9 46060 python optional
python2.4-mysqldb_1.2.0-4_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCRYUvd6lUs+JfIQIRAm3zAJ433axOu3g6/JWtxboRfGe8g4eBBgCeJXpR
aW+D162Cub3KKdAqF+Jpif8=
=7Z6S
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
