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
<dholth>
I am also becoming a bitbucket fugitive, went to the dark side (github)
<dholth>
How do you set a virtualenv when importing a cffi embedding-mode module
<dholth>
or dlopen'ing it from c
<mattip>
don't you have to make sure libpypy-c or libpython are on your path before runnint the exe?
<mattip>
so just make sure the right one is on the PATH
<dholth>
ldd says libpypy3-c.so => /home/dholth/prog/uwsgi/.venv/bin/libpypy3-c.so but sys.executable is set to '*' and only the base installation gets on sys.path
lritter has joined #pypy
<dholth>
I'm sure the answer is in the existing uwsgi pypy plugin
<dholth>
pypy_setup_code from libpypy-c
<dholth>
pypy_setup_home probably
xcm has quit [Remote host closed the connection]
xcm has joined #pypy
xcm has quit [Remote host closed the connection]
xcm has joined #pypy
<dholth>
Oh, super easy, the cwd has to be inside the venv, then pypy will use that.
<dholth>
When embedded in a C program
xcm has quit [Remote host closed the connection]
xcm has joined #pypy
<mattip>
cfbolz: when you have a chance could you merge default to py3.6 - optimize-sre-unicode creates some conflicts