Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#64484 - [poetry] needs update for Python 3.8

Attached to Project: Community Packages
Opened by Daniel Schopf (dschopf) - Wednesday, 13 November 2019, 08:27 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 24 November 2019, 02:44 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Eli Schwartz (eschwartz)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

Running poetry with Pyhton 3.8 fails:

$ poetry
Traceback (most recent call last):
File "/usr/bin/poetry", line 8, in <module>
from poetry.console import main
File "/usr/lib/poetry/poetry/console/__init__.py", line 1, in <module>
from .application import Application
File "/usr/lib/poetry/poetry/console/application.py", line 6, in <module>
from cleo import Application as BaseApplication
ModuleNotFoundError: No module named 'cleo'

Support for Python 3.8 has been added in poetry 1.0.0b2 (released Oct 11).

This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Sunday, 24 November 2019, 02:44 GMT
Reason for closing:  Fixed
Comment by Eli Schwartz (eschwartz) - Thursday, 14 November 2019, 15:54 GMT
This happens because poetry vendors dependencies in a really bad manner, and then inserts them onto the PYTHONPATH using the python version major.minor. I've been working on packaging the dependency tree properly... some things are now packaged, let me see if I can finally get this complete now!

...

I sort of don't like the idea of packaging beta releases for a semver major update just to get some vendored dependencies in the correct directory. Let's see if we can do better. ;)
Comment by Guillaume gauvrit (mardiros) - Friday, 15 November 2019, 12:57 GMT
```
$ pacman -Ql poetry | grep --color=never _vendor/py3 | awk '{print $2}' | awk -F'/' '{print $7}' | uniq
py3.4
py3.5
py3.6
py3.7
```

So, the PKGBUILD for poetry https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/poetry

download the file https://github.com/sdispater/poetry/releases/download/0.12.17/poetry-0.12.17-linux.tar.gz

https://github.com/sdispater/poetry/releases/tag/0.12.17

and this file does not contains py3.8...

Here is a quickfix:
```
guillaume:~ 𝝿 sudo pacman -S poetry
...
guillaume:~ 𝝿 cd /usr/lib/poetry/poetry/_vendor/py3.7
guillaume:/usr/lib/poetry/poetry/_vendor/py3.7 𝝿 cd ..
guillaume:/usr/lib/poetry/poetry/_vendor 𝝿 sudo ln -s py3.7 py3.8
guillaume:/usr/lib/poetry/poetry/_vendor 𝝿
guillaume:/usr/lib/poetry/poetry/_vendor 𝝿 ls
py2.7 py3.4 py3.5 py3.6 py3.7 py3.8
guillaume:/usr/lib/poetry/poetry/_vendor 𝝿 poetry
Poetry 0.12.17

Usage:
command [options] [arguments]

...

```



Comment by Eli Schwartz (eschwartz) - Tuesday, 19 November 2019, 16:28 GMT
I've just uploaded python-poetry 0.12.17-1 to community, which will replace 'poetry'. This completes a long-term goal I had agreed upon with svenstaro: the package now uses the same pkgname style as other python ecosystem tools like pip, and, relevant to this bug, it builds from source and uses system-packaged versions of its dependencies rather than vendoring a copy for every single python release other than the one archlinux actually provides. ;)

We're now also running the project unittests, and overall we should be much better able to cope with new versions of python and stuff. Try it out!
Comment by Daniel Schopf (dschopf) - Friday, 22 November 2019, 15:27 GMT
Basic testing didn't show any issues so far, thanks for the update.
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 24 November 2019, 02:44 GMT
Thanks a ton, Eli.

Loading...