Bug 943 – pypi: pip install PySide fails: No such file or directory: '/root/build/PySide/setup.py' (pip finds OLD pyside only)

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 943 - pypi: pip install PySide fails: No such file or directory: '/root/build/PySide/setup.py' (pip finds OLD pyside only)

Summary:

pypi: pip install PySide fails: No such file or directory: '/root/build/PySid...

Status:	RESOLVED WONTFIX

Product:	PySide
Classification:	Unclassified
Component:	packaging
Version:	HEAD
Platform:	PC Linux

Importance:	P3 normal
Assigned To:	Bruno Araujo

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-07-23 02:04 EEST by letters.random13
Modified:	2012-01-05 23:42 EET (History)
CC List:	10 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description letters.random13 2011-07-23 02:04:29 EEST

[maybe this should be in component 'installation', not 'packaging', but that
option isn't available]

install pyside from pypi via 'pip install' fails.
the version of pyside that pip tries to install is VERY OLD; 0.1.4.5 (not even
an option on the bugzilla Version selector!)

http://www.pyside.org/files/
 pyside-0.1.4.5.tar.bz2                   19-Aug-2009 17:57  606K

is (current?) pyside supposed to be installable via pip?  if yes, what is the
workaround?

same error occurs using a manually generated python2.7.2 on n900ce meego 1.2
(other packages install fine via pip install).

=================
[root@~]# pip install PySide
Downloading/unpacking PySide
  Downloading pyside-0.1.4.5.tar.bz2 (620Kb): 620Kb downloaded
  Running setup.py egg_info for package PySide
    Traceback (most recent call last):
      File "<string>", line 14, in <module>
    IOError: [Errno 2] No such file or directory: '/root/build/PySide/setup.py'
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):

  File "<string>", line 14, in <module>

IOError: [Errno 2] No such file or directory: '/root/build/PySide/setup.py'

----------------------------------------
Command python setup.py egg_info failed with error code 1
Storing complete log in /root/.pip/pip.log

================

the pkg README file is empty; this is not healthy, nor helpful to the installee

==================
[root@~]# ls -l build/PySide/README 
-rw-r--r--. 1 root root 0 Jul 22 15:32 build/PySide/README


[root@~]# python --version
Python 2.7.1
[root@~]# pip --version
pip 1.0.1 from /usr/lib/python2.7/site-packages (python 2.7)

Comment 1 Hugo Parente Lima 2011-07-25 16:56:17 EEST

Try with a newer version if they exists on PyPi, the current version is 1.0.5.

You can reopen this bug is it still not working with a newer version.

Regards.

Comment 2 iain.dalton 2011-08-08 21:37:17 EEST

It looks like pip install looks at 
<http://pypi.python.org/pypi/PySide/>, specifically the "Download URL" 
link: <http://www.pyside.org/files/>.  The latest version of PySide is 
available under the wrong name: pyside-qt4.7+1.0.5.tar.bz2, which pip 
doesn't know to use.  The latest source distribution under the proper 
name is pyside-0.1.4.5.tar.bz2, which has a timestamp of 2009-08-19.  It 
tries to use it and fails.

Solution: pyside-qt4.7+1.0.5.tar.bz2 should be pyside+1.0.5.tar.bz2, or PyPI
package should be PySide-QT4.7.

Comment 3 Hugo Parente Lima 2011-08-16 21:15:33 EEST

Roman Lacko did this PyPi package, so I added him to cc'list, so he will know
about the problem that appear to be just a URL typo.

Thanks

Comment 4 Roman Lacko 2011-08-17 09:34:52 EEST

PIP is not supported. PIP install packages only from sources, not from
binaries,
PySide packages are distributed as binaries.

Comment 5 Hugo Parente Lima 2011-08-17 20:20:20 EEST

So can we mark this bug as invalid?

Comment 6 letters.random13 2011-08-18 06:13:05 EEST

speaking as a 'user' of pyside, i say the bug IS valid.

but, it is, and always has been, a pyside maintainer issue.

pip uses pypi as its 'source'. pypi is a good(?) means to advertise python
'packages' such as pyside. as it currently stands, any
python/pypi/pip/easy_install user who sees pyside and wants to *easy* install
it will have the same irritating, misleading installation failure, with no idea
of what to do next, except report it to pyside as a pyside bug.

if pyside cannot install that way, why is it in pypi, except for invalid
historical reasons? at least there should be some mention that it cannot be
installed in the 'normal' easy ways. or just move the obsolete source tar files
off of the pyside download page (or tell pypi to look at a dummy page or pkg)
and let pypi complain to the user that it cannot find the package. at which
time maybe they'll ask the pyside maintainers what they should do...

$ pip install dummypyside
Downloading/unpacking dummypyside
  Could not find any downloads that satisfy the requirement dummypyside
No distributions at all found for dummypyside

Comment 7 Roman Lacko 2011-08-18 10:07:21 EEST

For now installation with easy_install (not PIP) is supported only on windows.

This will work without problems in windows:

>> easy_install PySide

On other platform it will not work simply becasue the binaries compatible with
Setuptools/easy_install were newer created and uploaded to PyPI.

I have plans to add support for building the binaries with my scripts also on
Linux (I'm using Ubuntu). But still it will be available only as source
distribution. It means that easy_install (or PIP) will be able to download the
distribution from PyPI but the binaries will be build on your system (the
process of downloading the source and build of binaries will be handled
transparently by PIP/easy_install). I'm affraid that pre-build binary
distributions will never be available for Linux on PyPI.

Comment 8 Hugo Parente Lima 2012-01-05 23:42:11 EET

Ok, I'm marking this bug as WONTFIX, as PyPi install isn't supported by us, it
was brought to live by community efforts, so probably no one from the core dev
team will take a look at it :-/

In other words, let's try to keep on bugzilla only things that can be fixed by
commits on PySide github repositories with few exceptions. Anyway thanks very
much for the report.