Visitar URL original
Update license specifier in pyproject.toml · Issue #1793 · NeuralEnsemble/python-neo · GitHub
Skip to content

Update license specifier in pyproject.toml #1793

Closed

Description

@zm711

Please note that as of PEP639 we need to specify our license differently

https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license

min version of Setuptools for this is 77 so we should discuss whether we want to update our build dependency to that.

Activity

  1. changed the title [-]Update license[/-] [+]Update license specifier in pyproject.toml[/+] on Oct 13, 2025
  2. h-mayorquin commented on Oct 22, 2025

    @h-mayorquin
    Contributor

    I am +1 for just setting a higher floor for setuptools. This should not affect users as the backend is built in isolation and we don't really use any new feature.

    Or, if we are ambitious we could move to hatchling which I would prefer.

  3. zm711 commented on Nov 8, 2025

    @zm711
    ContributorAuthor

    Sounds good to me. I can make that PR shortly. Just so I feel like I can still contribute. :)

  4. samuelgarcia commented on Nov 14, 2025

    @samuelgarcia
    Contributor

    Or, if we are ambitious we could move to hatchling which I would prefer.

    You wanted to move toward uv for building no ?

  5. h-mayorquin commented on Nov 15, 2025

    @h-mayorquin
    Contributor

    Not really, uv would be sweet on the CI to make installation faster but for building I don't care too much as long as we move away from setuptools.

  6. added this to the 0.14.4 milestone on Dec 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions