Skip to content

missing pyproject.toml #211

Closed
Closed

Description

@ymahlich

When installing a python package locally via pip that I actively develop on I prefer doing so via pip install -e/--editable <path-to-local-git-repo>. This allows me to being able to import the package from anywhere without having to reinstall it after every change.

setuptools / setup.py is being deprecated. pip recommends switching to a pyproject.toml.

I don't think this is necessarily urgent, but maybe something to keep in the back of our heads.

Activity

  1. ymahlich commented on Oct 28, 2024

    @ymahlich
    CollaboratorAuthor

    Putting together another package and making it ready for distribution I came across this: https://hatch.pypa.io/1.8/
    Might be useful for creating the pyproject.toml (see more details here: https://hatch.pypa.io/1.8/intro/#existing-project).
    As far as I understand it it should be able to just use a preexisting setup.py and essentially translates that into a pyproject.toml which will be the way pip will be installing software in the future.

  2. jjacobson95 commented on Nov 13, 2024

    @jjacobson95
    Collaborator

    We will have to update scripts/push_to_pypi.py.py as well. This is where the package is built before pushing it to pypy in the build_all.py script

  3. moved this to Ready in CoderDataon Nov 22, 2024
  4. moved this from Ready to In progress in CoderDataon Dec 18, 2024
  5. linked a pull request that will close this issue211 missing pyprojecttoml #273on Dec 18, 2024
  6. moved this from In progress to Done in CoderDataon Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions