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
Pip install command does not match the documentation #151
I would understand if it was a fork of this but it is not. It looks like a re-uploaded version of this repo which hides forking information, and despite the new user's commits from July 19, 2025 onwards, their readme remains not updated, it still has David's message about it not being maintained. OTOH it also has the pip install fitparse message.
https://github.com/nbr23/python-fitparse IS a fork. I took it out of the "github fork network" or whatever they call it because when a parent repo gets deleted, forks get deleted too. I don't want that. But that's just github fancy UI stuff. The repo is very much a fork with some updates
I understand your concern about dependency confusion. I updated my readme to make sure readers of my fork install the forked version. I don't know that further changes are needed. If the owner of this repo wants me to transfer ownership of the pypi project, I'm happy to oblige
I don't know how the original repo's doc references the wrong pypi project. It was available when I used it to publish the fork. I don't believe pypi allows recycling of those names, but I could be wrong 🤷
@nbr23 Awesome thanks for a speedy response! I think you've done all that's necessary. All that's left to do is have this repository update its documentation to point to the correct package and perhaps to your fork. Thanks for keeping the library alive :)
Activity
update readme to make clear this is a fork and not the original
nbr23 commentedon Feb 13, 2026
hi @maqp,
thanks, I've updated the readme for https://github.com/nbr23/python-fitparse to hopefully clarify my repo's situation, which is:
Cheers
maqp commentedon Feb 14, 2026
@nbr23 Awesome thanks for a speedy response! I think you've done all that's necessary. All that's left to do is have this repository update its documentation to point to the correct package and perhaps to your fork. Thanks for keeping the library alive :)