atom-community / atom-community/atom-script
ModuleNotFoundError: No module named 'boto3'
- Dominant language
- JavaScript
- Stars
- 730
- Forks
- 264
- PR merge metrics
- No merged PRs in 30d
Description
Running atom 1.24.1 from console in pipenv with Python3.6.4
**Code runs from console in venv; one of four imports fails through atom**
_import boto3 <<<< fails
from botocore.exceptions import ClientError <<< in same library as boto3
import pickle
from io import BytesIO_
Here's startup with ECHO $PATH
(pelican-env-0QFAzI3g) (xenial)les@localhost:/home/les/pelican-env$ echo $PATH
/home/les/.local/share/virtualenvs/pelican-env-0QFAzI3g/bin:/home/les/.local/share/umake/bin:/home/les/bin:/home/les/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
(pelican-env-0QFAzI3g) (xenial)les@localhost:~/pelican-env$ atom .
Seems strange that the one import fails and the others don't
Is there a way to see what PATH atom/script is working from? Where does script get it's PATH?
Any ideas?
Contributor guide
Research direction
Start by reproducing the import failure with Atom 1.24.1, pipenv, and Python 3.6.4, comparing the Atom Script environment with the working console virtual environment. Inspect how the Atom Script entry point receives PATH and selects the Python interpreter. Done means explaining or correcting why boto3 fails while the other imports work, with a documented reproduction or regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100