Thanks, I now understand what pathlib2 does, but more importantly found
out it is not really needed in that case making the fix even easier =)
On Fri, Dec 02, 2022 at 11:35:06AM +0100, Andrew Ammerlaan wrote:
Hi,
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).
Best regards,
Andrew
On December 2, 2022 10:04:02 AM GMT+01:00, Martin Kletzander
<nert.p...@gmail.com> wrote:
Hi all,
I noticed that a package from an overlay fails to install due to it
requiring pathlib2 with python_targets with 3.10 and/or 3.11. So I
checked pathlib2's setup.py [0] that it supports newer python versions
and wanted to update the ebuild, but noticed
My question is whether I should:
1) do some more research/work to bump the versions or
2) update the upstream in case this is something deprecated order
3) whether the updated ebuild with newer python versions should live in
the overlay instead.
Thanks for any (non-null) pointers,
Martin
[0] https://github.com/jazzband/pathlib2/blob/develop/setup.py#L39
