Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project packaging and metadata #400

Open
kurtmckee opened this issue Feb 20, 2025 · 1 comment
Open

Project packaging and metadata #400

kurtmckee opened this issue Feb 20, 2025 · 1 comment

Comments

@kurtmckee
Copy link
Contributor

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.

@JessicaTegner
Copy link
Owner

Hi @kurtmckee

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.

Open for suggestions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants