You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Create a new release based on fixes after v2.2.0? #135
Would it be possible to create a new release to take into account the changes/fixes that was made after v2.2.0?
Commits spanning from 2021 to 2023 are not reflected in release v2.2.0 (2020).
For anyone still watching this thread: since the original hasn't had a release since 2.2.0, I've published a maintained, drop-in successor on PyPI — user-agents-ng.
The API is unchanged (from user_agents import parse), so migration is just:
@SAKMZ Have you considered turning on issues on the repo? This way there is no practical way to report issues back (not that I see any, but I was considering migration, and this looks weird).
Activity
SAKMZ commentedon Jul 20, 2026
For anyone still watching this thread: since the original hasn't had a release since 2.2.0, I've published a maintained, drop-in successor on PyPI —
user-agents-ng.The API is unchanged (
from user_agents import parse), so migration is just:What's new in 3.0.0: tested support for Python 3.9–3.14, type hints +
py.typed,pyproject.tomlpackaging, and CI on Linux + Windows.Full credit to @selwin and the original authors — this only picks up where 2.2.0 left off. Repo: https://github.com/SAKMZ/python-user-agents. Happy to fold in outstanding fixes if there's interest.
nijel commentedon Sep 22, 2026
@SAKMZ Have you considered turning on issues on the repo? This way there is no practical way to report issues back (not that I see any, but I was considering migration, and this looks weird).