| From: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
|---|---|
| To: | Eric Snow <esnow(at)verio(dot)net> |
| Cc: | Jan Urbański <wulczer(at)wulczer(dot)org>, psycopg(at)postgresql(dot)org |
| Subject: | Re: SystemError: null argument to internal routine |
| Date: | 2011-03-08 01:50:14 |
| Message-ID: | AANLkTikR8E1XM5pdd1=9nEt7wF4mdW8mZDkNxWsY6oEh@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
On Mon, Mar 7, 2011 at 11:25 PM, Eric Snow <esnow(at)verio(dot)net> wrote:
> Daniele,
>
> Looks good. However, apparently that wasn't my problem. I am still getting the SystemError for the "null argument to internal routine". Where would be a good place to look for another source of that error in psycopg? I am guessing that that SystemError is a pretty generic one when it comes to python C extensions. Thanks.
If you have applied my patches, probably the problem is not in one of
the pgstatus values not checked, as it would raise a different
exception.
You may build the library using PSYCOPG_DEBUG in setup.cfg, then run
your test with the PSYCOPG_DEBUG environment variable set: this will
spit out plenty of informations about what's currently happening into
psycopg.
Anyway, if you have managed to package a test to reproduce the bug,
that would be more than enough for us to investigate.
Thank you!
-- Danele
| From | Date | Subject | |
|---|---|---|---|
| Next Message | alka sharma | 2011-03-08 09:53:34 | regd installing win-psycopg |
| Previous Message | Eric Snow | 2011-03-07 23:25:52 | Re: SystemError: null argument to internal routine |