Skip to content

Keep poetry.lock modification time newer than pyproject.toml, after relevant commands #7392

@Kache

Description

@Kache
  • I have searched the issues of this repo and believe that this is not a duplicate.
  • I have searched the FAQ and general documentation and believe that my question is not already covered.

Feature Request

After doing operations like add/remove/update that both updates pyproject.toml and refreshes poetry.lock, please complete the operation leaving poetry.lock's modification time to be newer than pyproject.toml's.

Not only is this conceptually proper to match the direction of dependency, it means Makefiles can be used to implement "auto-poetry install if needed" behavior, e.g.:

The comment in #75 suggests this already used to be the case at some point. I'm currently using 1.2.2.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureFeature requests/implementationsstatus/triageThis issue needs to be triaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions