python-mimeparse
python-mimeparse copied to clipboard
falconry
mimeparse vs python-mimeparse
Howdy,
While doing some packaging work for Fedora, I noticed that both mimeparse and python-mimeparse are available on PyPI. After digging through the commit history, I see that python-mimeparse was originally forked from mimeparse. Mimeparse only has one commit after the fork happened.
To reduce the confusion, would it be possible for the projects to be merged back together? Or put another way, what would it take for this module to claim the mimeparse name on PyPI and become the single official source?
Hey @carlwgeorge, thanks for pointing that out.
It seems that the other package has quite a bit of issues (at least on GitHub: https://github.com/jcgregorio/mimeparse/issues) and isn't in active development.
@carlwgeorge could you link to that one commit that was was added to mimeparse after the fork happened? I'll take a look at it and see if it's breaking any logic. If not, it might be worth adding it here, so that this package is a complete, extended version of mimeparse.
There's probably plenty of projects in the wild relying on both mimeparse and python-mimeparse, so we can't just pick one name and abandon another one. We could, however, add a deprecation warning to mimeparse and suggest moving to python-mimeparse.
Cool, I didn't realize the original project had been migrated to GitHub. Here is the commit I mentioned previously.
Just from my own OCD perspective, I would prefer to use the mimeparse name, which is why I suggested merging the projects and/or taking over the mimeparse name on PyPI. If that is possible, how about adding the deprecation warning to python-mimeparse?
CC @jcgregorio
FYI, I was able to switch the Fedora package to use this source instead of the old one.
@dbtsai you should ask to take over https://pypi.python.org/pypi/mimeparse
See: https://www.python.org/dev/peps/pep-0541/#abandoned-projects
Ironically, this projects seems, itself, to be abandoned now. Because of that and other reasons (being the only 3rd party dependency), we have vendored it the Falcon web framework.
@dbtsai If you're still reading this, we are offering to take over maintenance under the Falconry umbrella, as we'd like to improve matching as per https://github.com/falconry/falcon/issues/1367 / https://github.com/dbtsai/python-mimeparse/pull/36.
(Otherwise we might try the PyPi process referenced by @graingert as well I suppose.)
Awesome @dbtsai ! I'm not sure how the process looks like either... I guess you could add me and @kgriffs on PyPi to start with:
- https://pypi.org/user/vytas/
- https://pypi.org/user/kgriffs/
I found this, but I haven't tried it this way I think where the recipient is from another organization... https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository#transferring-a-repository-owned-by-your-user-account
I think the usual process is to first transfer to a personal account of someone in the organisation, and then they transfer it into the organisation.
I think @dbtsai needs to make a new organisation and move this project there, then add @vytas7 to that new org, who can transfer the project to the final destination
I added both vytas and kgriffs as owner in pypi, and requested to transfer this to @vytas7 in github. @vytas7 you can transfer to Falcon later. Let me know if there is anything needs my help. Thanks.
Thanks for taking your time wrt transferring things, and for maintenance so far @dbtsai !
And thanks @hugovk and @graingert for shedding light on the process. Apparently no new organisations were needed for this though :cold_sweat:
Thank you @vytas7 & @dbtsai for maintaining this project. I first only found the original one, with broken 0.1.4 release. It would be nice if you could release it under mimeparse name. Did you try to contact @jcgregorio by email? Also, PyPI has a procedure in case when the original author is unreachable.
I can try to reach out to @jcgregorio, but I think this avenue has been explored before.