I wanted to install wx and tried to "sudo pip install wx". Sadly this https://pypi.python.org/pypi/wx module described as "my first python module, like php file_get_contents" shadowed the wxpython I eventually installed with "sudo apt-get install python-wxgtk2.8". Can we remove that package from pypi? Preferably with the author's consent. Yuval
On Fri, Jun 7, 2013 at 7:59 AM, Yuval Greenfield <ubershmekel@gmail.com> wrote:
I wanted to install wx and tried to "sudo pip install wx". Sadly this https://pypi.python.org/pypi/wx module described as "my first python module, like php file_get_contents" shadowed the wxpython I eventually installed with "sudo apt-get install python-wxgtk2.8".
Can we remove that package from pypi? Preferably with the author's consent.
Packages are allowed to have the same module names as other packages. In this case it's a bit unfortunate, but it should reasonably have been quickly solved by uninstalling the wx package? //Lennart
On Fri, Jun 7, 2013 at 10:27 AM, Lennart Regebro <regebro@gmail.com> wrote:
Packages are allowed to have the same module names as other packages. In this case it's a bit unfortunate, but it should reasonably have been quickly solved by uninstalling the wx package?
//Lennart
It wasn't easy figuring out I needed to type "sudo pip uninstall wx" to fix wx. A python beginner would have had a terrible time with this. I realize we don't want to start squat-wars. But pypi's wx is a 5 liner that absolutely no person would ever want installed. At the least, pip should warn me when I install "wx" that it's probably not what I'm looking for. Yuval
On Fri, Jun 7, 2013 at 9:56 AM, Yuval Greenfield <ubershmekel@gmail.com> wrote:
On Fri, Jun 7, 2013 at 10:27 AM, Lennart Regebro <regebro@gmail.com> wrote:
Packages are allowed to have the same module names as other packages. In this case it's a bit unfortunate, but it should reasonably have been quickly solved by uninstalling the wx package?
//Lennart
It wasn't easy figuring out I needed to type "sudo pip uninstall wx" to fix wx. A python beginner would have had a terrible time with this.
I expect a beginner would have read steps on how to install wxPython and hence not installed wx by mistake. :-) The fundamental problem here is of course that wxPython has chosen to have different names for package and module, which is an unfortunate choice. If the wxPython maintainers want to rename the package wx, that would solve the problem.
I realize we don't want to start squat-wars. But pypi's wx is a 5 liner that absolutely no person would ever want installed. At the least, pip should warn me when I install "wx" that it's probably not what I'm looking for.
There's no way for pip to know that. //Lennart
On Fri, Jun 7, 2013 at 12:56 AM, Yuval Greenfield <ubershmekel@gmail.com> wrote:
I realize we don't want to start squat-wars. But pypi's wx is a 5 liner that absolutely no person would ever want installed. At the least, pip should warn me when I install "wx" that it's probably not what I'm looking for.
This isn't a question for the wxPython project, it's one for the PyPi folks and/or the author of the "other" wx. As it happens, there has been a discussion recently on the distutils list about whether the Pyton community should establish a system for regulating top-level package names -- but at this point, it seems everyone all getting along is where we are at. wxpython is listed on PyPi, what else can we do? This is not a unique situation that someone would accidentally install a different package than they intended. In this case, I suspect that if you installed wxPython on top of that wx, it would just work. Still not a bad idea to suggest the author of the other wx to remove or rename it -- why invite confusion? Last point -- does PyPi have a system for aliases? If so, it might be a good idea to have wxPython in there as wx as well. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov
participants (3)
-
Chris Barker - NOAA Federal
-
Lennart Regebro
-
Yuval Greenfield