X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 4A31A9DC867 for ; Sun, 5 Feb 2006 20:18:44 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 30734-01 for ; Sun, 5 Feb 2006 20:18:46 -0400 (AST) X-Greylist: delayed 00:05:01.974027 by SQLgrey- Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by postgresql.org (Postfix) with ESMTP id 82FF79DC849 for ; Sun, 5 Feb 2006 20:18:41 -0400 (AST) Received: from [84.173.21.192] (helo=[192.168.1.10]) by mrelayeu.kundenserver.de (node=mrelayeu5) with ESMTP (Nemesis), id 0ML25U-1F5u0k1qZS-0001cE; Mon, 06 Feb 2006 01:13:42 +0100 Message-ID: <43E694B6.4040604@online.de> Date: Mon, 06 Feb 2006 01:13:42 +0100 From: Christoph Zwerschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041206 Thunderbird/1.0 Mnenhy/0.6.0.104 MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: PQprint under Windows Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:d4c19f41f9a9703255691874c1441822 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200602/11 X-Sequence-Number: 5975 I tried to compile PyGreSQL under Windows. Everything seems to work, except some functions which are using PQprint. Whenever these functions are called, I get a Windows exception. I am using the following versions: Windows XP SP2 Python: 2.4.2 PostgreSQL 8.1.2 PyGreSQL 3.8 For compilation I used MinGW and Microsoft Visual C++ Toolkit 2003, both work fine, but both have the same problem mentioned above. Can anybody confirm that PQprint is or was ever running under Windows? The 8.1 docu does not say that it is deprecated or not running under Windows. Can it be a bug? I also noticed that the HTML code in PQprint is not very clean and sometimes even wrong, e.g. it has instead of
. -- Christoph