Skip to content

export command under current project generates poetry.lock #81

@shawnzhu

Description

@shawnzhu

see below version numbers:

$ poetry self show plugins

  - poetry-plugin-shell (1.0.1) Poetry plugin to run subshell with virtual environment activated
      1 application plugin

      Dependencies
        - pexpect (>=4.7.0,<5.0.0)
        - poetry (>=2.0,<3.0)
        - shellingham (>=1.5,<2.0)

  - poetry-monoranger-plugin (0.4.1) Monoranger is a plugin for Poetry that helps you manage your monorepo, enabling shared lockfiles and virtual environments.
      1 application plugin

      Dependencies
        - poetry (>=1.8.0)

  - poetry-plugin-export (1.9.0) Poetry plugin to export the dependencies to various formats
      1 application plugin

      Dependencies
        - poetry (>=2.0.0,<3.0.0)
        - poetry-core (>=1.7.0,<3.0.0)

Problem

when running poetry export under /monorepo/foo/libarary-a/, it generates a poetry.lock file:

$ poetry export > requirements.txt
The lock file does not exist. Locking.

I got the impression that it will reuse the shared poetry.lock from the root directory.

BTW, poetry export doesn't work (showing `` ) under a current project until running either poetry install or `poetry sync`, which I usually run under the root directory only.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions