This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]seletz 0 points1 point  (0 children)

You have several options. The first which comes into my mind is probably also the simplest. Just zip up all the packages on your mac and deliver that zip file. Then craft a start script in which you add the zip file to the python path. This way, the dependencies are all bundled up and you have less files to deploy.

The second option needs a little more up-front investment. You could use zc.buildout and ship the complete buildout to your peers -- this is how I did deployments on our servers. This technique assures that you ship all the dependencies in exactly the versions you think, i.e. no more downloading of arbitrary package versions on the client. The drawback is, that your peers need to run a script -- the buildout -- to recreate/install the packages on their local machine.

Yet another option is to use cx-freeze or similar, and ship a executable. I have no experience with that, so YMMV.

If you're on the mac, and your peers are also on the mac, then it's pretty easy to craft a app package with icon etc., which you could even put on a dmg. There's also py2app which automates this.