Rank n00b question, will portable python work on a USB stick with a portable Reaper install? I've been playing with it this evening without much luck. --------------------------- ReaScript error --------------------------- Failed to load/initialize reascript Can't open E:\Portable Python 3.2.1.1\App\python32.dll --------------------------- OK ---------------------------
Did you tell Reaper where python is located ? This is to be done on Options -> Preferences -> Plug-ins -> Reascript. Put your own "Custom path to dll directory".
If you'll get the portable python working with Reaper where it doesn't crash anymore but none of the scripts will do anything either, you are in a stage I've been quite a long time already. If you get the scripts working too, I'm eager to hear what you did.
--------------------------- '95 325is M-tech kit Hamann DTM Front Splitter Ellipsoids w/ HID AA Gen3 Exhaust
Well, this seems to work so far but I'm too new to scripts to give it a proper test. Here's what I did: 1. Download the 64 bit MSI installer 2. Used to install Python on my USB stick. I did a full install into a subdirectory. At this point there's a little niggle. Even though you tell the installer to use the USB stick, it puts the python32.dll in c:\windows\system32. I simply moved it into the top level of the subdirectory I created in step 2. I went into preferences and enabled scripts, browsed to the subdirectory on the USB stick and Reaper found the .dll. To test, I created a Test.py file with 'RPR_APITest()' as the only line. Seems to execute fine, I get the 'test OK' message. At this point I'm about as far as I can go testing wise. Maybe over the next couple days I'll get a chance to play with it a little more. Edit: I don't have any reason to try it but I imagine this would work with the 32 bit MSI as well. That's assuming this actually works and I'm not barking up the wrong tree. Edit 2: Got to thinking that browsing for the path is a bad idea. It will include the drive letter which may not be the same on a different computer. Entering \<subdirectory> in the 'Custom path to dll directory' field seems to work. Edit 3: Oy. This works but it's not portable. The search continues.
Thanks for investigating this issue Toitoy! Unfortunately manual registry changes won't make it truly portable, unless one is willing and able to do that with every host. And working at home machine there is not necessarily any need, since one might as well install and use python in the host.
--------------------------- This message brought to you by the society for knowing what you're talking about when you post. Omega8: The smartest peanut in the turd
Yes it is true. I'm not a programmer, but I think it's the problem with Reascript module, which searches only for python.dll and doesn't understand that folders "Lib" and "Dlls" are in the same folder.