Opened 4 years ago
Last modified 21 months ago
#62296 assigned defect
poetry should be offered as python version-specific packages rather than as variants
Reported by: | LucaFilipozzi (Luca Filipozzi) | Owned by: | dgilman (David Gilman) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.4 |
Keywords: | Cc: | Schamschula (Marius Schamschula), 3add3287 (3add3287) | |
Port: | poetry |
Description (last modified by LucaFilipozzi (Luca Filipozzi))
If a user wishes to install both py37 and py38 (for whatever reason, testing, etc.), if there's a need to use poetry
, then it should be installable as py37-poetry
(providing poetry-3.7
) and py38-poetry
(providing poetry-3.8
), with poetry
selectable via port select
.
Change History (9)
comment:1 Changed 4 years ago by reneeotten (Renee Otten)
Owner: | set to dgilman |
---|---|
Status: | new → assigned |
comment:2 Changed 4 years ago by LucaFilipozzi (Luca Filipozzi)
Description: | modified (diff) |
---|---|
Summary: | poetry should be offered python-specific packages → poetry should be offered as python-specific packages |
comment:3 Changed 4 years ago by LucaFilipozzi (Luca Filipozzi)
Summary: | poetry should be offered as python-specific packages → poetry should be offered as python version-specific packages rather than as variants |
---|
comment:4 Changed 4 years ago by LucaFilipozzi (Luca Filipozzi)
I filed this ticket in response to to ticket:62295.
comment:5 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Implementing this suggestion is required to fix comment:ticket:62682:4.
comment:6 Changed 3 years ago by Schamschula (Marius Schamschula)
Cc: | Schamschula added |
---|
comment:7 Changed 3 years ago by harens (Haren S)
If a user wishes to install both py37 and py38 (for whatever reason, testing, etc.)
Off the top of my head, I can't think of a practical reason why a user would wish to do this since the CLT should be the same regardless.
Implementing this suggestion is required to fix comment:ticket:62682:4.
In regards to py-lexicon
(see #62295 and #62682), poetry shouldn't have been a dependency in the first place. This has been dealt with upstream and should be fixed in the next release (see AnalogJ/lexicon#787 for more details).
As discussed in #62682, both poetry
and py-poetry-core
should rarely (if ever) be required as a dependency in a portfile. In the majority of scenarios, upsteam just hasn't configured poetry properly on their end.
We already have many poetry ports that are working fine without ever needing to reference poetry (e.g. commitizen, py-rich, etc.). I'm therefore in favour of keeping the variants rather than switching to python version-specific packages for the time being.
comment:8 Changed 3 years ago by harens <harensdeveloper@…>
comment:9 Changed 21 months ago by 3add3287 (3add3287)
Cc: | 3add3287 added |
---|
In the future, please add the maintainer to CC (
port info --maintainer poetry
).