Package Details: python-poethepoet 0.34.0-1

Git Clone URL: https://aur.archlinux.org/python-poethepoet.git (read-only, click to copy)
Package Base: python-poethepoet
Description: A task runner that works well with poetry
Upstream URL: https://github.com/nat-n/poethepoet
Licenses: MIT
Submitter: carlosal1015
Maintainer: carlosal1015
Last Packager: carlosal1015
Votes: 1
Popularity: 0.003625
First Submitted: 2023-04-01 04:15 (UTC)
Last Updated: 2025-04-26 01:33 (UTC)

Latest Comments

SpotlightKid commented on 2025-02-11 20:00 (UTC) (edited on 2025-02-11 20:02 (UTC) by SpotlightKid)

I would suggest option 2, since this project has not been tested or build with the intention of using poetry 2.0

I would agree with the conclusion, but what do you mean by "this project"? Or did you mean to say "poetry < 2.0"?

thatch45 commented on 2025-02-11 19:37 (UTC)

Upstream is right to not want to comply here, they are compatible with poetry 2.0 and greater. I would argue that they should match a breaking change in the build process with a major release number but I don't think that is my call to make.

Until poetry is updated to 2.0 in the extra repo I would do one of these two things: 1. For now I would suggest either patching the pyproject.toml to include the tool.poetry section 2. Revert to a version that did not have a hard dep on poetry 2

I would suggest option 2, since this project has not been tested or build with the intention of using poetry 2.0

Thank you for your work! Keep it up!

fridge commented on 2025-02-02 15:26 (UTC)

I opened an issue in the upstream GitHub repository: https://github.com/nat-n/poethepoet/issues/275

irashid commented on 2025-02-02 09:45 (UTC) (edited on 2025-02-02 09:54 (UTC) by irashid)

i edited pyproject.toml and add section :


[tool.poetry]
name = "poethepoet"
version = "0.32.2"
description = "A task runner that works well with poetry."
authors = ["Nat Noordanus <n@noordan.us>"]
readme = "README.md"
license = "MIT"
repository = "https://github.com/nat-n/poethepoet"
homepage = "https://github.com/nat-n/poethepoet"
documentation = "https://poethepoet.natn.io/"
keywords = ["automation", "tasks", "task-runner", "plugin", "poetry", "poe"]
classifiers = ["Topic :: Software Development :: Build Tools"]

under the project section then save and update tar.gz file. then


1. makepkg -g
2. updpkgsums
3. makepkg
4. pacman -U python-poethepoet

solved the problem

SpotlightKid commented on 2025-01-31 13:42 (UTC)

Same here. Maybe upstream introduced an incompatibility with poetry < 2.0?

fridge commented on 2025-01-31 09:55 (UTC)

Version 0.32.2-1 does not build on my system. Could this be a common problem?

Building python-poethepoet...
==> Making package: python-poethepoet 0.32.2-1 (Fr 31 Jan 2025 10:51:44 CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found poethepoet-0.32.2.tar.gz
==> Validating source files with sha512sums...
    poethepoet-0.32.2.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting poethepoet-0.32.2.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
* Building wheel...
Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/pyproject_hooks/_in_process/_in_process.py", line 389, in <module>
    main()
  File "/usr/lib/python3.12/site-packages/pyproject_hooks/_in_process/_in_process.py", line 373, in main
    json_out["return_val"] = hook(**hook_input["kwargs"])
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/pyproject_hooks/_in_process/_in_process.py", line 280, in build_wheel
    return _build_backend().build_wheel(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/poetry/core/masonry/api.py", line 55, in build_wheel
    poetry = Factory().create_poetry(Path(".").resolve(), with_groups=False)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/poetry/core/factory.py", line 60, in create_poetry
    raise RuntimeError("The Poetry configuration is invalid:\n" + message)
RuntimeError: The Poetry configuration is invalid:
  - The fields ['authors', 'description', 'name', 'version'] are required in package mode.

ERROR Backend subprocess exited when trying to invoke build_wheel
==> ERROR: A failure occurred in build().
    Aborting...

bcb commented on 2024-10-09 09:44 (UTC)

python-poetry-core needs to be a makedepends, it doesn't build without it.

rid9 commented on 2023-09-14 17:03 (UTC)

Build is failing for 0.22.1-1 because the tarball root folder is back to not using v as version prefix