2022.1.1.30569 Patch Release Update

The 2022.1.1.30569 Patch/Minor release has been removed from the Download Portal due to a missing signature in some of the included files. This causes the files to not be recognized as valid files provided by Alteryx and might trigger warning messages by some 3rd party programs. If you installed the 2022.1.1.30569 release, we recommend that you reinstall the patch.

Dev Space

Customize and extend the power of Alteryx with SDKs, APIs, custom tools, and more.

Option to run custom Python script during installation

11 - Bolide

The Python SDK offers a possiblity to automatically install Python packages through pip when installing using the requirements.txt. Some changes to the virtual environment of the tool might not be covered by this: For example, downloading and configuring language models for spaCy cannot be solved through the requirements.txt alone (similar for training corpora for NLTK).


So, as an idea for future versions of the SDK: Allow us to specify a Python script that is run when a tool is installed. This way we might be able to set up the environment, load additional tools etc.

Alteryx Community Team
Alteryx Community Team

I think this is a good idea, I'd suggest you add it here.


I don't have personal experience with spaCy (although I know @JPKa does), but I believe NLTK checks to see if something has already been downloaded before starting the download. So while not as efficient as your proposal, a reasonable workaround would be to download the training corpora in the plugin script itself. It would take longer to run the workflow the first time the tool is ever used, then be much faster thereafter.

11 - Bolide

Hi Neil,


I will add it to the idea section - wasn't sure if the section was also for SDK-suggestions. :) See here: https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Running-custom-scripts-during-Python-tool-in...


Using the first run of the plugin is definitely an option. But users might think something is wrong, if download and installation takes 5 minutes or so and they don't know what's happening. Currently, I simply deploy the language models along with the plugin in the yxi. This makes the installer quite large, but at least the model is available directly.


Moreover, this would also allow to install packages not available through `pip`.