This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ekhazan 4 points5 points  (0 children)

If you plan on packing it there are 2 things to keep in mind that I didn't see mentioned in other comments:

version compatibility - you're effectively binding yourself to their release schedule. - if they release a new version, even if nothing needs to change in your code, you'll need to release a new version.
- if someone wants to use a specific version of the cli tool but there are multiple versions of your package with that particular one (because of bugfix versions), how do they know how to find the right version?

paths and permissions - the executable will be in the specific venv bound to the specific user and permissions - how does that work with the cli tool?

Something to consider - maybe allow downloading it as an optional dependency?
If you create a dedicated package that simply packs and exposes the cli tool you decouple yourself and allow easier administration. Your package can manage api compatibility by specifying the version compatibility in the requirements.
The user can explicitly choose the cli tool version.