| 1 |
Hi, |
| 2 |
|
| 3 |
Pathlib2 is a backport, as such it doesn't really make sense to add 3.10 and 3.11 to compat. The package from the overlay probably should adjust its dependencies to only depend on pathlib2 when instaling for 3.9 or 3.8. This can be accomplished with the python_gen_cond_dep function (see docmenttion of python-r1.eclass). |
| 4 |
|
| 5 |
Best regards, |
| 6 |
Andrew |
| 7 |
|
| 8 |
|
| 9 |
On December 2, 2022 10:04:02 AM GMT+01:00, Martin Kletzander <nert.pinx@×××××.com> wrote: |
| 10 |
>Hi all, |
| 11 |
> |
| 12 |
>I noticed that a package from an overlay fails to install due to it |
| 13 |
>requiring pathlib2 with python_targets with 3.10 and/or 3.11. So I |
| 14 |
>checked pathlib2's setup.py [0] that it supports newer python versions |
| 15 |
>and wanted to update the ebuild, but noticed |
| 16 |
> |
| 17 |
>My question is whether I should: |
| 18 |
> |
| 19 |
>1) do some more research/work to bump the versions or |
| 20 |
> |
| 21 |
>2) update the upstream in case this is something deprecated order |
| 22 |
> |
| 23 |
>3) whether the updated ebuild with newer python versions should live in |
| 24 |
> the overlay instead. |
| 25 |
> |
| 26 |
>Thanks for any (non-null) pointers, |
| 27 |
>Martin |
| 28 |
> |
| 29 |
>[0] https://github.com/jazzband/pathlib2/blob/develop/setup.py#L39 |
| 30 |
> |
Archives