Add pyStrich

[mmulqueen]

Project

pyStrich

Checklist

• I read CONTRIBUTING.md - awesome-python is a shortlist, not a catalog
• One project per PR
• PR title format: Add project-name
• Entry format: - [pypi-name](https://github.com/owner/repo) - Description ending with period.
• Display name is the PyPI package name
• Placed in an existing use case (new sections and subcategories are maintainer-only)
• Meets all Quality Requirements: active, stable, documented, at least 1 month old

Which Tier

Pick one:

• Obvious choice - a tool an experienced Python developer would name when asked "what do I use for this?"
• Challenger - not yet the obvious choice, but a credible successor to one. Give adoption-trajectory evidence, not popularity alone.

Explain:

To be honest, it's was hard to pick whether it's an obvious choice or a challenger, I've picked challenger. It's a long established project (2015), but I've only recently put effort into promoting it. According to pepy.tech it has been downloaded a million times and about 60k downloads in the last 30 days. Much of its search traffic is for Data Matrix, so maybe it would be the obvious choice for Data Matrix, but a challenger for QR codes for example. It's active (last release August 2026, multiple releases this year), documented (https://www.method-b.uk/pyStrich/docs/) and well over 1 month old. It's recommended in the fpdf2 docs. It's packaged in NetBSD and BlackArch. It's a dull, niche use-case, so there's never going to be a load of hype/traction.

Displacement

If the use case is at its cap, name the entry your project replaces and argue that yours does that entry's job better. One in, one out.

N/A - no displacement.

[mmulqueen]

I forgot to say, it's stable. Don't be put off by the low version number, there's just never been a reason to bump it to 1.x, the API is generally backwards compatible back to the 2015 versions.