python-package-guide
python-package-guide copied to clipboard
pyOpenSci
scientific Python package recommendations & guidance curated by pyOpenSci
It would be helpful with some information about uv in the build system comparison (or at least a banner that acknowledges that uv exists and that it will be added...
I recently revisited the decision diagram at https://www.pyopensci.org/python-package-guide/package-structure-code/python-package-build-tools.html#tools-for-building-your-package and noticed that it seems to be more complicated than necessary. Specifically, the check "Does my package have a few c/c++ extensions?"...
This page: https://www.pyopensci.org/python-package-guide/package-structure-code/python-package-build-tools.html contains an overview of building and build tools (front end and back end). - [ ] Some of the tables need to be updated - IE, poetry...
There is now a universal python lock file specification [pylock.toml](https://packaging.python.org/en/latest/specifications/pylock-toml/) [PEP-751](https://peps.python.org/pep-0751/) This standard is very new at the time of writing, accepted March 2025, but is being adopted by the...
Creating a sub issue for a new page that would be valuable for advanced readers of the Packaging Guide: Locking. Now that the PyPA has a blessed lockfile standard, [pylock.toml](https://packaging.python.org/en/latest/specifications/pylock-toml/),...
Creating an issue to check interest/feasibility/etc. in expanding the section on packaging with compiled extensions! There are a bunch of moving pieces here, and I don't think we can quite...
A few years ago, @NickleDave started a [page on data for Python packages and what to do with it.](https://github.com/pyOpenSci/python-package-guide/pull/110/files) I think it's worth having someone take over and complete the...
I wrote tech blog of @akari-Inc 🎉 https://tech.akariinc.co.jp/entry/2025/05/01/190000 https://x.com/tkoyama010/status/1917907154285314485
In our workshop we ran into issues with publishing to PyPI using hatch because it requires a keyring to be setup and codespaces don't support that. this will impact others....
Bumps the actions group in /examples/pure-hatch/.github/workflows with 1 update: [actions/checkout](https://github.com/actions/checkout). Updates `actions/checkout` from 5.0.0 to 6.0.0 Release notes Sourced from actions/checkout's releases. v6.0.0 What's Changed Update README to include Node.js...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}