2016-11-11, 15:15
(2016-11-11, 08:05)jonjon Wrote: A long post I know, but it's clearer to see the whole thing.
Hope it helps
This is exactly what I'm seeing as well.
If the variables are commented out, the environment lookup returns None. The code that checks for that and replaces it with a default value isn't working (and neither was using a default value in the getenv call). So there seems to be something strange about how os.getenv returns when the environment variable doesn't exist at all (vs. it existing and being empty).
Maybe this is specific to the python interpreter being used by AWS Lambda?