Ashesh Vashi 7767c085c3 Resolved an issue finding the python interpreter on *nix systems, and ... Windows 2008 R2 (32 bit), while running the pgAdmin 4 as runtime for the PostgreSQL one click installers. - Found a typo in runtime code, we were appending the path using ';' on *nix systems too. We should have used ':', and that did not allow the os.environ['PATH'] to identify the correct path of the python interpreter under the 'venv' directory. - On Windows 2008, it was not honouring the environment variables, set under the Qt application (e.g. pgAdmin4.exe runtime), in the python application. (e.g. pgAdmin4.py). We will need to assume that - the python interpreter resides under the 'venv' directory outside the 'bin' directory. - Also, on windows 2008, it was setting PYTHONHOME environment variable to the full path of the pgAdmin4.exe, we need to reset it to 'venv' directory, if we find the python interpreter under it. Thanks Murtuza Zabuawala for tips, and help.		2017-03-10 21:19:06 +05:30
..
pgadmin	Resolved an issue finding the python interpreter on *nix systems, and	2017-03-10 21:19:06 +05:30
regression	Create screenshots when feature tests fail.	2017-03-09 15:34:51 +00:00
babel.cfg	Include SQL templates in the translation template.	2016-11-14 11:53:20 +00:00
config.py	Disable HTMLMIN with Python 2.6 as it doesn't work on that older version.	2017-03-09 15:21:52 +00:00
pgAdmin4.py	Fix the issue where Import/Export was failing in linux runtime. Fixes #2166	2017-03-09 09:54:55 +00:00
pgAdmin4.wsgi	Fix WSGI support.	2016-08-18 13:43:00 +01:00
setup.py	Resolved quite a few file-system encoding/decoding related cases.	2017-03-07 15:31:03 +05:30