[Bug 257365] devel/py-click-threading: Update to 0.5.0 (Fixes Python 3.8 support)

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 02 Aug 2021 04:30:52 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257365

Kubilay Kocak <koobs_at_FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Open
           Severity|Affects Only Me             |Affects Some People
            Summary|devel/py-click-threading    |devel/py-click-threading:
                   |needs updated to support    |Update to 0.5.0 (Fixes
                   |python3.8                   |Python 3.8 support)
           Assignee|ports-bugs_at_FreeBSD.org      |jhibbits_at_FreeBSD.org
              Flags|                            |merge-quarterly?
                 CC|                            |python_at_FreeBSD.org
           Keywords|                            |needs-patch

--- Comment #2 from Kubilay Kocak <koobs_at_FreeBSD.org> ---
deskutils/py-vdirsyncer (consumer) should be checked for current (proposed)
version compatibility. RUN_DEPENDS specifies >=, but upstream may specify a <
pinned version, or not be compatible with 0.5.0 (or some other issue).

Also, if the current version of the port doesn't support 3.8, an initial change
to cap the current version to -3.7 should be committed, so that can be merged
first and separately

Also noted, the click RUN_DEPENDS should also match the version specifier
declared in upstream sources ('click>=5.0',), and upstream isnt testing against
Python 3.10, but this ports USES=python <version-spec> allows it. We should
either confirm 3.10 passes tests, or cap it at -3.9

^Triage: Reporter is committer, assign accordingly.

_at_Justin, Happy to review/approve this for you if you don't have a ports bit.
Holler if you need help or have questions

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Mon Aug 02 2021 - 04:30:52 UTC

Original text of this message