Saturday, July 4, 2026

Python packaging best practices

 There are so many possible ways to go with python packaging that it's painful. I'm still working more on bitvector-modern. I just setup codespell, but there is lots left to do. I started creating issues to track what is coming up:

  • #5 - Add a micro benchmark setup
  • #6 - Switch in the new __add__ and __iadd__ calls
  • #7 - Switch test style from unittest to pytest
  • #8 - Covert more of the Any type annotations to tighter definitions
  • #9 - Move all imports to the top
  • #10 - Use a better random number generator than the default import random
  • #11 - Convert more strings to f-strings
  • #12 - Make the set_value interface have explicit keyword args
  • #13 - Create a docs directory and import most of the prior documentation
  • #14 - Switch to copy.deepcopy and remove def deep_copy()
  • #15 - Add an AGENTS.md
  • #16 - Setup release automation
  • #17 - Force conventional commits
It's really wild how different it is to work on a project that doesn't have active users or constraints of a company. I have a change to be opinionated and try out things I haven't done before.

No comments:

Post a Comment