virtualenv - Which options for python deployment do I have if GCC not working anymore -


my python buildout-based production environment moved admins chroot. rerunning buildout fails because compiler(gcc) exits error while compiling package c-extensions (pil, zodb).

_imaging.c:3403: error: (near initialization 'functions[39].ml_meth') error: setup script exited error: command 'gcc' failed exit status 1 

admins told me gcc broken in chroot. of course strange , not viable situation , fixed asap.

but using buildout/virtualenv since years. interested in options still have updating buildout-based python deployment while gcc broken. ran buildout, if removed dependencies (in buildout.cfg or packages setup.py) trigger gcc compilation, got me left uncomplete application startup scripts. packages downloaded/assembled/compiled, buildout recompiles part has changed somehow (i know .installed.cfg).

how can or python developer not responsible system administration continue using strengths of buildout deployment in such situation? open suggestions , want discuss , learn pros , cons.

build elsewhere, on build host -- run buildout in place can run (a box of same architecture running gcc) -- integrate fabric build environment push build deployment host. have not done this, assume have write of means push need (e.g. built eggs, develop-eggs, src, parts, bin directories) server in fabfile.


Comments

Popular posts from this blog

html - How to style widget with post count different than without post count -

How to remove text and logo OR add Overflow on Android ActionBar using AppCompat on API 8? -

javascript - storing input from prompt in array and displaying the array -