I do something like this in my init.py
import nuke
from os.path import expanduser, join
import sys
home_dir = expanduser('~')
nuke_base_dir = join(home_dir, '.nuke')
for extra_path in [nuke.NUKE_VERSION_STRING, 'shared']:
new_path = join(nuke_base_dir, extra_path)
nuke.pluginAddPath(new_path, addToSysPath=True)
this allows me to build plugins in my home account per Nuke version
along with a shared directory.
Kevin
On 1 March 2017 at 15:14, John Coldrick <[email protected]> wrote:
> This is a challenge we have and I'm getting slow reactions from Foundry so I
> thought I would ask the Braintrust. :) Essentially I'm just wondering if
> you can if/then your way out of this problem, can I start either 9 or 10
> from a single init/menu.py and end up with properly sourced plugins? The
> biggest single challenge we have is we're trying to do with *without* using
> $NUKE_PATH, which drives a different init.py.
>
> Not really asking for a walkthrough, but just wondering if anyone happens to
> know if it's trivial/tough/impossible to do. If the recommended way really
> is not using a single configuration but wrapping in NUKE_PATH, that's fine.
> It really seems to be an issue of the startup order.
>
> Appreciate any thoughts! We're on Windows if it matters.
>
> Thanks
>
> J.C.
>
> _______________________________________________
> Nuke-users mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
*Framestore* | Kevin Wheatley | Head of Imaging
*London* - New York - Los Angeles - Montreal
19-23 Wells Street, London, W1T 3PQ
T: +44 (0) 20 7344 8000
framestore.com <http://www.framestore.com/>
Facebook <https://www.facebook.com/Framestore>
Twitter <http://twitter.com/Framestore>
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
