Stuff like this often happens because Python has a compiled/cached version. Under Python2, `.pyc` files were in the same directory as the `.py` file ; under Python3 they are in a `__pycache__` directory and versioned to the interpreter.
you probably had a `views/__pycache__/__init__.cpython-35.pyc` file, which python 3.5 picked up but 3.7 and 3.8 will not. On Wednesday, March 25, 2020 at 2:06:26 PM UTC-4, Sydo Luciani wrote: > > Yes, I was missing __init__.py in views folder, but didn't have any > problem while working in Python 3.5 environment, > error started when switched to Python 3.7 and Python 3.8, and creating > __init__ fixed the issue. > > The different behavior brought up curiosity. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/25856fcc-e569-4fe7-a138-6f3bb9917849%40googlegroups.com.
