Any particular reason not to use the tarball on the pypy website? There might be a silly permission issue to fix, but it's much easier than what appears below.
On Sat, Jul 30, 2011 at 3:17 PM, Tom Roche <tom_ro...@pobox.com> wrote: > > (Apologies if > > - this is not the appropriate venue for this question, but I don't see > any other pypy lists, and I'm finding the other docs a bit > inscrutable. > > - I sound too inexperienced or unpythonic: I've spent most of my coding > life in java and perl. > > ) > Please advise how to configure pypy to run other python code. Why I ask: > > I've started running a model implemented in python. Unfortunately a run > on "normal" python 2.6.x or 2.7.x requires > > - 130 min on my ubuntu laptop (on which working would be more convenient) > - 55 min on the best build machine to which I currently have access > > However I have read that this model runs 5x faster under pypy, so I > wanna get me that! Unfortunately my current ubuntu > > me@it:~$ lsb_release -ds > > Ubuntu 10.04.3 LTS # yes, I am planning to upgrade Real Soon Now > me@it:~$ uname -rv > > 2.6.32-33-generic #70-Ubuntu SMP Thu Jul 7 21:13:52 UTC 2011 > > is too down-level to install the available pypy RPM, so I instead did > > URI="https://bitbucket.org/pypy/pypy/downloads/pypy-1.5-linux64.tar.bz2"; > TMP_DIR_ROOT="/tmp/pypy" > for CMD in \ > "rm -fr ${TMP_DIR_ROOT}" \ > "mkdir -p ${TMP_DIR_ROOT}" \ > "pushd ${TMP_DIR_ROOT}" \ > "wget -O - ${URI} | tar xvjf -" \ > "ls -alh" \ > "popd" \ > ; do > echo -e "${CMD}" > eval "${CMD}" > done > # check path names, then > TMP_DIR_ROOT="/tmp/pypy/pypy-c-jit-43780-b590cf6de419-linux64" > TARGET_DIR_ROOT="/opt/pypy-c-jit-1.5.0-alpha0" > TARGET_PYPY_EXEC="${TARGET_DIR_ROOT}/bin/pypy" > USR_PYPY_EXEC="/usr/local/bin/pypy" > for CMD in \ > "sudo mkdir -p ${TARGET_DIR_ROOT}" \ > "sudo cp -r ${TMP_DIR_ROOT}/* ${TARGET_DIR_ROOT}/" \ > "sudo chmod 755 ${TARGET_DIR_ROOT}/" \ > "sudo chmod 755 ${TARGET_DIR_ROOT}/bin/" \ > "sudo chmod 755 ${TARGET_PYPY_EXEC}" \ > "sudo ls -al ${TARGET_PYPY_EXEC}" \ > "sudo ln -s ${TARGET_PYPY_EXEC} ${USR_PYPY_EXEC}" \ > "sudo ls -al ${USR_PYPY_EXEC}" \ > "${USR_PYPY_EXEC} --version" \ > "which pypy" \ > "pypy --version" \ > ; do > echo -e "${CMD}" > eval "${CMD}" > done > > The good news is, I can now > > me@it:~$ ls -al $(which pypy) > > lrwxrwxrwx 1 root root 37 2011-07-30 16:06 /usr/local/bin/pypy -> > /opt/pypy-c-jit-1.5.0-alpha0/bin/pypy > me@it:~$ pypy --version > > Python 2.7.1 (b590cf6de419, Apr 30 2011, 02:00:34) > > [PyPy 1.5.0-alpha0 with GCC 4.4.3] > > But when I try to actually *run* the @#$%^&! thing, it spews: > > me@it:~$ pypy > > debug: WARNING: library path not found, using compiled-in sys.path and > sys.prefix will be unset > > 'import site' failed > > Python 2.7.1 (b590cf6de419, Apr 30 2011, 02:00:34) > > [PyPy 1.5.0-alpha0 with GCC 4.4.3] on linux2 > > Type "help", "copyright", "credits" or "license" for more information. > > debug: OperationError: > > debug: operror-type: ImportError > > debug: operror-value: No module named _pypy_interact > me@it:~$ pypy -c 'import sys; print sys.path' > > debug: WARNING: library path not found, using compiled-in sys.path and > sys.prefix will be unset > > 'import site' failed > > ['', '/home/buildslave/bot64/pypy-c-jit-linux-x86-64/build/lib_pypy', > '/home/buildslave/bot64/pypy-c-jit-linux-x86-64/build/lib-python/modified-2.7', > '/home/buildslave/bot64/pypy-c-jit-linux-x86-64/build/lib-python/2.7', > '/home/buildslave/bot64/pypy-c-jit-linux-x86-64/build/lib-python/modified-2.7/lib-tk', > '/home/buildslave/bot64/pypy-c-jit-linux-x86-64/build/lib-python/2.7/lib-tk', > '/home/buildslave/bot64/pypy-c-jit-linux-x86-64/build/lib-python/2.7/plat-linux2'] > > What do I need to do to fix its library path? Is this where translation > is required? (Again, please note that I *have read* > > http://codespeak.net/pypy/dist/pypy/doc/getting-started-python.html > > but I'm finding difficulty understanding what one must do to *use* pypy, > vs what one must do to *hack* pypy, which is not my usecase.) > > TIA, Tom Roche <tom_ro...@pobox.com> > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > http://mail.python.org/mailman/listinfo/pypy-dev >
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
