CV-Toolbox does not load in R17

[Donovan Keith]

Hey Rick,

CV-Toolbox is not loading in R17. My guess is because you've source-protected/compiled some libraries you're importing. R17 uses a different Python version than R16, and any source-protected files must be compiled w/ that version.

-Donovan

[Rick Barrett]

Have you explored this at all - are 2.7 byte-compiled modules backwards compatible with 2.6, or do we have to include separate versions for R17+ and R16-

[Donovan Keith]

Need two separate ones, and I'm not sure if there's a method for differentiating on import. We'll probably need two separate folders (one for R16, one for R17) and only install R17.

[Rick Barrett]

That . . . sucks. Toolbox will manage it for all other stuff I guess, but it's going to suck for Toolbox. It's even worse that it's not at a full version release but SP1, which means we have to get real specific about which release.

I wonder if there's a way I can fail friendly (like if you can try import and show a warning dialog). I'll have to investigate.

[Rick Barrett]

Ok - looks like maybe we can still have a single folder structure.

Niklas provided some info on PluginCafe:

if sys.version.startswith('2.7'):
  module_path = 'res/modules_27'
else
  module_path = 'res/modules_26'

with _localimport(module_path):
  import module_a
  import module_b

[Donovan Keith]

That's encouraging at least. Also, we need to modify how we're handling our imports on all of our plugins and use Niklas' new crazy long import boiler plate. The ugly imports are one of the biggest issues I have w/ our Python implementation. Not sure if there's an easy solution.

[Rick Barrett]

So the localimport code needs to be pasted directly into our plugin code, not as an external file? Is that right?

[Donovan Keith]

https://gist.github.com/NiklasRosenstein/f5690d8f36bbdc8e5556

Needs to be used instead of his c4dtools importer library.