Date: Tue, 05 Oct 2021 00:21:37 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 242014] www/jetty8: jettyctl fails to run with Python 3: SyntaxError: invalid token Message-ID: <bug-242014-21822-z1Im4tpIJj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-242014-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-242014-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242014 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |needs-patch --- Comment #6 from Kubilay Kocak <koobs@FreeBSD.org> --- Is removing USES=3Dpython correct if it needs Python at runtime for the con= trol script? Does it only support a particular subset of Python versions? Does USES=3Dpy= thon need a :<version-spec>? If it's only required at runtime, ',run' may be required. However, if the script produces .pyc/pyo files upon first invocation, the files should be r= un through Pythons standard 'compileall' function to produce and package these, otherwise the resulting files will be orphaned on the system on deinstall. Note also that any scripts invoking Python should invoke (shebang) using the specific version of Python the port has been built with, or uses, using eit= her: - PYTHON_CMD, or=20 - LOCALBASE/sbin/foo-{PYTHON_VER} (with an additional LOCALBASE/sbin/foo version pointing to it). See USE_PYTHON=3Dconcurrent We should also match upstream's documentation with respect to what the name= of the script is (with or without .sh extension) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242014-21822-z1Im4tpIJj>