This shows you the differences between two versions of the page.
| |
| indigo_2024.2_documentation:python_packages [2025/02/18 20:36] – created - external edit 127.0.0.1 | indigo_2024.2_documentation:python_packages [2025/04/25 23:00] (current) – [Using a "requirements.txt" File] davel17 |
|---|
| websocket-client==1.7.0 | websocket-client==1.7.0 |
| </code> | </code> |
| | |
| | <color purple>**Best Practices:**</color> |
| | |
| | If you're using GitHub, be sure that the contents of the ''//../Packages//'' folder is included in your ''//.gitignore//'' file. This will ensure the ''//Contents/Packages/pip-install-log-success.txt//'' and any other content is not included as a part of your package. When testing your plugin, you should include any needed binaries in this folder so when you publish an update, the binaries will not be included. |
| |
| <color purple>**Troubleshooting:**</color> | <color purple>**Troubleshooting:**</color> |
| |
| If you find that packages are not being installed when a user installs/updates your plugin, one cause might be that you have a //''Contents/Packages/pip-install-log-success.txt''// file left over in your plugin bundle. If it's in the bundle, Indigo will assume the packages are already installed. | If you find that packages are not being installed when a user installs/updates your plugin, one cause might be that you have a //''Contents/Packages/pip-install-log-success.txt''// file left over in your plugin bundle. If it's in the bundle, Indigo will assume the packages are already installed. |
| | |
| | If you're working on transitioning from included binaries to using a ''//requirements.txt//'' file, be sure to remove the deprecated binaries from your package. If they're present, Indigo may favor those over the libraries you're trying to install automatically. |
| |
| == Manual Installation by User == | == Manual Installation by User == |