Date: Wed, 14 Jul 2021 10:38:14 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 257131] [NEW PORT] devel/py-cadquery-pywrap: C++ binding generator for Python Message-ID: <bug-257131-21822-qGd2AofGNh@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-257131-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-257131-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=3D257131 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |256925, 256924 Keywords| |feature, needs-patch, | |needs-qa CC| |ports@nicandneal.net, | |python@FreeBSD.org Summary|[NEW PORT]: |[NEW PORT] |devel/py-cadquery-pywrap - |devel/py-cadquery-pywrap: |C++ to python wrapper used |C++ binding generator for |by CadQuery. |Python Status|New |Open Flags| |maintainer-feedback?(ports@ | |nicandneal.net) --- Comment #1 from Kubilay Kocak <koobs@FreeBSD.org> --- Review items: Upstream seem to be using a name (setup.py:name=3Dpywrap) that's already registered with PyPI [1][2], a different project, which is likely to be problematic in various ways. Probably worth pinging upstream about it if they're not already aware. Since your port is named "cadquery-pywrap", there's slightly less of an issue, un= less and until upstream pick a different 'proper name' and we have to rename the port. Better to get clarity on what they will call it as soon as possible. Ideally its "cadquery-pywrap" :) Upstream pins jinja ( 'jinja2=3D=3D2.11.3',), modifying just the RUN_DEPEND= S is insufficient, and will break at runtime as soon as jinja is not that exact version. Patch the upstream dependency version spec, and ask upstream to make this a normal >=3D dependency All the python (.py) files will need to be precompiled (pyc/pyo) prior to installation using standard 'compileall' methods, as these will be generate= d at first run time, and on pkg-deinstall be orphaned (as theyre not referenced = in the pkg-plist). However, I would suggest trying to make the standard 'USE_PYTHON=3Ddistutils autoplist concurrent' framework bits work, since upstream ships a setup.py, that 'should just work' If you need help #freebsd-ports and/or #freebsd-python on Libera IRC :) [1] https://pypi.org/project/pywrap/ [2] https://github.com/tmr232/pywrap Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256924 [Bug 256924] [NEW PORT]: devel/py-logzero - Robust and effective logging for Python https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256925 [Bug 256925] [NEW PORT]: devel/py-cymbal - Add functionality missing from libclang Python binding --=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-257131-21822-qGd2AofGNh>