Plus, I tested it on Arch Linux where the source is copied by pacman to /usr/share/owtf

Hardcoding ~/.owtf should ideally be done in framework/config/framework_config.cfg

@tunnelshade , please check the fix

@alexandrasandulescu Could you please fix the coding style in your pull requests? We are trying to follow the pep8 (exception being 120 limited chars per line (CR included)).
For instance:

• This can be onlined
• This can be onlined
• This is not C, no need for parenthesis, please remove them
• This can be onlined
• Superfluous parenthesis
• Superfuous parenthesis
• Comments start with '# ' (notice the space after the hash) and upper case on the first letter, and finish with a period '.'
• Superfluous parenthesis
• This can be onlined
• Documentation on the function?

PEP8:

• Maximum line length (s/79/119 for OWTF)
• Comments
• Recommendations

PEP257:

• Docstrings

Sphinx:

• Sphinx docstring examples

@DePierre thanks. I'll keep that in mind . fixed

@tao: Sphinx syntax has not been written for the majority part of OWTF - isn't just the docstrings sufficient for this case?
Rephrase opinion below!

@delta24 Your comment makes me so sad...

I am trying my best since almost 2 years to push pep8 code with sphinx-like docstrings step by step for any new code I am adding to the codebase. If anyone would do the same day after day, the codebase would be easier to read. Instead, it is just unbearable, nobody understands anything, no doc, no coding rules, nothing.

Please reconsider writing PEP8 code with Sphinx docstrings for, at least, any new added code.

Let me rephrase this: Don't get me wrong. Sphinx-like docstring comments are invaluable for any code. But as a practice, I think either the whole module/ or the whole .py file should have them, not only the newly added code. If @alexandrasandulescu is ready to add the docstring comments for the whole module, well and good!
Cheers!

No one will ever write documentation for OWTF at once but going step by step makes everything possible.
Sure it would be nice to have sphinx docs for all functions but are you ready to do that? I don't think so.
This is childish to use the "yes but no one else does so why should I do that?"
Also, this is a requirement for OSCS
https://www.owasp.org/index.php/Summer_Code_Sprint2015#OWASP_OWTF_-_HTTP_Request_Translator_Improvements
Check the Expected Results

Okay guys, @delta24 It is good to have docstrings for the whole module but as @DePierre says it cannot be done overnight. Once we start writing it for the new code that we write we will get accustomed to it and subsequently will be useful.

@alexandrasandulescu Use a PEP8 checker with your IDE/Editor to follow PEP-8

@tunnelshade , fixed