Skip to content

fix: Make poetry.lock and pyproject.toml compatible with current poetry#51

Open
esafak wants to merge 1 commit intohackersandslackers:masterfrom
esafak:fix/update_pyproject_lock
Open

fix: Make poetry.lock and pyproject.toml compatible with current poetry#51
esafak wants to merge 1 commit intohackersandslackers:masterfrom
esafak:fix/update_pyproject_lock

Conversation

@esafak
Copy link
Copy Markdown

@esafak esafak commented Aug 3, 2025

The tutorial was not working with the current version of poetry:

> poetry install

The Poetry configuration is invalid:
  - tool.poetry.homepage must be uri

and once I fixed that:

> poetry install

The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.
Creating virtualenv poetry-tutorial-project-jvvTWLCy-py3.13 in /Users/emre/Library/Caches/pypoetry/virtualenvs
Installing dependencies from lock file

The lock file is not compatible with the current version of Poetry.
Regenerate the lock file with the `poetry lock` command.
  • Update poetry.lock with new dependency versions and hashes.
  • Update pyproject.toml to reflect new dependency structure for dev dependencies.
  • Add project homepage URL to pyproject.toml.
  • Add typing-extensions to dev dependencies in pyproject.toml.
  • Update to latest versions of several development dependencies.

In addition, I would like to draw your attention to another fork that adds testing.

* Update poetry.lock with new dependency versions and hashes.
* Update pyproject.toml to reflect new dependency structure for dev dependencies.
* Add project homepage URL to pyproject.toml.
* Add typing-extensions to dev dependencies in pyproject.toml.
* Update to latest versions of several development dependencies.
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Aug 3, 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

Successfully merging this pull request may close these issues.

1 participant