Module Not Found
ModuleNotFoundError: No module named 'xxxx'
If your script runs into this issue, there's a few likely scenarios:
- You haven't provided the right External Package Dependendencies on the requirements tab or through a
- You have provided a package incorrectly, either by:
- Including a typo in the package name.
- Not formatting the version number properly.
- Listing a version that doesn't exist.
- Listing a version that's not compatible with Python 3.7.
- When pulling code from our Git sync, you've simultaneously provided Python Packages in the UI and a
requirements.txtfile in your repository. You'll need to use one or the other. Providing both results in two separate
pip installcommands which can result in package installation issues.
- You've provided a package that has additional system package dependencies. For example:
psycopg2requires that you install
libpq-devas a system package. Alternatively, you can use
psycopg2-binaryto avoid the extra dependency.
sparkrequires that you install
scalaas system packages.
JayDeBeApirequires that you install
default-jreas a system package.
To test this out on your local machine, you can spin up a new virtual environment and pip install packages one by one. If one throws an error, that's your culprit.
If pip runs into a single error during installation, it will fail to install all remaining packages listed, so the the package listed in the error may not be the one causing an issue.
No such file or directory
Beginning of Output
If this error appears printed at the beginning of your output and your Vessel appears to never run, the likely culprit is due to the File to Run field either containing, or not containing, the correct folder name.
- If you're using a Git Connection, make sure to follow these instructions to reference the file name correctly.
- If you're not storing files in a folder structure, make sure the File to Run field only contains the file name.
- If you are using a folder structure, make sure the File to Run field contains the exact location of the file.
Middle/End of Output
If this error appears towards the end of your output and your Vessel appears to have run partially, the likely culprit is that your code is referencing the wrong file name or location.
It is sometimes difficult to remember all of the files that would be available to your Vessels in a Fleet. We recommend this guide to list all available files so you can better visualize the file names.