Created basic pyproject.toml

[pawel-biernacki-roche]

Created a very basic pyproject.toml, so that it is possible to install the package with e.g. poetry.

Previously, the following error was raised:

ChefBuildError Backend subprocess exited when trying to invoke get_requires_for_build_wheel

[pawel-biernacki-roche]

@charlesll would it be possible to release a new version of the package to pypi? Much appreciated!

[charlesll]

Yes, will do that in the upcoming days!

[pawel-biernacki-roche]

Wonderful! Much appreciated 🙌

[charlesll]

Hi @pawel-biernacki-roche , I am actually looking at switching to a full pyproject.toml file, but this creates issues with compilation of the FORTRAN code... It is apparently not possible to do the same things that I did in my setup.py file, if I understood right. This issue already exists when working with your minimal pyproject.toml file.

Pyproject does not allow handling the Fortran compilation and extension as setup.py does.

Any idea how to solve this issue ?

[pawel-biernacki-roche]

Hi @charlesll ,

I have investigated this a bit and it seems to me that you won't be able to fully drop the setup.py; I have found this two links that are a bit more informative:

• https://stackoverflow.com/questions/66157987/how-to-build-a-c-extension-in-keeping-with-pep-517-i-e-with-pyproject-toml-ins
• https://www.reddit.com/r/learnpython/comments/121xqmy/including_fortran_code_in_package_without_setuppy/

However, I personally would still recommend to move as much as possible to pyproject.toml. In our closed-source code we use it to configure tests, dependencies (for poetry environment, which we then use to build the package), linter, styler, etc.

In case you want to go poetry way, then these discussions are quite interesting (and perhaps some kind of a starting point):

• support for non-python extensions python-poetry/poetry#1351
• Stabilize 'build.py' python-poetry/poetry#2740

[pawel-biernacki-roche]

Hi @charlesll ! Is there any progress on pushing the new package to pypi? It starts to become a blocker for our work... Is there maybe something we could help out with?

[charlesll]

Hi @pawel-biernacki-roche unfortunately I did not make any progress on this side because when I include the pyproject.toml, the compilation of the FORTRAN code does not work anymore when doing pip install gcvspline. Right now I haven't found a solution (see comments above) or maybe I missed something?

[charlesll]

I confirm the following error when trying to install with your pyproject.toml;

import gcvspline
Traceback (most recent call last):
File "", line 1, in
File "/media/charles/DATA/Documents/gcvspline/gcvspline/init.py", line 1, in
from .gcvspline1 import *
File "/media/charles/DATA/Documents/gcvspline/gcvspline/gcvspline1.py", line 12, in
from . import _gcvspl as gcvspl
ImportError: cannot import name '_gcvspl' from partially initialized module 'gcvspline' (most likely due to a circular import) (/media/charles/DATA/Documents/gcvspline/gcvspline/init.py)

I don't get why I have this error...

[pawel-biernacki-roche]

@charlesll I have worked a bit more on the pyproject.toml, mostly moving the metadata. I am able to build the wheel with the definition that I have. I also manage to install it in our poetry environments.

We have, however, encountered issues when installing the project with python 3.8, so will investigate that more. In the meantime, shall I open a PR for the pyproject.toml enhancement?

The installation in py3.9 goes fine:

[charlesll]

Yes, please open a PR and I will also test it on my side.