When I first started p1tr the installer worked flawlessly. But next time I started P1tr the install started again. Obviously it cant determine correctly if it has already run or not. The second attempt to install p1tr fails with this traceback:
FATAL: Cannot create P1tr directory in your home:
Traceback (most recent call last):
File "bot.py", line 58, in <module>
main()
File "bot.py", line 37, in main
load_language()
File "/Users/mc/dev/p1tr/lib/helpers.py", line 75, in load_language
conf_lang = imp.load_source('config', './lib/config.py').language
File "./lib/config.py", line 45, in <module>
config_file = install.main()
File "/Users/mc/dev/p1tr/install.py", line 64, in main
shutil.copytree(os.getcwd(), target)
File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/shutil.py", line 110, in copytree
os.makedirs(dst)
File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/os.py", line 172, in makedirs
mkdir(name, mode)
OSError: [Errno 17] File exists: '/Users/mc/.p1tr'[18:30:54] INFO: None
This is not really a bug, it was rather intended to be a feature. In ~/.p1tr you should have a working P1tr installation. This way of proceeding is most useful for normal users, not developers.
However, this is a bit uncomfortable, so you can, as a workaround, copy ~/.p1tr/bot,conf to your P1tr directory for development.
I will commit a change which enables you to use ~/.p1tr/bot.conf when starting P1tr from your development directory.