I definitely agree on using the central location on a server. An additional option if you are concerned about load time or network traffic is to rsync or robocopy from the central location to the local machine before each launch of Nuke. And then use the local plugin path.
On Sat, Jul 16, 2011 at 2:08 AM, Sebastian Elsner <[email protected]>wrote: > Thanks Nathan for your opinion. This is what I was thinking too. > > Am 15.07.2011 18:35, schrieb Nathan Rusch: > > I'd say the universally understood Rule #1 goes something like, "Thou >> shalt not modify the local installation in any way." Doing so can make >> things a pain to debug or keep up to date if you end up changing >> versions and are suddenly faced with missing libraries or modules, >> especially if you've forgotten which ones were locally installed. >> >> Use a central location as your primary plugin path, and come up with a >> logical directory structure to keep things organized. Yes, it will >> probably be a little slower to load, but a few extra seconds of startup >> time is nothing compared to the time you'll waste messing around with >> people's local machines otherwise. In my case, if I need some small >> platform-independent additions that I don't want to roll out to the >> facility (for dev work, etc.), I'll drop them into a local init/menu >> combo with a very clear menu label. >> >> -Nathan >> >> -----Original Message----- From: Sebastian Elsner >> Sent: Friday, July 15, 2011 9:20 AM >> To: Nuke Python discussion >> Subject: [Nuke-python] python 3rd party library location >> >> Hi, >> >> I have been wondering how others tackle the problem where to place >> python extensions like the mysql driver or sqlalchemy to have them >> available inside the nuke python interpreter. Do you place them in >> PYTHONPATH or right with the nuke installation? Putting them to the >> PYTHONPATH on a fileserver may be slow at importing, but is easy to >> maintain. Right in the Python site libs dir seems a bad solution when >> installing new bugfix versions. Maybe use a local PYTHONPATH... >> Suggestions for best practices welcome! >> >> cheers >> >> Sebastian >> >> > -- > Sebastian Elsner - pipeline td - r i s e | fx > > t: +49 30 20180300 [email protected] > c: +49 175 3365739 www.risefx.com > > > r i s e | fx GmbH > Schlesische Strasse 28 Aufgang B, 10997 Berlin > Geschäftsführer: Sven Pannicke, Robert Pinnow > > ______________________________**_________________ > Nuke-python mailing list > Nuke-python@support.**thefoundry.co.uk<[email protected]>, > http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/> > http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-python<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python> >
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
