Hi, For my lab i actually manage to package the latest version (existing 
package on guix are old) of python mkdocs static site generator with 
mkdocs-materials theme. Mkdocs use a yaml entry to call the theme (here 
mkdocs-material-theme) to use for the website generation. Both project use a 
pyproject.toml for pip installation. An example of mkdocs.yml that use the 
material theme : ```yamlsite_name: my site nametheme:  name: material``` The 
name entry run/use python entry-points 
(https://peps.python.org/pep-0621/#entry-points) to detect theme actually 
installed with pip in the same context. Entry-point is a common way to 
install/link package as plugin. Even if my homemade package mkdocs-material is 
well installed and contain the entry-point.txt into dist-info/entry_points.txt 
that doesn't work. By looking in the build system of python i found some 
information about that : I package mkdocs-material using the new 
pyproject-build-system 
https://git.savannah.gnu.org/cgit/guix.git/tree/guix/build/pyproject-build-system.scm
  My problem is that management of entry-points seems not implemented, as line 
https://git.savannah.gnu.org/cgit/guix.git/tree/guix/build/pyproject-build-system.scm#n61
 say. Is there a way to implement this outside of pyproject-build-system, only 
for this project ? Best regards,SR   

Reply via email to