New issue 311 by jka...@kakar.ca: PyPI packages cannot be installed with PIP
http://code.google.com/p/protobuf/issues/detail?id=311
What steps will reproduce the problem?
1. Run 'pip install protobuf'
What is the expected output? What do you see instead?
I expect the protobuf package to be installed, but instead see this:
$ sudo pip install protobuf
Downloading/unpacking protobuf
Downloading protobuf-2.4.1.tar.bz2 (1.4Mb): 1.4Mb downloaded
Running setup.py egg_info for package protobuf
Traceback (most recent call last):
File "<string>", line 14, in <module>
IOError: [Errno 2] No such file or
directory: '/home/jkakar/src/fluidinfo/fluiddb/branches/implicit-paths-790115/build/protobuf/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: '/home/jkakar/src/fluidinfo/fluiddb/branches/implicit-paths-790115/build/protobuf/setup.py'
----------------------------------------
Command python setup.py egg_info failed with error code 1
Storing complete log in /home/jkakar/.pip/pip.log
What version of the product are you using? On what operating system?
I'm using the latest version on PyPI with an up-to-date Ubuntu 11.04
system.
Please provide any additional information below.
The issue is that the tarball uploaded to PyPI doesn't have a setup.py
in the root of the package. Probably the right thing to do is to
upload just the python/ directory.
http://pypi.python.org/pypi/protobuf appears to only list version 2.3.0
rather than the later (2.4.1 today) version on the
http://code.google.com/p/protobuf/downloads/list project.
the 2.3.0 tar.gz listed on pypi is just the contents of the python/
directory of the full protobuf tarball.
In order for this to work via pip install I don't think including just the
python/ subdirectory is the right thing to do; that'd mean the C++
extension module version of the API that wraps the C++ protobuf API could
not be compiled and used.
A top level setup.py suitable for pip above the python/ subdirectory might
be a better answer than just a python only package.
FYI, the package_dir argument of setup will probably help:
http://docs.python.org/distutils/setupscript#listing-whole-packages
This is a duplicate of issue #66.
aka google doesn't know how to build python packages.
Likewise, this is a major pain for us (reproduced on OS X 10.7 and Ubuntu
10.10). A fix would be much appreciated.
Is there a solution for this issue to be expected? Installation also fails
on SLES 11, where I need to install an application depending on protobuf.
This error still occuring on OSX 10.7. Would appreciate a patch.
Comment #8 on issue 311 by rem...@google.com: PyPI packages cannot be
installed with PIP
http://code.google.com/p/protobuf/issues/detail?id=311
This has been fixed; see issue #66 for details.