Add pyrift — static analyser for CPython/PyPy behaviour differences

[BHUVANSH855]

Project

pyrift

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

• Challenger - not yet the obvious choice, but a credible successor to one. Give adoption-trajectory evidence, not popularity alone.

Explain:
pyrift fills a gap that no existing Code Analysis tool covers — silent
runtime behaviour differences across CPython versions and between CPython
and PyPy. Tools like pylint, ruff, mypy, and bandit all operate on syntax
and types. pyrift operates on runtime semantics: deprecated APIs, removed
modules, GC timing differences, and version-specific stdlib gaps.

It was released in August 2026, reached v0.7.0 within days, has 90 rules,
392 tests, zero dependencies, and is already announced on Python Discord,
Python Discourse, and the PyPy mailing list. The library solves a real
problem — Python version upgrades and CPython/PyPy compatibility — that
developers currently handle manually or not at all.

Displacement

No displacement needed. pyrift occupies a unique position in the Code
Analysis section — it is the only tool focused on runtime behaviour
differences rather than syntax, style, or types. It complements rather
than replaces existing entries.

[JinyangWang27]

@BHUVANSH855 Thanks for your submission. However, the repository age needs to be at least 1 month. Please see our CONTRIBUTING.md for full requirements.