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

pyproject.toml entry-points isn't parsed correctly #2885

Closed
2 tasks done
atmorling opened this issue Jan 13, 2025 · 2 comments · Fixed by #2886
Closed
2 tasks done

pyproject.toml entry-points isn't parsed correctly #2885

atmorling opened this issue Jan 13, 2025 · 2 comments · Fixed by #2886

Comments

@atmorling
Copy link
Contributor

Checks

  • I have checked that this issue has not already been reported.

  • I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

[project]
description = "A description"
name = "test"

[project.entry-points.entry]
entry = "some.entry
$ pixi install --manifest-path pyproject.toml
Error:
  × Unexpected keys, expected only 'name', 'version', 'description', 'readme', 'requires-python', 'license', 'license-files', 'authors', 'maintainers', 'keywords', 'classifiers', 'urls', 'entry_points',
  │ 'scripts', 'gui-scripts', 'dependencies', 'optional-dependencies', 'dynamic'
   ╭─[pyproject.toml:5:10]
 4 │
 5 │ [project.entry-points]
   ·          ──────┬─────
   ·                ╰── 'entry-points' was not expected here
 6 │ entry = "some.entry"
   ╰────
  help: Did you mean 'entry_points'?

Issue description

This is new in 0.40.0, downgrading to 0.39.5 fixes the issue.

Per the error, updating pyproject.toml to use entry_points instead also works.

Expected behavior

Raising this as a bug because this should be allowed per the pyproject.toml spec

As hinted by the error message, pretty sure that this line


should be entry-points

@baszalmstra
Copy link
Contributor

Jep! Thats a bug! Would you be able to open a PR?

@atmorling
Copy link
Contributor Author

Sure thing!

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 a pull request may close this issue.

2 participants