python-pillow / python-pillow/Pillow

Create a `Framework :: Pillow` Trove classifier?

Open
#8,892 9 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Question
Dominant language
Python
Stars
13.8k
Forks
2.5k
Avg merge
2d 8h
Merged PRs (30d)
89

Description

There are lots of plugins for Pillow on PyPI, but they can be hard to find.

Here's a few, and their maintainers:

  1. https://pypi.org/project/pillow-avif-plugin/ @fdintino
  2. https://pypi.org/project/pillow-heif/ @bigcat88
  3. https://pypi.org/project/pillow-jpls/ @planetmarshall
  4. https://pypi.org/project/pillow-jxl-plugin/ @Isotr0py
  5. https://pypi.org/project/pillow-mbm/ @drewcassidy
  6. https://pypi.org/project/pillow-stackblur/ @pix666
  7. https://pypi.org/project/pillow-svg/ @gribbg
  8. https://pypi.org/project/DjvuRleImagePlugin/ @Piolie
  9. https://pypi.org/project/heif-image-plugin/ @homm
  10. https://pypi.org/project/jxlpy/ @olokelo
  11. https://pypi.org/project/pyheif-pillow-opener/ @ciotto
  12. https://pypi.org/project/raw-pillow-opener/ @samuelduann
  13. https://pypi.org/project/amigainfo/ @bitplane
  14. https://pypi.org/project/pillow-jxl-plugin/ @Isotr0py
  15. https://pypi.org/project/pillow-lunasvg @Maksim-Burtsev

To remedy this, I suggest we request a Trove classifier, for example, Framework :: Pillow.

PyPI's guidelines (taken from https://github.com/pypa/trove-classifiers/issues/121):

The PyPI moderators are in the process of developing a few guidelines for the creation of new Framework classifiers. Because removing classifiers is very difficult, and the longer the classifier list gets the harder it is to browse, I think we're expecting the bar to add new ones to be relatively high. Currently, we're looking at these guidelines:

  • New Framework classifiers should be created if they are "notable;" and
  • They will be of immediate use to existing projects (in other words, no creating classifiers simply in anticipation of future uses)

We understand that "notability" is subjective and we'd appreciate help judging that.

As to the other guideline ('immediate use to existing projects'), it's been suggested that

  • Requestors can demonstrate this by providing links to 10 or more existing PyPI projects that have expressed a desire to use the classifier; or
  • Another way to demonstrate this would be to have 10 or more other project maintainers submit comments on the requesting issue about their desire to use the classifier.

Are you a plugin maintainer? Would you like to use a Framework :: Pillow classifier? If so, please comment, saying which plugin you maintain.

Once we get ten, I'll open a request with PyPI.

Thank you!

Contributor guide

Open the contributing guide

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.

Research direction

Start with issue #8892, the quoted PyPI classifier guidelines, and the linked trove-classifiers issue; review the listed Pillow plugin projects and their maintainer responses. Done means gathering at least ten maintainers who want the classifier and opening the corresponding request with PyPI.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
developer-experience
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.