You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see that the project metadata and packaging is spread across several files, including:
pypandoc/__init__.py(shared metadata)
setup.py(packaging)
setup_binary.py(packaging)
pyproject.toml(Poetry metadata...maybe dev dependencies?)
Could you share your workflow for packaging? For example, if you don't use Poetry I'd like to eliminate its configuration in pyproject.toml, which will eliminate confusion.
The text was updated successfully, but these errors were encountered:
For the workflow for packing, look at the workflow file used by GitHub Actions.
But essentially:
We have 2 packages on pypi, pypandoc and pypandoc_binary.
setup.py builds pypandoc, while pypandoc_binary is build by the setup_binary.py file.
pyproject.toml was part 1 of converting the packaging to a modern tool, but I have yet to finish it because we have these 2 different packages.
Idially, I would want to convert the entire packing to a modern tool, like UV or poetry, but I don't know, and haven't had time to, actually do it when having to preserve the 2 seperate packages like this.
Hi @JessicaTegner,
I see that the project metadata and packaging is spread across several files, including:
pypandoc/__init__.py
(shared metadata)setup.py
(packaging)setup_binary.py
(packaging)pyproject.toml
(Poetry metadata...maybe dev dependencies?)Could you share your workflow for packaging? For example, if you don't use Poetry I'd like to eliminate its configuration in
pyproject.toml
, which will eliminate confusion.The text was updated successfully, but these errors were encountered: