cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end ) | use cffi for calling C | if a pep adds a mere 25-30 [C-API] functions or so, it's a drop in the ocean (cough) - Armin
isidentical has quit [Remote host closed the connection]
isidentical has joined #pypy
muke has joined #pypy
<muke>
Hey, just installed pypy on my gentoo system, and was just a little curious, is there a way to have pypy use my package manager's numpy build rather than downloading a seperate one through pypy's pip?
jcea has joined #pypy
<antocuni>
muke: nope
<antocuni>
numpy is written in C and C extensions must be compiled separately for every python version/implementation
<muke>
antocuni fair enough, is there a way to have it compile from source instead?
<muke>
it's not especially important i'm just wondering
<antocuni>
pypy -m pip install numpy should "just work"
<muke>
it does work yea
<muke>
but if i can compile it from source i can add custom optimisations
<antocuni>
pip install DOES compile from source. If you want to compile from source by yourself you can get a numpy tarball or a git checkout and fiddle with setup.py
<antocuni>
but this is more a numpy question than a pypy one
<muke>
well for any package i compile how would i install that into pypy after building it?
<antocuni>
pypy is not different than CPython in this respect
<antocuni>
to install packages, you can either use pip or running setup.py directly
<muke>
right ok, thanks
isidentical has quit [Quit: isidentical]
<LarstiQ>
and virtual envs of course to separate environments/use different pythons
isidentical has joined #pypy
lritter has joined #pypy
muke has quit [Quit: Leaving]
otisolsen70_ has joined #pypy
otisolsen70 has quit [Ping timeout: 264 seconds]
otisolsen70_ has quit [Quit: Leaving]
<tos9>
I guess this may be a C or gcc question more than a CFFI one but... "relocation R_X86_64_PC32 against symbol `avifImageCreate' can not be used when making a shared object; recompile with -fPIC"
<tos9>
what does this mean -- I see literally a line before that gcc is compiling the cffi .so with -fPIC
<tos9>
It means the thing it's linking against needs -fPIC?
<LarstiQ>
tos9: oof, been a while. I guess if you're linking against something that isn't position independent the entire -fPIC game falls apart?
<tos9>
LarstiQ: meaning it's telling me I didn't properly compile the first thing position-independent, right?
<tos9>
(I mean, I didn't do anything, I ran cmake, so will have to see what I did...)
<tos9>
ok I guess that makes sense as an error message, I mean it's telling me what symbol it's looking at, let's see...
<tos9>
yeah me removing BUILD_SHARED_LIBS when calling cmake appears to make that go away, which I thought I wanted to get a statically linked thing, but maybe I don't know what I'm doing. Think things are working now.
<tos9>
all this works easily on macos, clearly everyone should ditch this linux thing
isidentical has quit [Quit: isidentical]
marky1991 has joined #pypy
krono has quit [Quit: Connection closed for inactivity]
<marky1991>
hmm, there's some strange code in array_slice_setitem in ctypes that i don't get
<marky1991>
let me see if it's pypy3.7 specific...
<marky1991>
but given a slice like this some_array[::2], for a length 56 list, it's coming up with 28.5, which causes an exception.