On Mon, Sep 5, 2016 at 8:15 PM, Albe Laurenz <laurenz.a...@wien.gv.at> wrote:
> Dave Page wrote: > >>>> mod_wsgi (pid=20880): Target WSGI script > '/opt/pgadmin4/pgAdmin4.wsgi' cannot be loaded as Python module. > >>>> mod_wsgi (pid=20880): Exception occurred processing WSGI script > '/opt/pgadmin4/pgAdmin4.wsgi'. > >>>> Traceback (most recent call last): > >>>> File "/opt/pgadmin4/pgAdmin4.wsgi", line 8, in <module> > >>>> from pgAdmin4 import app as application > >>>> File "/opt/pgadmin4/pgAdmin4.py", line 58, in <module> > >>>> app = create_app() > >>>> File "/opt/pgadmin4/pgadmin/__init__.py", line 204, in create_app > >>>> import pgadmin.utils.paths as paths > >>>> AttributeError: 'module' object has no attribute 'paths' > >>>> > >>>> Indeed there is no pgadmin/utils/paths directory with a __init__.py > in it. > >>> > >>> No, but there should be a pgadmin/utils/paths.py file. Is that there? > >> > >> Yes, there is, and it is readable to everyone. > >> > >> I don't know much about Python - could it be that version 2.7 handles > this > >> line differently from 3? > > > > No - I do all my development on 2.7 and it works fine (as do most of > > the other devs I believe). 3.x is definitely less well tested, and 2.6 > > is behind that. > > > > Ashesh, any ideas what could be causing this? > I can think of existing .pyc files, which can cause this kind of problems. -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company <http://www.enterprisedb.com/> *http://www.linkedin.com/in/asheshvashi* <http://www.linkedin.com/in/asheshvashi> > > Must have been something weird; a web server restart fixed the problem. > > Thanks for the help; it is working now. > > I'm kind of surprised that pgAdmin4 is already a release candidate, I still > find lots of bugs just randomly clicking around. > I'll report them of course. > > Yours, > Laurenz Albe >
