ModuleNotFoundError: No module named 'src.Config' about platypus HOT 13 CLOSED

Looking into this ASAP. Thanks.

from platypus.

@lucas-torres Unable to replicate this issue, how did you clone the repository? Could you do a quick directory listing of src/ as well?

from platypus.

Same issue here, this is the listing for src/:

• Aor.py
• cache
• Config.py
• ServerHandler.py
• Slackbot.py
• static
• templates
• Tornado.py

from platypus.

@kliptonize Odd, I don't seem to be able to replicate this either by downloading a fresh latest release or cloning the repository. Could you copy the contents of Config.py into a reply? Really want to get to the bottom of this.

from platypus.

Okay, cloning to a fresh VPS seems to produce the same issue, I will be taking a closer look at this tonight and should have a solution pushed out tomorrow (if my power sticks around).

from platypus.

Update: @kliptonize @lucas-torres Would you guys mind doing a python --version just to confirm a suspicion I have? This bug may be due to Python 2 not having the same import methodology as Python 3 (in which Platypus is developed, and is made clear through the docs).

from platypus.

Sure thing, mine is Python 2.7.12, shall I update, or wait for a fix?

(Installed Python 3.5.2 next to it, throws a ImportError: No module named 'MySQLdb' error)

from platypus.

Python 3.6.2 :: Anaconda, Inc. Here

from platypus.

@kliptonize You'll want to run pip install -r requirements.txt

@lucas-torres Looking into this if it's persisting on Python 3.6.2

from platypus.

Sadly, the problem remains, even after the pip install command tells me all requirements are satisfied

from platypus.

@kliptonize Pip might still be trying to install dependencies for Python 2 to use, try following this on SO https://stackoverflow.com/questions/11268501/how-to-use-pip-with-python-3-x-alongside-python-2-x

from platypus.

Tracked down the root of the problem: for some reason the init.py file is missing and causing import errors in fresh install of Python, even though my dev env handles it fine. Weird, but pushing fix now.

from platypus.

Pushed out fix, closing issue as I have verified it in clean env. Feel free to reopen if it does persist.

(git pull or download new tagged release)

from platypus.