Created attachment 226591 [details]
git diff to upgrade dsbxinput-0.1 to dsbxinput-0.1.1
Release notes: https://github.com/mrclksr/DSBXinput/releases/tag/0.1.1
portlint: OK (looks fine.)
testport: OK (poudriere: 130Ramd64)
^Triage: Add python 3.8 support, MFH
@Maintainer Did upstream remove 3.7 support, or does it support 3.7+ ?
Does it also support and pass runtime tests / test suite with 3.9/3.10? If not it should be marked 3.7-3.8
(In reply to Kubilay Kocak from comment #1)
the port depends on pyqt which is build for $PYTHON_DEFAULT (3.8), so I figured the easiest way to fix it is changing the script's shebang to use Python 3.8 instead of 3.7.
(In reply to Marcel Kaiser from comment #2)
Thanks for the feedback Marcel.
That (3.8) is just the 'current point in time' default version, provided by the ports framework, not individual ports. The default changes over time, and users cann choose whatever default version they like (overriding the default).
Individual ports declaratively just specify what versions the package (code) supports.
In py-qt5's case, that's:
USES= metaport python:3.5+ (annythingn from 3.5 up, currently, to 3.10)
In this ports case, whatever python versions the code in dsbxinput.in supports ("actually can run with"). This is a matter of testing the code.
A good best-practice read over how to write as portably as possible (as an upstream), is:
For example the shebang line in sdbxinput should likely/probably be "/usr/bin/env python3" (in that it supports, and will call python3 on user systems), unless its Python 2/3 compatible in which case "/usr/bin/env python" might be more suitable.
Don't hesitate to jump on #freebsd-python on LiberaChat IRC if you need support or have further questions, we're happy to help
(In reply to Kubilay Kocak from comment #3)
Thanks a lot for the explanation, Kubilay :-)