jupyter-fileid script needs click

[frenzymadness]

Description

I've installed jupyter-server-fileid from PyPI and it created an executable file bin/jupyter-fileid. Unfortunately, the script does not work because click is not installed by default.

Reproduce

1. run pip install jupyter-server-fileid
2. run bin/jupyter-fileid

Expected behavior

I can imagine two possible solutions:

1. Add click to the standard dependencies. I've calculated the size of a virtualenv where I installed only jupyter-server-fileid and all its dependencies and it has 66 MB. Adding click there adds only one more MB which is not that big difference.
2. Make it more user-friendly for users. Add try/except to the script and an error message saying that you should install jupyter-server-fileid[cli] or click directly to make it work.

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[dlqqq]

Hm, right now the CLI is mainly intended for developers, which is why we require the explicit [cli] during installation for usage.

#49 will add additional user-facing commands that warrant inclusion of click to the required dependencies. Sadly I haven't had much time to work on that due to a flurry of new responsibilities, but I would be happy to include this change once I return to work on it. 😁

[dlqqq]

Also sorry for the incredibly late response; despite being the creator of this repo, GH defaulted to not notifying me unless explicitly mentioned. I have changed my settings to allow me to be notified and respond more quickly.

[frenzymadness]

Hm, right now the CLI is mainly intended for developers, which is why we require the explicit [cli] during installation for usage.

Then it makes sense. Thanks for the explanation. Do you want to keep this issue open for adding the better error message?

[dlqqq]

Do you want to keep this issue open for adding the better error message?

Yup, I left this issue open intentionally. 😁

[dlqqq]

Well, the error message won't be needed if click becomes installed by default after we add user-facing CLI options.