Re: textproc/py-pyphen: Change build to pep517
- Reply: Kurt Jaeger : "Re: textproc/py-pyphen: Change build to pep517"
- In reply to: Kurt Jaeger : "Re: textproc/py-pyphen: Change build to pep517"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 06 Feb 2023 17:41:51 UTC
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 ? >