Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

mimeparse vs python-mimeparse

Open
#20 16 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

The issue names no source files, tests, or entry points. Start by reviewing the referenced commit history and the mimeparse and python-mimeparse PyPI projects; done means reaching a maintainer decision about merging the projects or claiming the mimeparse name.

Written by the indexing model from the issue text.

Description

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?

Dominant language
Python
Stars
20
Forks
12
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from falconry/python-mimeparse

All issues in falconry/python-mimeparse

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.