In a virtualenv of a CentOS 7.1 server, pyq 4.0 failed like this:
/tmp/pyq/lib/python2.7/site-packages/pyq/_k.so: undefined symbol: sd1
Does anyone have a clue how to fix this?
Thank you.
Jin.
Typically people see undefined symbols when trying to import pyq in a plain python. Please use the pyq executable.
If it does not help, please post the full output of “pyq --versions” command.
It indeed was not using pyq. The problem is resolved. Thank you very much.
I met the same problem.
? 2017?3?14??? UTC+8??12:29:44?JM???
It indeed was not using pyq. The problem is resolved. Thank you very much.
JM, How you resolved the problem?
Are you just met the problem at the console side, or in IDE/PyCharm side?
? 2017?3?14??? UTC+8??12:29:44?JM???
It indeed was not using pyq. The problem is resolved. Thank you very much.
Sorry, what’s the meaning of “plain python”?
? 2017?3?12??? UTC+8??2:47:02?Alexander Belopolsky???
Typically people see undefined symbols when trying to import pyq in a plain python. Please use the pyq executable.
If it does not help, please post the full output of “pyq --versions” command.
On Friday, March 17, 2017 at 5:05:51 AM UTC-4, hzad...@gmail.com wrote:
Sorry, what’s the meaning of “plain python”?
By “plain python” I mean the ordinary python executable. When you install PyQ, you get a separate executable, called “pyq” which behaves almost like the ordinary python, but actually is a kdb+ instance running an embedded Python interpreter.
The pyq module cannot be imported in the plain python because it requires access to the C level kdb+ functions such as sd1 which are only available to embedded programs.
Note that the pyq executable is almost equivalent to the “q python.q” command.