Unified project repo's with all-repos

[foarsitter]

I would propose that we unify all the repositories under the py-pdf organization with all-repos. I would like to see that within the py-pdf organization projects the same tools and configurations are used where possible so the possibility arises to make adjustments cross-repo with all-repos.

This gives us the benefits that all the maintainers now how to run the tests and do some maintenance tasks like updating a python version and extending the test-matrix because they are familiar with the project structure without knowing the code.

[stefan6419846]

I do not think that this makes sense in the short term: The projects tend to be different enough (for now) and I do not really see the need to do cross-project adjustments for now.

As it stands, we have fpdf2 with setuptools, pypdf (and pdfly) with flit and pypdf_table_extraction with poetry.

While there might be shared resources/experience, I would argue that this rather is about factual than distribution-specific stuff. Enforcing specific rules or build pipelines is already represented by corresponding GitHub workflows - I personally tend to have a look at the contribution guide for specific rules and then just let CI tell me what might need further adjustments.

[bosd]

I agree, Ideally we would utilize the same toolset within al repo's.
I have not evaluated yet if that is possible.

On the other hand, it is good to get started here and have some mechanisims in place.
Which covers #2.
Some linters, pre-commit stuff, ruff, tests, autopublish to pypi.
@foarsitter I remember you had some ideas about this in the other repo.

[foarsitter]

@bosd I used the cookiecutter-hypermodern-python to scaffold the previous fork and merged back in the source.

Here is a detailed list of features for this Python template:

• Packaging and dependency management with Poetry
• Test automation with Nox
• Linting with pre-commit and Flake8
• Continuous integration with GitHub Actions
• Documentation with Sphinx, MyST, and Read the Docs using the furo theme
• Automated uploads to PyPI and TestPyPI
• Automated release notes with Release Drafter
• Automated dependency updates with Dependabot
• Code formatting with Black and Prettier
• Import sorting with isort
• Testing with pytest
• Code coverage with Coverage.py
• Coverage reporting with Codecov
• Command-line interface with Click
• Static type-checking with mypy
• Runtime type-checking with Typeguard
• Automated Python syntax upgrades with pyupgrade
• Security audit with Bandit and Safety
• Check documentation examples with xdoctest
• Generate API documentation with autodoc and napoleon
• Generate command-line reference with sphinx-click
• Manage project labels with GitHub Labeler

The docs contain some tutorials: https://cookiecutter-hypermodern-python.readthedocs.io/en/2022.6.3.post1/guide.html#tutorials

[bosd]

@foarsitter Yes, the hypermodern-cookiecutter.
It looks very interesting, I researcged a bit about it after you referred to it over the the camelot repo.
Wanted to use it for another project, but did'nt get to implement it yet.

The cookiecutter project you're referring too, IMO still seems the best of the bunch.
Yet, It seems it could use some maintainer ❤️ as wel. (Last commit july 2023.)
(Still supports python 3.7, but nothing newer then 3.10)

We can stull use it as a base. Merge the improvements which are worthwhile from one of the forks here.