Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Encountered During poetry install -vvv - pyproject.toml Changed Since poetry.lock Was Last Generated #7

Open
Flemington7 opened this issue Jan 20, 2025 · 1 comment

Comments

@Flemington7
Copy link

Description:
Hi team,

I encountered an error while running poetry install -vvv in the project setup. The error message indicates that the pyproject.toml file has changed significantly since the poetry.lock file was last generated.

Steps to reproduce:

  1. Clone the repository.

  2. Navigate to the project directory.

  3. Run the following command:

    poetry install -vvv
  4. Encounter the following error message:

    pyproject.toml changed significantly since poetry.lock was last generated. Run `poetry lock` to fix the lock file.
    

Expected behavior:

The poetry install -vvv command should install the dependencies without errors, ensuring the project is set up correctly.

Actual behavior:

The installation fails with the error mentioned above.

Suggested action:

To resolve the issue, it seems necessary to run the poetry lock command to regenerate the poetry.lock file. Please run the following command:

poetry lock

This should update the lock file and allow the installation to proceed correctly.

System Information:

  • Poetry version: Poetry (version 2.0.1)
  • Python version: Python 3.12.3
  • Operating System: Ubuntu 24.04.1 LTS (WSL 2 on Windows)
  • Poetry installation method: pipx
  • Plugin installation method: pipx inject

Additional context:

The issue may have been caused by changes in pyproject.toml without updating the poetry.lock file. Running poetry lock should update the lock file, resolving the mismatch.

@JacksonArthurClark
Copy link
Collaborator

@Flemington7

Yes, we're aware of this issue and our fix was the same. Let me know if you have any trouble getting things to run or if you have any questions.

JacksonArthurClark pushed a commit that referenced this issue Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants