Closed chazeon closed 6 years ago
That was actually the first implementation of the qha/scripts/qha
, I wrote something as qha/__main__.py
. But later on I referred this, and decided to use a scripts
folder and add them into setup.py
. I think this is more intuitive to me. Do you have any problem of installing those scripts? I think
When we install the package, setuptools will copy the script to our PATH and make it available for general use.
according to the doc I pasted. And it is verified by me.
Well, I think we could keep them both.
The script installed fine, they are copied to the righteous position, but under Windows, there is no way to start them directly because the way of open the file is determined based on extension, and that's what these two guys doesn't have.
Could you please check whether bracnch release/v1.0.1
help to solve this issue? @chazeon
Bracnch release/v1.0.1
resolves this issue.
Thanks!
Something to consider: we could follow Python's official packages' organization in order that they can be more easily invoked. Good examples are
http.server
andpip
, they could both be invoked withpython -m
, like:or
and
pip
could also be invoked as scripts under Unix based system. To allowpython -m
, we could move the main part ofscripts/qha
toqha/__main__.py
, andscripts/qha-convert
toqha/convert.py
, thus they would be runnable useor
and create the scripts at the old places to invoke those two scripts.
We could refer to distributions of the official packages as examples.