Open InCogNiTo124 opened 2 years ago
Hi, there's some kind of misalignment there with relation to the fact of whether bin is a folder or a package.
I haven't solved it completely in the last release, as I was focusing on making the q standalone executable using pyoxidizer.
Can you describe the reasons you need it? Is it for actually using q on a machine, or is it for development purposes?
Harel
I was just trying alternative running options. The official ubuntu release seemed a bit outdated and I was reluctant to build my own dpkg from master
so I tried cloning the repo and installing it locally. I don't need need it, but I stil felt I should report this
msmetko
FWIW, just changing console_scripts
to q = q:run_standalone
isn't great. it works after installing, but then
$ pip3 uninstall q
Found existing installation: q 3.1.6
Uninstalling q-3.1.6:
Would remove:
/Users/raylu/venv/bin/q
/Users/raylu/venv/lib/python3.9/site-packages/*
Would not remove (might be manually added):
/Users/raylu/venv/lib/python3.9/site-packages/_distutils_hack/__init__.py
/Users/raylu/venv/lib/python3.9/site-packages/_distutils_hack/override.py
[a looong list of every single file in site-packages]
/Users/raylu/venv/lib/python3.9/site-packages/zipp/glob.py
/Users/raylu/venv/lib/python3.9/site-packages/zipp/py310compat.py
Proceed (Y/n)?
adding py_modules=['q']
is one way to fix uninstallation
Steps to reproduce:
The solution is line
setup.py:L28
:'q = bin.q:run_standalone' -> 'q = q:run_standalone'