Need to work with psycopg2ct to get going on PyPy
Bug #944770 reported by
Jamu Kakar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Storm |
New
|
Undecided
|
Unassigned |
Bug Description
I tried to get Storm working with PyPy and psycopg2ct but ended up
running into issues because we reach into psycopg2._psycopg in various
places and this doesn't exist in psycopg2ct.
Related branches
To post a comment you must log in.
I can see this happening in a couple of places:
storm/databases /postgres. py:
> if psycopg2 is not dummy: extensions. register_ type(psycopg2. extensions. UNICODE) extensions. register_ type(psycopg2. _psycopg. UNICODEARRAY)
> psycopg2.
> psycopg2.
tests/databases /postgres. py:
> if has_psycopg: _psycopg. __version_ _.split( None, 1)[0] stopped. skip = ( /bugs.launchpad"
> import psycopg2._psycopg
> psycopg2_version = psycopg2.
> if psycopg2_version in ("2.4", "2.4.1", "2.4.2"):
> test_pgbouncer_
> "Fails with pyscopg2 %s; see https:/
In both case these tricks are no longer necessary, with psycopg2 2.4.4
on Precise at least:
- The UNICODEARRAY type is now in psycopg2. extensions.
- psycopg2. __version_ _ is now available.
However, I don't know if these changes are reflected in psycopg2ct.