Skip to content

Replace PIL with Pillow on PyPI #1535

Closed

Description

@matysek

Is there any chance that Pillow team could take over ownership of PyPI page https://pypi.python.org/pypi/PIL/ and that Pillow would became the "official" version of PIL?

It would be nice if Pillow could be installed just by command pip install PIL.

Activity

  1. wiredfool commented on Nov 12, 2015

    @wiredfool
    Member

    I think we'd need Fredrik Lundh to do that, and I haven't seen anything him in ~5 years.

    That entry is ancient, as it even predates the last actual PIL release, which was 1.1.7.

  2. radarhere commented on Dec 2, 2015

    @radarhere
    Member

    If this is the way to go, it looks like one would create a support request to recover the page from Fredrik Lundh, along the lines of http://sourceforge.net/p/pypi/support-requests/562/

  3. hugovk commented on Dec 2, 2015

    @hugovk
    Member

    Or contact the author directly. That's what I did with my fork of pylast, and he gave me access: pylast/pylast#92.

  4. radarhere commented on Dec 2, 2015

    @radarhere
    Member

    In trying to find contact details, a WHOIS lookup for effbot.org will provide an e-mail address. There is an @effbot user on GitHub, but that may or may not be Fredrik Lundh.

    I presume that we'd want @aclark4life to become the owner of the index page.

  5. radarhere commented on Dec 2, 2015

    @radarhere
    Member

    Thanks. I've sent an e-mail, we'll see what happens.

  6. aclark4life commented on Dec 2, 2015

    @aclark4life
    Member

    I don't expect to hear from Fredrik, but of course it can't hurt to ask. For reference, here's where Pillow was introduced in July 2010:

    More interesting comments in August 2010:

    My favorite comment from Fredrik, which gave my effort legitimacy (in my mind), is here:

    At least a packaging fork means that someone's over there is producing something more than
    invectives, but I'd still prefer a patch.
    

    Regarding whether we want this to happen, maybe. There's a lot to think about with regard to Pillow actually becoming PIL and I've not done any of that thinking yet. I'm not opposed to it, but I'd want to make sure it was "done right" and I'm not sure what that means. At the very least, I'd want to have a good reason and I'd want to reduce confusion, not add to it.

  7. changed the title [-]replace PIL by Pillow on PYPI[/-] [+]Replace PIL with Pillow on PYPI[/+] on Dec 2, 2015
  8. radarhere commented on Dec 4, 2015

    @radarhere
    Member

    Fredrik replied, saying that he'd attempt to get around to it next week.

    I'm not necessarily advocating that we do make Pillow the 'official' version of PIL. I do think that updating the page to show 1.1.7 would be good, and changing the description to make people aware of Pillow would be good.

  9. aclark4life commented on Dec 4, 2015

    @aclark4life
    Member

    @radarhere Great, glad to hear

  10. wiredfool commented on Dec 7, 2015

    @wiredfool
    Member
  11. aclark4life commented on Apr 1, 2016

    @aclark4life
    Member

    I'm going to assume this isn't going to happen. Please reopen if I'm wrong or if something changes. (And I'm still not sure I'd want it to happen, though I guess we could make it work somehow; possibly by releasing Pillow as both Pillow & PIL for a while.)

  12. verhovsky commented on Sep 25, 2019

    @verhovsky
  13. aclark4life commented on Sep 26, 2019

    @aclark4life
    Member

    @verhovsky Never say never, I guess… thanks for trying! Also need @python-pillow/pillow-team to think about how to support it, if it happens.

  14. 30 remaining items

  15. hugovk commented on Mar 7, 2024

    @hugovk
    Member

    Thanks, accepted!


    Back to the OP question:

    Is there any chance that Pillow team could take over ownership of PyPI page pypi.python.org/pypi/PIL and that Pillow would became the "official" version of PIL?

    It would be nice if Pillow could be installed just by command pip install PIL.

    Once upon a time, the releases on PyPI had their installation files hosted elsewhere than PyPI.

    Later, PyPI also offered hosting itself (see also PEP 438).

    Then in 2015, PEP 470 removed support for externally-hosted files (pypi/warehouse#431), meaning all files must be hosted on PyPI.

    It used to be that you could pip install pil and pip install pillow and not really be sure which you had. Hence the warning at https://pillow.readthedocs.io/en/latest/deprecations.html#pillow-and-pil:

    Pillow and PIL cannot co-exist in the same environment. Before installing Pillow, please uninstall PIL.

    However, all the releases at https://pypi.python.org/pypi/PIL/ are from 2006 and earlier, and were all externally-hosted files. That means pip install pil no longer works:

    ❯ pip install pil
    ERROR: Could not find a version that satisfies the requirement pil (from versions: none)
    ERROR: No matching distribution found for pil

    This means no more confusion over having PIL and Pillow both installed at the same time.

    I recommend we leave PIL on PyPI as it is: don't release any kind of shim so that pip install pil would install Pillow. Let attempted installs of PIL give an error.

    This should help keep the installation story simpler: install pillow.

    (It's already complicated enough with people installing pillow for one Python interpreter, but running a Python script for another (for example).)

  16. added a commit that references this issue on Mar 7, 2024
  17. hugovk commented on Jan 19, 2025

    @hugovk
    Member

    PyPI has a brand new feature allowing packages to be archived. It adds a banner like:

    This project has been archived.

    The maintainers of this project have marked this project as archived. No new releases are expected.

    Let's do it for https://pypi.org/project/PIL/

    @aclark4life Please could you go to https://pypi.org/manage/project/PIL/settings/ and click the "Archive" button? It's possible to unarchive later.

  18. reopened this on Jan 23, 2025
  19. moved this from Closed to New Issues in Pillowon Jan 23, 2025
  20. aclark4life commented on Jan 23, 2025

    @aclark4life
    Member

    Will do

  21. aclark4life commented on Jan 23, 2025

    @aclark4life
    Member

    Should we take their advice before archiving?

    Image
  22. hugovk commented on Jan 23, 2025

    @hugovk
    Member

    I don't think we need to, there's very little at https://pypi.org/project/PIL/ and no files to download; pip install PIL gives an error.

    If we made a new release, we'd need to upload some files, and having some sort of file to download would be more confusing than none.

  23. aclark4life commented on Jan 23, 2025

    @aclark4life
    Member

    Done!

  24. hugovk commented on Jan 23, 2025

    @hugovk
    Member

    Thank you!

    Image
  25. moved this from New Issues to Closed in Pillowon Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    InstallationUsually a problem with …PackagingAny mention of setup.py; some overlap with Install label

    Type

    No type

    Projects

    • Status
      Closed

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions