Third-party module classes not detected when setting PYTHONPATH in a shell file

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)

Empieza reproduciendo la detección faltante de la clase GAMS con el run.sh proporcionado y compara las versiones del paquete 1.9.3 y 1.9.4. Rastrea cómo el paquete invoca la ruta de Python configurada y lee PYTHONPATH. Se considera terminado cuando las clases dentro del módulo gams vuelvan a detectarse al usar run.sh.

Escrito por el modelo de indexación a partir del texto del issue.