10 Jan
2009
10 Jan
'09
8 p.m.
At 10:21 AM 1/10/2009 -0800, rayterrill wrote:
They're going to be distributed to over 800+ locations internally, so I was looking for a repeatable structured mechanism to deploy the code and verify that it was installed correctly, vs. just copying the files into the python sys.path and hoping they're there when they need to be run (how it currently is working).
In that case, an egg is a good choice.