[Bug 269209] devel/py-packaging: Update to 23.0

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 28 Jan 2023 21:42:58 UTC

            Bug ID: 269209
           Summary: devel/py-packaging: Update to 23.0
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: sunpoet@FreeBSD.org
          Reporter: rhurlin@FreeBSD.org
             Flags: maintainer-feedback?(sunpoet@FreeBSD.org)
          Assignee: sunpoet@FreeBSD.org

Created attachment 239771
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=239771&action=edit
patch to update from 21.3 to 23.0

This patch updates devel/py-packaging from 21.3 to 23.0. There have been
several changes and fixes [1][2].

[1] https://github.com/pypa/packaging/releases/tag/22.0
[2] https://github.com/pypa/packaging/releases/tag/23.0

What this patch does:
- Change USES from distutils to pep517
- Add pytest (26338 tests are fine, 1 skipped)
- Remove devel/py-pyparsing dependency
- Add several dependencies for BUILD_, RUN_ and TEST_DEPENDS
- More actual text in pkg-descr

portlint -AC, portclippy are fine.

Poudriere breaks with a dependency loop:

[00:00:06] Error: Dependency loop detected:
These packages depend on each other: py38-packaging-23.0 py38-build-0.9.0
These packages depend on each other: py310-build-0.9.0 py310-packaging-23.0
These packages depend on each other: py37-build-0.9.0 py37-packaging-23.0
These packages depend on each other: py39-packaging-23.0 py39-build-0.9.0
These packages depend on each other: py311-packaging-23.0 py311-build-0.9.0

It turns out, that devel/py-build (the pep517 package builder) uses

For devel/py-packaging 23.0 there is no way back to distutils, because there is
no setup.py anymore. 

This patch can hopefully serve as a template once a way has been found for the
PEP517 package builder ports themself to use this standard as well. I
personally have no clue, how to solve the problem, sorry.

You are receiving this mail because:
You are the assignee for the bug.