Feat: move to hatchling?

[agoose77]

I am aware that @blink1073 has been looking into using hatch for building e.g. nbconvert.

I've also used it to write my own build plugin, and it's very easy to use. Given that hatch already supports PEP 621, PEP 517, PEP 660 et al, we'd be getting a lot of nice features up front.

Relevant Issues:

• Support PEP660 - editable installation #103
• Add more declarative config #119
• Switch away from setup.cfg when available #122

[blink1073]

Hi @agoose77, I'm actually already testing out a plugin in jupyter/notebook#6425. My goal is indeed to have that replace our use of jupyter-packaging across the board.

[blink1073]

cf jupyterlab/frontends-team-compass#146

[ofek]

This is done I think

[jasongrout]

Just to be clear, if the hatch solution pans out, is the plan to sunset this project and eventually archive it?

[blink1073]

Just to be clear, if the hatch solution pans out, is the plan to sunset this project and eventually archive it?

Yes, that is correct

[ofek]

Has the blog post been released yet?

[blink1073]

Not yet 😅. I'm tracking the migration effort in jupyterlab/hatch-jupyter-builder#54