Closed nwtti closed 7 years ago
Could you post the output when running python setup.py install
from the source directory?
I hope it is normal that I have to run it as root, otherwise I'll get an permission error with .../protobuf-3.1.0.post1-py3.6.egg/EGG-INFO/namespace_packages.txt.
Yes, that is probably because it has to compile some protobuf sthings.
Anyways, just seeing you use Python 3.6 and i have never tested with Python 3 yet.
Do you mind running python setup.py test
from the source directory? Maybe the issue is originated there.
Thats interesting, setup.py test
gives some errors using python3 (most of them because of the missing brackets when using print, but still errors), but works just fine using python2.
But /plugins python_version
in profanity tells me, that profanity will use Python 3.6. Is there a way to use python2 instead in profanity?
EDIT: Ok, Its about compatibility with python3. Recompiling Profanity with python2 did the trick, but now I'm having the same issue as in #11. Nevermind, I think this thread is solved for now. Maybe you could add to your ReadMe, thats its only compatible to python2.
Oh great .. thanks for the pointer. Will definetly add a remark in the Readme (or fix support for Python 3). Will leave this ticket open until this is done.
Using Issue #13 for further Python 3 Support tracking.
I can't load the plugin, but profanity doesn't give any information about why it fails (or I'm just to stupid to find it, lol). I'm using Arch Linux and the latest version of profanity and the omemo plugin from Github (Profanity installed via profantiy-git from AUR) . A profanity.log with '--log=DEBUG' is attached, but doesn't give any information on why it fails. You can also see, that I am able to install other plugins (ascii.py in this log file) without problems.
profanity.log.txt (here's a paste if you don't wanna download that file)