topic Modify all Script File Paths in Custom Toolbox? in Python Questions

Modify all Script File Paths in Custom Toolbox?

MicahBabinski — Mon, 18 May 2015 20:44:25 GMT

Greetings,

I have a custom toolbox called "Micahs_tools.tbx" which I have built up over a couple of years:

The toolbox contains 94 tools. Initially I saved the source Python scripts in a network location, but for various reasons I have moved the directory which contains the scripts to a local drive. Now I'm wondering if there's a Python way to get at the paths to those scripts and change them to reflect the new location of the scripts.

Is this possible, and how would it be accomplished?

Thanks!

Micah

Re: Modify all Script File Paths in Custom Toolbox?

curtvprice — Tue, 19 May 2015 05:18:14 GMT

Was the toolbox originally located on the same disk as the scripts? Relative paths make this process transparent, i.e. you can move the scripts and the toolbox together and the paths will resolve automatically.

You can also embed (import) scripts into the tbx file - if the paths are correct when you do it.

Re: Modify all Script File Paths in Custom Toolbox?

MicahBabinski — Tue, 19 May 2015 14:56:16 GMT

Alas, no, the scripts were saved on a network share and the .tbx is on my C drive. Does that mean it can't be done?

Re: Modify all Script File Paths in Custom Toolbox?

BillDaigle — Tue, 19 May 2015 16:11:16 GMT

I don't think you can get to the raw code in a tbx file. You might, however, be able to convert the tbx to a pyt using the following tool: http://www.arcgis.com/home/item.html?id=83585412edd04ae48bdffea3e1f7b2e7. I haven't tried it, so I'm not sure what complexity it will introduce. Once the tool is in the pyt, updating the scripts paths should be relatively simple.

Re: Modify all Script File Paths in Custom Toolbox?

curtvprice — Tue, 19 May 2015 18:26:03 GMT

No it can't be done -- they are binary files that you cannot access in Python. If you look there is text embedded in the tbx file, but that's just the metadata - tool documentation (XML code).

The only way to do this is to go through and update the script paths one by one for your 94 tools. If you go to relative paths [or embed the scripts in the tbx, or do Bill's suggestion to make a pyt], from here on out you will never have to do it again. Personally I like leaving the scripts outside the toolbox where I can easily edit them.