>> Lastly what is the right way to get the platform as pypy not cpython?
>> --
>> Robin Becker
Maciej already answered the other stuff. I had pypy working with
reportlab a long time ago just by not using the C extensions at all.
Detecting pypy is a bit harder.
https://www.python.org/dev/peps/pe
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
thi
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
Hi Anto,
> On 22.11.2015, at 12:10, Antonio Cuni wrote:
>
> 1) I know that ARM CPUs can be either little or big endiam. What is the case
> for our armhf machine?
Our builders are all little endian. To my knowledge most (maybe all) Linux
distributions for ARM are little endian nowadays.
>
>
