pros/cons of loading python modules from network location -
i wondering downsides loading python modules network location?
i've developed few dozen python tools , want share them across team , each computer has python27 locally installed. not have necessary modules tool's use. there may total of 2 additional modules tool needs import. i've decided place these modules on network. in tool have:
sys.path.append('z:\\pipeline\\site-packages') import shotgun
is horrible idea? find super easy manage , rather trying manage installing kinds of packages on users computers , whatnot.
i'm assuming wouldn't taxing load modules dozens of artists across network, since 1 tool loaded module no longer needs communicate network, right?
how many machines/users have in team? structure of network location? size of files(modules) have there? possible users try load modules in same time?
basically if team small, shouldn't worried it. not best solution (mostly because can install these modules using pip install
or easy_install
, if team getting bigger (or if use cluster , try run same code on 1000's machines concurrently) - might have problems there.
if storage not designed multiple machines-access (caching/distributing/raid) - might trouble if big.
you can read more distributed file systems give solution such cases.
Comments
Post a Comment