https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268018
--- Comment #3 from Sean Champ <lab+bsd@thinkum.space> --- Ah, there's a Wiki page https://wiki.freebsd.org/Python/PEP-517 I'm quite new to the Python programming language lol. I don't believe every project uses flit in itself, from pyproject.toml? Some projects might prefer hatchling e.g, or using the conventional setuptools. For an more recent devel/py-jupyterlab (3.5.0) released more recently than what's in ports right now, there's also the following for instance: ~~~~ [build-system] requires=["jupyter_packaging>=0.9,<2"] build-backend = "jupyter_packaging.build_api" ~~~~ I believe I'd hoped it might be a sufficient hack, to just call setuptools instead. If there's a broader project for addressing PEP-517 though, I think that's good to see. Of course with textproc/py-sphinx if I was only using setuptools and only installing everything it compiled, then that may not be sufficient to ensure that the sphinx themes would be installed with the py-sphinx port - thus to the effect of present patch, to ensure that at least the basic sphinx theme is installed and available for direct application with sphinx or for reference and extension in other sphinx themes. Returning to the PEP-517 topic, after the recent devel/py-jupyterlab release, then after one local test build it seemed that building with jlpm in particular may result in drawing in a lot of NPM packages, with quite a large download in the build process. I believe that's what the distributors may be using in order to produce what we're seeing in the downloads from cheeseshop? Thus, perhaps what we've download from the cheeeshop master site may already have been partially processed - contrasted to building directly from GitHub sources, for instance With sphinx at least, I'd thought it might be a good precaution to filter it again with pyproject-build nonetheless, if not simply installing all the sources files from the distfile archive. My main goal with the patch was simply to ensure that the basic theme is installed, along with the rest of the sphinx components that show up after the filtering with the upstream project's preferred build tool. I think it's great if the more general concern about PEP-517 support is being addressed though -- You are receiving this mail because: You are the assignee for the bug.
