#191 What is the policy on confusingly-similarly named packages?


This evening, I went to install wxPython (which is called "wx" when you import it).

However, "pip install wx" grabs a completely unrelated package: http://pypi.python.org/pypi/wx/1.0.0

This seems to literally be a attempt at uploading a package, as a test. The entire contents of the package are a 7-line function, that takes a file-name, and returns the file contents as a string.

Now, that's fine, but it's sure confusing when you type "pip install wx", it successfully installs, and you can even "import wx", but you get a different wx.

How is this sort of name-space collision handled in pypi?


  • fake-name

    fake-name - 2012-08-11

    As a somewhat unrelated tangent, "pip install wxPython" grabs the completely wrong package (I'm on a Mac, it tries to download the windows source tree).

    Who do I talk to about that?

  • Martin v. Löwis

    • status: open --> closed
  • Martin v. Löwis

    The only policy on naming is that they are available on a first-come-first-served basis, and that any name is fine as long as it isn't literally equal to an existing name, and is not morally unacceptable.

    We rely on users to negotiate colliding interests. I.e. you could contact the owner of the wx package and ask him to remove it, and you could contact the owners of the wxPython package and let them know. However, unless the content of the wx package is actually malicious, we will not forcefully remove it.

    As for pip downloading the wrong file: please report that to the pip maintainers.


Log in to post a comment.