indygreg/PyOxidizer

pyproject.toml support for tools like poetry

RobRoseKnows opened this issue · 5 comments

Separate issue from #82 as recommended. pyproject.toml is what's used by poetry and is the standard behind Pipfile.

nhoad commented

@indygreg once this is done, will it mean that packages built using flit will be supported as well?

Running into the issue with flit not being able to pip install inside pyoxidizer. I was able to get the pip install command that is generated to complete on my machine by putting PYTHONPATH=/usr/local/lib/python3.7/site-packages in front of the pip command. Is it possible to get the modified version of distutils to link setuptools from the site-packages so that flit can build?

Until poetry is installed, my workflow is along the lines of:

poetry install
poetry export -f requirements.txt > src/requirements.txt
cd src
pyoxidizer run

After enabling the requirements.txt example inside the src/*.bzl file. If there are errors about pinning version hashes, add the provided version hash to the end of requirements.txt

Is there any way to run poetry export whenever pyoxidizer build is called? It's easy to miss when adding new dependencies to poetry.

Or perhaps poetry export could be called whenever poetry dependencies change. Though that probably won't work until the 1.2 release is out, with its plugin support.

Or perhaps poetry export could be called whenever poetry dependencies change.

could use the poetry export pre-commit hook, maybe...