Clever Geek Handbook

Building Django on windows

For my django projects, I've created a nice workflow. Using buildout to "bootstrap" a project and applications that I have developed from versioning. The rest of the packages and applications are installed from pypi. I am working on ubuntu and my servers are on ubuntu. It works like a charm.

There is now a new developer working on windows. It has a lot of problems when construction work works the same way I use it.

Is there a specific way or another way to use buildout to customize it for Windows?

using a simple install seems to be the problem ....

Windows user: I have installed numpy and matplotlib with installers for windows (x64). But buildout is still trying to compile matplotlib. Compilation doesn't work. I tried GCC as a compiler. Can I prevent assembly from building and using installed packages?

+3


source to share


1 answer


If something has a dependency on numpy or matplotlib, buildout will try to install it, period. So, you have two main solutions:



  • Don't explicitly state whether you want numpy or matplotlib. Depending on this, you and your colleague have already installed it around the world. Buildout won't try to install what it doesn't know about :-)

  • Use syseggrecipe to explicitly tell buildout to look for a package in your global installation:

    [buildout]
parts = 
    sysegg
    django
    ....

[sysegg]
recipe = syseggrecipe
eggs =
    matplotlib
    numpy

[django]
recipe = djangorecipe
....

    Make sure the sysegg part is near the very top of the parts list. syseggrecipe puts a link to your globally installed version in the build directory develop-eggs/

    , thereby signaling the existence of the package.

    Warning: I'm not sure if syseggrecipe works 100% on windows since it uses symbolic links. Pull requests that fix it (if this turns out to be a problem) are welcome.

+1


source






More articles:


All Articles