atom-community / atom-community/ide-python
Third-party module classes not detected when setting PYTHONPATH in a shell file
- Langage dominant
- JavaScript
- Étoiles
- 238
- Forks
- 40
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
I've defined a shell script inside the root of my project, called `run.sh`. What it does is, adds two paths relating to a third-party module (GAMS Python API), to `PYTHONPATH` environment variable, and then calls python with all arguments given to the script:
```bash
#!/bin/bash
export PYTHONPATH=/opt/gams/gams34.3_linux_x64_64_sfx/apifiles/Python/api_39/:"$PYTHONPATH"
export PYTHONPATH=/opt/gams/gams34.3_linux_x64_64_sfx/apifiles/Python/gams/:"$PYTHONPATH"
export PYTHONPATH="$(pwd)":"$PYTHONPATH"
python3 $@
```
In the package settings, I've configured the python path to `./run.sh`, for the script to be called and the module being detected by the package.
However, after updating the package version to 1.9.4, it no longer detects the classes inside the `gams` module:

Note that, _the script works perfectly with 1.9.3_. I downgraded the package and then upgraded it, and it seems it is reproducable for me.
(I don't think the system specs are needed, as I just mentioned, the issue is new in 1.9.4, with exact set of packages and Atom version)
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par reproduire la détection manquante de la classe GAMS avec le run.sh fourni et comparez les versions 1.9.3 et 1.9.4 du package. Suivez la manière dont le package invoque le chemin Python configuré et lit PYTHONPATH. Le travail est terminé lorsque les classes du module gams sont à nouveau détectées lors de l’utilisation de run.sh.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- bash, javascript, python
- Domaine
- tooling
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100