_k.error: scov on pyq start

Questions

• Which operating system are you using (if Linux, please provide flavour of it, i.e RedHat, CentOS or Ubuntu), is it 32-bit, or 64-bit?

  CentOS 64-bit
  

• Which version of PyQ are you running? Please provide output of pyq --versions, if PyQ isn’t operational, please provide Python interpreter version and PyQ version python -V; python3 -V; pip list | grep pyq:

  PyQ is not operational
  Python 3.7.4
  PyQ 4.2.1
  

• Which version of kdb+ are you using, is it 32-bit or 64-bit?

  64-bit 
  

  • If on 64-bit, is your QLIC set? Please provide output env | grep QLIC on linux/macOS, or set|grep QLIC on Windows.

    QLIC=/opt/qb/q3.1
    

• Did you use virtual environment to install PyQ? If not, why?

  Using miniconda
  

• Where is your QHOME? Please provide output env | grep QHOME on linux/macOS, or set|grep QHOME on Windows.

  QHOME=/opt/qb/q3.1
  

• Do you use Conda? If so, what version?

  conda 4.7.10
  

Steps to reproduce the issue

pip install pyq pyq

Expected result

Python terminal prompt

Actual result

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/kgang/.local/lib/python3.7/site-packages/pyq/__init__.py", line 733, in <module>
    q = _Q()
  File "/home/kgang/.local/lib/python3.7/site-packages/pyq/__init__.py", line 701, in __init__
    [name for name, _ in _q_builtins()])
  File "/home/kgang/.local/lib/python3.7/site-packages/pyq/__init__.py", line 634, in _q_builtins
    pairs.append((attr, q(x)))
  File "/home/kgang/.local/lib/python3.7/site-packages/pyq/__init__.py", line 614, in q
    return K._k(0, x)
_k.error: scov
'2019.09.13T11:14:27.195 python
@
"k"
"p)from pyq import q"

[perfecto25]

Just adding in case anyone hits this issue running KDB 3.1

all you need to do is adjust this line for version import,

vi /home/user/py3/lib64/python3.6/site-packages/pyq/__init__.py

#line 624
# change kver to 3.2

    if kver < 3.2:
        for new in ['scov', 'svar', 'sdev']:
            names.remove(new)

[sashkab]

This has been resolved internally. Expected fix will be released in PyQ 5.0.