You can add any directory to the PYTHONPATH environment variable before 
launching Nuke.

Alternatively, you can call sys.path.append('/path/to/external/site-packages') 
in an init.py or menu.py.

-Nathan



From: Howard Jones 
Sent: Monday, March 04, 2013 2:23 PM
To: Nuke Python discussion 
Subject: Re: [Nuke-python] wxPython in Nuke

Thanks Nathan

Yes it was unable to find the wx module and I cant find a way to copy the files 
across correctly.
Only question now then - anyone know how to install this into Nuke? Or link 
Nuke to an external python?



Cheers

Howard



------------------------------------------------------------------------------
  From: Nathan Rusch <nathan_ru...@hotmail.com>
  To: Howard Jones <mrhowardjo...@yahoo.com>; Nuke Python discussion 
<nuke-python@support.thefoundry.co.uk> 
  Sent: Monday, 4 March 2013, 18:34
  Subject: Re: [Nuke-python] wxPython in Nuke


  "Error interpreting this plugin" is Nuke’s way of masking an actual Python 
exception for GUI purposes. If you check the Nuke terminal, you should see the 
Python traceback, which will give you more information about what’s going on.

  My first guess would be that you’re either missing an underlying library or 
running into a binary-compatibility issue.

  -Nathan



  From: Howard Jones 
  Sent: Monday, March 04, 2013 2:33 AM
  To: Nuke Python discussion 
  Subject: [Nuke-python] wxPython in Nuke

  Hi 



  This is probably a simple issue and therefore a dumb question, but I'm 
testing out wxPython and have a simple test script.


  #!/usr/bin/env python

  import wx

  def test():
      nuke.message('Boo!')


  Simply without the 'import wx' line,it works - with, it doesn't. 
(RuntimeError: 
/Volumes/1_media/application_support/Nuke/nukeSettings/nukePython/test.py : 
error interpreting this plugin)

  So I've tried adding wx to Nukes internal python site-packages which I'm not 
sure is necessary. Same issue.

  So 

  1) Is this even possible (wx via Nuke)

  2) Do I need to add wx to the site package inside Nuke, or is this handled 
anyway by the shebang and therefore pointing to the already installed wx.
  3) Or is this likely to be an incorrect version for Nukes 2.6 python (I 
installed for 2.7)



  I should add that wxPython is installed and working correctly with 2.7 
outside of Nuke.


  Howard


------------------------------------------------------------------------------
  _______________________________________________
  Nuke-python mailing list
  Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
  http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python






--------------------------------------------------------------------------------
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python

Reply via email to