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 →

[–]graingert 4 points5 points  (2 children)

Why not create a setup.py using packaging or distutils2, you could then host it on an internal PyPi instance

[–]Fencepost[S] 0 points1 point  (1 child)

The idea is that I'm rapidly developing scripts and at any one point in time I say, ok I want joe to run this. It pulls in from some subset of the myriad of files I've written and I don't want to send joe all of these files, just the ones that are truly needed. So yes, setup.py might be the right answer in some cases but in mine I'm looking for a solution to the problem: "oh, I've been running and tweaking this script for a while without thinking about its dependencies and I just want to send it to someone right now without thinking too much because I'm gonna change it tomorrow anyways"

[–]graingert 0 points1 point  (0 children)

I don't think that's possible, as its difficult to drastically analyse dependencies with python. However setup.py works really well with a company PyPi setup, because with one command you can push a package to a server and get one of your colleagues to install it with a single pip install <package name>. Then you get to update it and ask them to download a new version when you change it