Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Proposal] Rename to hatch-jupyter #143

Open
timkpaine opened this issue Jul 9, 2024 · 2 comments
Open

[Proposal] Rename to hatch-jupyter #143

timkpaine opened this issue Jul 9, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@timkpaine
Copy link
Member

timkpaine commented Jul 9, 2024

Problem

This is the de-facto standard Jupyter build plugin for Hatch, but the name is a bit long 😅

Proposed Solution

Rename project and configuration sections to hatch-jupyter. This would also align with the emerging pattern:

Additional context

  • I am happy to do the implementation.
  • I proactively grabbed hatch-jupyter name and added @blink1073 as an owner (feel free to remove me).
  • Will also require renaming/re-adding the conda repo.
@timkpaine timkpaine added the enhancement New feature or request label Jul 9, 2024
@blink1073
Copy link
Contributor

Hi @timkpaine! I personally do not think it is worth the disruption to existing users. We'd also have to update https://blog.jupyter.org/packaging-for-jupyter-in-2022-c7be64c38926.

@Zsailer
Copy link
Member

Zsailer commented Jul 11, 2024

In the Jupyter Server meeting today, we talked about this.

It was mentioned that we could make one last release of hatch-jupyter-builder that depends on the new "hatch-jupyter" with not version pin. That way, folks can still use the old name but it's pulling in the new package to do all the business. Add all kinds of deprecation warnings too.

I'm not sure it's worth the possible headache either, but don't have a strong opinion either way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants