defining entrypoints about move HOT 8 CLOSED

What e.g. git or conda have:

move --help # help move
move encode --help # move command with subcommand encode

from move.

I think using move-dl is fine, it is then also consistent with the pip package

from move.

[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...)

from move.

I added the example on entrypoints: b9e7c2d

from move.

What do you mean by sub-commands here?

from move.

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

from move.

@enryH:

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...)

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.

from move.

🤯 nice that this is solved!

from move.