Hi!
> Kurt Jaeger wrote:
> > =>> Checking for filesystem violations... done
> > =>> Error: Filesystem touched during build:
> > extra: usr/local/lib/python3.9/site-packages/flit_core/__pycache__
> > extra: usr/local/lib/python3.9/site-packages/flit_core/vendor/__pycache__
> > extra:
> > usr/local
Kurt Jaeger wrote:
Thanks. I'm testbuilding print/py-weasyprint and it fails with this:
=>> Checking for filesystem violations... done
=>> Error: Filesystem touched during build:
extra: usr/local/lib/python3.9/site-packages/flit_core/__pycache__
extra: usr/local/lib/python3.9/site-packages/flit_
Hi!
> I test on 12.3amd, 12.4amd, 13.1amd, 14.0i386 and 14.0amd.
>
> It happens on 12.4a and 14.0i -- not on the other ones ?
It did happen after I forced a rebuild.
--
p...@freebsd.org +49 171 3101372 Now what ?
Hi!
> Kurt Jaeger wrote:
> > It looks like it now requires devel/py-flit and/or devel/py-flit-core.
[...]
> For these specifically, there's some additional magic involved, due
> these being bootstrap components.
Thanks. I'm testbuilding print/py-weasyprint and it fails with this:
=>> Checking f
Kurt Jaeger wrote:
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 ?
For these specifically, there's some additional magic involved,
Hi Kurt,
Am 06.02.23 um 20:18 schrieb Kurt Jaeger:
Hi!
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-pyph
Hi!
> 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
> wa
x27;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 upgrad
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 bu
