Re: Seeking guidance on submitting several new Python-based ports

Hi! > > How should I go about submitting these new ports? > > If you add one port per PR and set the proper dependencies in each PR, > it's easy for several committers to work on those ports. All the new ports are added to the tree. I hope I did not miss any. -- p...@freebsd.org +49 17

Re: Seeking guidance on submitting several new Python-based ports

Hi! > Is it reasonable to submit several ports as part of one PR? > For my purposes, there are a handful of "leaf" ports: [...] > So on one extreme, I have to submit each port, one-at-a-time, > in order. On the other extreme, I submit all 12 in one PR. > > How should I go about submitting these n

Re: textproc/py-pyphen: Change build to pep517

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

Re: textproc/py-pyphen: Change build to pep517

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 ?

Re: textproc/py-pyphen: Change build to pep517

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

Re: textproc/py-pyphen: Change build to pep517

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

Re: textproc/py-pyphen: Change build to pep517

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

Re: Bringing back lang/python27 with few modules?

Hi! > We've had many user reports over the last year re the entire situation, > including a number recently about pypy in particular. > > Feel free to reach out to python@ and we'll sort something out together. > > We're on IRC (#freebsd-python @ libera) or you can email me off list and > we can