Date: Mon, 6 Feb 2023 09:41:51 -0800 From: Yuri Victorovich <yuri@freebsd.org> To: Kurt Jaeger <pi@freebsd.org> Cc: python@freebsd.org Subject: Re: textproc/py-pyphen: Change build to pep517 Message-ID: <4774f0f2-1438-56fd-69c4-b35acacdcd33@tsoft.com> In-Reply-To: <Y%2BEuDK6z344u7eRc@fc.opsec.eu> References: <202302061004.316A4YbD001799@gitrepo.freebsd.org> <Y%2BEuDK6z344u7eRc@fc.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Kurt, You can change any port to pep517 except in very few cases when this would introduce a circular dependency. pep517 is now a default way to build python packages because distutils is now deprecated in Python. In the case of textproc/py-pyphen - it used the ad-hoc setup.py that wasn't registering it properly, because this was added before pep517 was available. Hope this helps. Best, Yuri On 2/6/23 08:42, Kurt Jaeger wrote: > Hi! > > because of this: > >> textproc/py-pyphen: Change build to pep517 > I want to ask you about the details of this. > > I'm trying to upgrade print/py-weasyprint from version 51 to 57.2. > > It looks like it now requires devel/py-flit and/or devel/py-flit-core. > > Those are ports that are built with > > USE_PYTHON=distutils > > Can I easily change those to > > USE_PYTHON=pep517 > > or is there some magic involved ? >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4774f0f2-1438-56fd-69c4-b35acacdcd33>