this post was submitted on 13 Oct 2025
5 points (100.0% liked)
Python
7589 readers
1 users here now
Welcome to the Python community on the programming.dev Lemmy instance!
π Events
Past
November 2023
- PyCon Ireland 2023, 11-12th
- PyData Tel Aviv 2023 14th
October 2023
- PyConES Canarias 2023, 6-8th
- DjangoCon US 2023, 16-20th (!django π¬)
July 2023
- PyDelhi Meetup, 2nd
- PyCon Israel, 4-5th
- DFW Pythoneers, 6th
- Django Girls Abraka, 6-7th
- SciPy 2023 10-16th, Austin
- IndyPy, 11th
- Leipzig Python User Group, 11th
- Austin Python, 12th
- EuroPython 2023, 17-23rd
- Austin Python: Evening of Coding, 18th
- PyHEP.dev 2023 - "Python in HEP" Developer's Workshop, 25th
August 2023
- PyLadies Dublin, 15th
- EuroSciPy 2023, 14-18th
September 2023
- PyData Amsterdam, 14-16th
- PyCon UK, 22nd - 25th
π Python project:
- Python
- Documentation
- News & Blog
- Python Planet blog aggregator
π Python Community:
- #python IRC for general questions
- #python-dev IRC for CPython developers
- PySlackers Slack channel
- Python Discord server
- Python Weekly newsletters
- Mailing lists
- Forum
β¨ Python Ecosystem:
π Fediverse
Communities
- #python on Mastodon
- c/django on programming.dev
- c/pythorhead on lemmy.dbzer0.com
Projects
- PythΓΆrhead: a Python library for interacting with Lemmy
- Plemmy: a Python package for accessing the Lemmy API
- pylemmy pylemmy enables simple access to Lemmy's API with Python
- mastodon.py, a Python wrapper for the Mastodon API
Feeds
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Package DevOPs is a skill. Half assing it will not:
impress a published package author's peers
encourage confidence in the authors perseverance to maintain the package
encourage confidence in the author's willingness to politely respond to Issues and PRs
package will have issues that never get resolved cuz the author packaging skillset is woefully lacking including but not limited to: Makefile, pre-commit, tox, gha, doctest, documentation, test coverage, multiple platform support, manylinux support, setup for collaboration, and static typing.
So suggest redirecting efforts towards studying how to improve packaging rather than how to avoid packaging.
A suggestion on things to improve documentation:
move the doctest out of in-code documentation and into test suite! So the doctest are proof and contribute to coverage
This is straight from a
Makefile. Where the file extension for doctest was changed to.rst. Can see have A B testing setup to compare two packages.Example how to include doctest into Sphinx document
Was this meant for a different thread?
On this board, and hope everyone else is, to learn and share. Try to contribute, not just state my opinion.
Didn't feel this thread offered anything substantial to learn, so threw out some gem that others might find useful in their projects.
Thank you, oh wise one ππ»