buildout

问题 I'm working on setting up a Zope Replicated Storage (ZRS) based deployment. I currently have two servers (east and west) west will be the primary east will be the secondary I haven't touched the west box yet . On the east box I've edited my buildout as follows (I had to pin plone.recipe.zeoserver to 1.2.6 because the zrs features didn't exist before version 1.2.6): [zeoserver] recipe = plone.recipe.zeoserver[zrs] replicate-from = ${hosts:zeoserver-west}:${ports:zeoserver-zrs} [versions] plone

问题 I'm working on a buildout script that needs to install a distutils package on remote server. On PyPi there are 2 recipes for doing this collective.recipe.distutils 0.1 and zerokspot.recipe.distutils 0.1.1. The later module a derivative of the former, and is a little more convenient then the first, but the both suffer from the same problem, which I will describe now. When bootstrap.py is executed, it downloads zc.buildout package and puts it into buildout's eggs directory. This gives ./bin

问题 I'm working on a buildout script that needs to install a distutils package on remote server. On PyPi there are 2 recipes for doing this collective.recipe.distutils 0.1 and zerokspot.recipe.distutils 0.1.1. The later module a derivative of the former, and is a little more convenient then the first, but the both suffer from the same problem, which I will describe now. When bootstrap.py is executed, it downloads zc.buildout package and puts it into buildout's eggs directory. This gives ./bin

问题 Pros and cons? I'm personally using buildout for my django projects but thinking of switching to virtualenv + pip for its simplicity. 回答1: At the core, buildout and pip+virtualenv do the same. They both use python packages, install them, isolate them from the rest of your python environment, handle dependencies (through setup.py) and so on. Buildout does more. Which, naturally, means a bit more configuration than with pip. You'll have to figure out whether the extra configuration is worth the

问题 I am messing around with the combination of buildout and virtualenv to setup an isolated development environment in python that allows to do reproducible builds. There is a recipe for buildout that let's you integrate virtualenv into buildout: tl.buildout_virtual_python With this my buildout.cfg looks like this: [buildout] develop = . parts = script virtualpython [virtualpython] recipe = tl.buildout_virtual_python headers = true executable-name = vp site-packages = false [script] recipe = zc

问题 In my setup.py file, I've specified a few libraries needed to run my project: setup( # ... install_requires = [ 'django-pipeline', 'south' ] ) How can I specify required versions of these libraries? 回答1: I'm not sure about buildout, however, for setuptools/distribute, you specify version info with the comparison operators (like == , >= , or <= ). For example: install_requires = ['django-pipeline==1.1.22', 'south>=0.7'] 来源： https://stackoverflow.com/questions/8161617/how-can-i-specify-library

问题 I have multiple projects that shares child apps with other projects . When working within the project directory I want to be able to make changes to the app , update it, and pull those updates into the second project . Requirement: No use of symbolic links (my IDE's debugger doesn't work well with them) No compiling/rerun a script. I would like to make changes to the app without having to rerun a script/buildout. Apps must be within the project folder. Here's the structure: app_one (git repo)

问题 According to Google App Engine Third Party Libraries Support, the latest version of lxml supported is 2.3 https://cloud.google.com/appengine/docs/python/tools/libraries27 And python-pptx requires lxml >= 3.1.0 https://github.com/scanny/python-pptx/blob/master/requirements.txt So what's the best way (if possible) to run python-pptx on GAE ? Note: I'm using buildout to deploy my applications, and that where those restrictions fail. Thanks! 回答1: App Engine isn't compatible with that library so

问题 Is it possible? I would like to install it in a 3.1.7 Plone instance, but don't want to enter the buildout incompatible versions hell. I tried in my machine, adding along with collective.alias extends = http://good-py.appspot.com/release/dexterity/1.0a2 and [versions] plone.recipe.plone = 3.1.7 plone.recipe.zope2instance = 3.6 But starts downloading a lot of stuff, until it downloaded Plone 4 egg itself as a dependency. I couldn't find a source of really pinned versions for 3.17 that would

问题 I am trying to install a project named "BOSS". This is what i got when i tried to run bin/buildout -c frontend.cfg . You can check the whole installation step on HERE. <USER>@ubuntu:/opt/boss$ sudo bin/buildout -c frontend.cfg Installing frontend-admin. npm WARN package.json boss-admin@1.0.0 No description npm WARN package.json boss-admin@1.0.0 No README data npm WARN package.json angular-perfect-scrollbar@0.0.5 No repository field. npm WARN package.json eslint-plugin-class-property@0.0.3 No