Skip to content

Switch to hatch as a build backend, environment manager and publishing tool #612

Description

@AnesBenmerzoug

We should consider switching to hatch to simplify our setup and reduce the number of tools we use:

  • setuptools
  • twine
  • tox

See here for a comparison to other tools and reasons for using hatch.

Metadata

Metadata

Assignees

No one assigned

    Labels

    CIGH actions for testing and packagingenhancementNew feature or requestpackagingLibrary packaging and releasing

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions