Sorry, I meant all the python source code files without "test" in the name.
You do not need any of the C++ or Java stuff if you are only using Python in
production.
On Wed, Apr 7, 2010 at 3:29 PM, Sherry Yang wrote:
> Kenton,
> Thanks for the followup. I actually copied over the complete inst
It looks like you just copied over the source code. You need to install the
modules in a place where python can find them: the python/setup.py script
does this for you.
On Wed, Apr 7, 2010 at 3:29 PM, Sherry Yang wrote:
> Kenton,
> Thanks for the followup. I actually copied over the complete i
Kenton,
Thanks for the followup. I actually copied over the complete install to
the production server and this did not help. Here are the directories (and
their subdirectories) I copied:
protobuf-2.3.0]$ ls
aclocal.m4config.status editors libtool
protobuf-lite.pc
You need all the files that don't have "test" in the name. (The test files
shouldn't be installed anyway.)
Protobufs do not depend on anything outside the Python standard library.
On Wed, Apr 7, 2010 at 2:01 PM, Eric wrote:
> Hello,
> I have Python and Google Protocol Buffers running on a Cen
Hello,
I have Python and Google Protocol Buffers running on a CentOS system
using the standard install. I want to run my Python scripts on a
production server (also CentOS) but if possible I would like avoid
doing the full install. Is there a relatively small subset of files I
can copy from the d