as far as I remember, C extension in reportlab is optional. Just disable it. If it's there for speedups, it's very likely it slows things down on pypy. Reference count is a fake thing on pypy, don't use it if you can help it. builtin codes have no filename, you have to somehow deal with it. I think the problem comes from a fact that on cpython builtin functions don't have code. On Mon, Nov 23, 2015 at 2:47 PM, Robin Becker <robin@reportlab.com> wrote:
I hope this is the right place to ask, but if not just tell me to go away.
At the request of a user I'm trying to get reportlab up to scratch for pypy. I have some fairly insignificant bugs in the tests related to Cpython-pypy differences and one C extension that crashes.
Firstly what is the best way to approach debugging an extension segfault. Do I need to build pypy with debugging turned on or can I just build the extension like that?
Are there any guidelines for making c extensions pypy friendly?
Secondly how to cope with some fairly simple testing problems. One of my extensions appears to work, but clearly attempting to verify reference counts is failing
ie from sys import getrefcount, _getframe
doesn't work. I suppose there's no real point in trying to figure out refcounts for pypy.
I have some errors related to co_filename eg
if os.path.splitext(obj.__code__.co_filename)[0]==modBn: AttributeError: 'builtin-code' object has no attribute 'co_filename'
but it's not clear to me if it's even possible to get the filename.
Lastly what is the right way to get the platform as pypy not cpython? -- Robin Becker _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev