Spec URL: https://decathorpe.fedorapeople.org/packages/poetry.spec SRPM URL: https://decathorpe.fedorapeople.org/packages/poetry-0.12.11-1.fc29.src.rpm Description: Poetry helps you declare, manage and install dependencies of Python projects, ensuring you have the right stack everywhere. Fedora Account System Username: decathorpe koji scratch build for rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=32193963 Note: This package does probably still require some additional work before it can be accepted. - It includes a self-update function that probably has to be patched out for the fedora package. - poetry seems to produce "setup.py" files that are possibly broken (because they use distutils.core::setup instead of setuptools::setup, but the former doesn't support all the same expected keyword arguments, for example for extra or optional dependencies). This package also depends on my pending reviews for the pylev, pastel, clikit, and cleo python packages.
Taking this review.
What's the benefit towards PyPI and setuptools?
(In reply to Raphael Groner from comment #2) > What's the benefit towards PyPI and setuptools? poetry manages the python package metadata in a machine-readable format (TOML), and allows exporting to the usual "setup.py", i.e. for uploading to PyPI. So it can be used as a "convenience wrapper" around the standard tools. (Neal, please correct me if I'm wrong here.)
(In reply to Fabio Valentini from comment #3) > (In reply to Raphael Groner from comment #2) > > What's the benefit towards PyPI and setuptools? > > poetry manages the python package metadata in a machine-readable format > (TOML), and allows exporting to the usual "setup.py", i.e. for uploading to > PyPI. > So it can be used as a "convenience wrapper" around the standard tools. > (Neal, please correct me if I'm wrong here.) That's basically correct. It replaces conventional setup.py, requirements.txt, Pipfile, Pipfile.lock, etc. with a PEP 518 compliant configuration in pyproject.toml and a simple poetry.lock file for projects that want dependency locking. It supports both virtualenv-oriented stuff (a la pipenv) and normal stuff (a la pip and friends) while also providing backwards compatibility to those tools when you elect to upload your project managed by poetry to PyPI.
(In reply to Neal Gompa from comment #4) > (In reply to Fabio Valentini from comment #3) … Great, thanks for your explanations.
Neal - any progress here?
(In reply to Orion Poplawski from comment #6) > Neal - any progress here? I'm waiting to resolve bug 1666293. Once that's done, I can process the rest of it.
Just FYI, poetry claims to be incompatible with requests-toolbelt >= 0.9.0, and on f30, 0.9.1 is available. I'm not sure if we should continue working on this. The upstream developer acts like he's hostile (or completely indifferent) regarding distribution packaging.
I officially give up, as the upstream developer has not reacted at all to any of of the relevant, open bug reports blocking this package for months. https://github.com/sdispater/poetry/issues/866 https://github.com/sdispater/cachy/issues/2 https://github.com/sdispater/pastel/issues/5 https://github.com/toastdriven/pylev/issues/11