On 13/11/2012, Nick Fankhauser <[email protected]> wrote: > Hi! > > I'm trying to compile one of my python applications using "translate.py". > Because the application needs access to postgreSQL, it's using pypq. The > application runs fine in python, and pypy as well. > Using the error messages from translate.py, I made a lot of changes to > my program to make it as much RPython as I can make it. > > But even after changing the code many, many times, I never get past the > following error message. It's from pypq and I'm not sure what command in > my application triggers the error, but by looking at the pypq source, I > assume it's from a pypq-"commit" command.
The pypy translation toolchain has never been intended to support translation of end-user programs. If at all possible, use the pypy python interpreter. It's often faster than rpython for real-world code, and a lot easier to use, too. > My questions are: > - Is it even possible to use pypq in RPython? No, it uses ctypes, which is only available at app-level. > - If not, is there any other postgreSQL adapter that works? No, you will have to use a low-level C interface; there are examples of this in pypy/modules. (I think this answers the remaining questions.) -- William Leslie _______________________________________________ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
