Re: [pgadmin-support] Cannot compile pgadmin4 mainline - Mailing list pgadmin-support

Ah thanks.  It was just odd it didn't keep the settings from before i 
upped my local git.

I searched my email history left and right trying to find where you had 
helped me previously, but I couldn't find anything and got stuck.  A 
user not knowing anything beforehand, seeing 'Python Path' is a bit 
misleading without knowing the internals and how this parameter gets used.

I'll make some notes in my local README on this so I don't have to fight 
this next time.

It would be really great if some sort of automatic virtualenv was set up 
and used as part of the startup.  It's pretty easy to auto detect where 
the virtualenv tools are located on major distros, and worst-case, it 
can always fall back to spit out a note saying 'here's how you do it 
manually'.



On 12/13/2016 04:05 AM, Dave Page wrote:
> On Mon, Dec 12, 2016 at 9:17 PM, Mark Murawski
> <markm-lists@intellasoft.net> wrote:
>> Thanks, That worked.
>>
>> Now I'm back to this again:
>>
>> markm {~} markm$ source /usr/share/virtualenvwrapper/virtualenvwrapper.sh
>> markm {~} markm$ workon pgadmin4
>> (pgadmin4)markm {~} markm$
>>
>>
>> (pgadmin4)markm {~} markm$ download/pgadmin4/runtime/pgAdmin4
>> Python path:  "/usr/bin/python3.4"
>> Python Home:  ""
>> Webapp path:  "/home/markm/download/pgadmin4/web/pgAdmin4.py"
>> Traceback (most recent call last):
>>    File "/home/markm/download/pgadmin4/web/pgAdmin4.py", line 24, in <module>
>>      from pgadmin import create_app
>>    File "/home/markm/download/pgadmin4/web/pgadmin/__init__.py", line 17, in
>> <module>
>>      from flask import Flask, abort, request, current_app
>> ImportError: No module named 'flask'
>> "Failed to launch the application server, server thread exiting."
>>
>> Python Path: /usr/bin/python3.4
>> Application Path:
>> /home/markm/.virtualenvs/pgadmin4/lib/python3.4/site-packages
>> ls -al /home/markm/.virtualenvs/pgadmin4/lib/python3.4/site-packages | grep
>> flask
>> drwxr-xr-x 1 markm markm  422 Nov  1 13:11 flask
>> drwxr-xr-x 1 markm markm   90 Nov  1 13:11 flask_babel
>> drwxr-xr-x 1 markm markm   64 Nov  1 13:11 flask_gravatar
>> -rw-r--r-- 1 markm markm  881 Dec 11 20:02 flask_htmlmin.py
>> -rw-r--r-- 1 markm markm  33K Nov  1 13:11 flask_login.py
>> -rw-r--r-- 1 markm markm  18K Nov  1 13:11 flask_mail.py
>> -rw-r--r-- 1 markm markm  14K Nov  1 13:11 flask_principal.py
>> drwxr-xr-x 1 markm markm  354 Nov  1 13:11 flask_security
>> drwxr-xr-x 1 markm markm   64 Nov  1 13:11 flask_sqlalchemy
>> drwxr-xr-x 1 markm markm  154 Nov  1 13:11 flask_wtf
>>
>>
>> I'm using the same path as last time, but it cannot find what it needs...
> The Python Path setting should include all directories that have the
> Python components in them. From what I can see above, shouldn't it be
> set to /home/markm/.virtualenvs/pgadmin4/lib/python3.4/site-packages
> instead of /usr/bin/python3.4 (which I assume is the Python command
> line interpreter, which pgAdmin doesn't care much about)?
>