devel/py-click-threading needs updated to support python3.8, particularly this change to click_threading/monkey.py is needed: https://github.com/click-contrib/click-threading/commit/99c47e64c7897f5a422e07d0112b42f0a06ac255#diff-e1963f3aa944d564694dd1ef3ef7ecbccde62c526347466e301ae43461bc0f20 Found when trying to run deskutils/py-vdirsyncer with python 3.8
Created attachment 226845 [details] Update devel/py-click-threading to 0.5.0
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. @Justin, Happy to review/approve this for you if you don't have a ports bit. Holler if you need help or have questions
I need this (and developer/py-click) updated in order to update deskutils/py-vdirsyncer. :-D
(In reply to Alexandre C. Guimarães from comment #3) - Consumer needs testing and confirmation - 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. this doesn't require approval
(In reply to Kubilay Kocak from comment #4) It is running fine with py38. I'm using it for a while already. I am the py-vdirsyncer maintainer, btw. :-)
Created attachment 228795 [details] Update devel/py-click-threading to 0.5.0 and take maintainership. I propose this patch to update and also (I) take the maintainership. I'm marking the previous patch obsolete due to intended maintainership switch. Thanks!
fixed long ago by rigoletto@.