Closed enryH closed 1 year ago
[options.entry_points]
console_scripts =
move-dl=move.__main__:main
move-dl-encode-data=move.encode_data.__main__:main
if I name the target move
I somehow get an error, I don't get: The system cannot find the file specified.
(so if move=move.__main__:main
it somehow has errors...)
I added the example on entrypoints
: https://github.com/RasmussenLab/MOVE/commit/b9e7c2d1dbfbcfa18804bd46ae1523a2848af1af
What e.g. git or conda have:
move --help # help move
move encode --help # move command with subcommand encode
Alternatively, what about adding a keyword that specifies what to do?
move mode=encode
move mode=optimize_reconstruction
move mode=optimize_stability
move mode=analyze_latent
move mode=get_associations
@enryH:
if I name the target
move
I somehow get an error, I don't get:The system cannot find the file specified.
(so ifmove=move.__main__:main
it somehow has errors...)
It's a Windows-specific problem. The issue is that move
is an internal Windows command (similar to mv
in Unix), and setuptools cannot override it.
A different name has to be used then, so I will stick with move-dl
for now.
🤯 nice that this is solved!
I think using move-dl
is fine, it is then also consistent with the pip package
I tried out of curiosity to define an entrypoint in
setup.cfg
, and I ran in an error regarding the uncommon module naming conventionChanging the module name from
01_encode_data
toencode_data
(and changingsetup.cfg
accordingly, solves the problem