Re: [Distutils] [buildout] How to configure python interpreter to use it with Google Appengine?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Максим Lacrima wrote:
Thanks for your reply, Tres! Here is my buildout.cfg: [buildout] develop = . parts = python test appengine
[python] recipe = zc.recipe.egg:scripts interpreter = python eggs = unikeeper
[test] recipe = pbp.recipe.noserunner eggs = unikeeper working-directory = ./src/keeper
[appengine] recipe = rod.recipe.appengine eggs = unikeeper server-script = dev_appserver exclude = unit_tests doc_tests unikeeper.egg-info url = http://googleappengine.googlecode.com/files/google_appengine_1.3.1.zip
It looks as though the google_appengine zipfile doesn't intend to be installed in such a way as to make its libraries easily usable under setuptools. The rod.recipe.appenge recipe creates the script for running the development environment, and puts 'parts/google_appengine' on sys.path. I think you could use the 'extra-paths' argument to the 'zc.recipe.eggs:scripts' recipe to add that same path to your custom interpreter, like so: [python] recipe = zc.recipe.eggs:scripts interpreter = python eggs = unikeeper extra-paths = ${buildout:directory}/parts/google_appengine Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkulAoIACgkQ+gerLs4ltQ5WNwCfXEfFucLseXXgWiFJIZVp1XMS ih0AnRW+1pf9SqakrjkW1R6HiTlIaV5T =hM5r -----END PGP SIGNATURE-----
participants (1)
-
Tres Seaver