The following procedures produced the l64 binaries of PyQ on CentOS7. How can I get the l32 binaries? How can I get it without root? Thx.
============================
http://code.kx.com/wiki/Contrib/PyQ
login as root
unzip kdb to /root/q
easy_install pip
pip install -i https://pypi.enlnt.com pyq
./python.q
./p.k
./l64/py.so
./l64/p.so
On Sunday, February 1, 2015 at 7:33:11 AM UTC-5, Yan Yan wrote:
The following procedures produced the l64 binaries of PyQ on CentOS7. How can I get the l32 binaries? How can I get it without root? Thx.
You can find instructions at <http://stackoverflow.com/a/24268143\>.
Thx. I think your suggestion should work in python 32 bit. But that would be limited by the 32 bit address space. I have just found that qPython is a native python driver that works w/o any C++ bridge. And it worked on centos7 + python 64 bit ^_^
On Thursday, February 5, 2015 at 7:46:45 PM UTC-5, Yan Yan wrote:
Thx. I think your suggestion should work in python 32 bit. But that would be limited by the 32 bit address space. I have just found that qPython is a native python driver that works w/o any C++ bridge.
PyQ and qPython solve two different problems. qPython is a Python client for kdb+, while PyQ is Python running inside the kdb+ process.
Take a look at the access times for PyQ: <https://pyq.enlnt.com/slides/#/4\>. I bet you won’t achieve that with any client-side solution.
Alex: Your response to the “Sorting half of a list” is quite interesting ^_^
IIRC I have compiled PyQ on centos6.6 32 bit, copied the binaries to centos6.6 64 bit, and ran kdb 32 bit embedded in python 64 bit. I have yet to try that on centos7 64 bit. Cross-compiling requires a bit of work.
Does the embedded kdb in PyQ listen on any network port? Thx.