[doc] virtualenv is not mandatory

[julienmalik]

on my ubuntu laptop, prosopopee runs fine with standard packages.

• apt-install gm, python-jinja2 and python-yaml
• git clone https:/Psycojoker/prosopopee

then from a site root :

• python $CLONE_DIR/prosopopee/prosopopee.py

I find it much easier to work with than to manage ve activation/deactivation...

[Psycojoker]

In the python community, virtualenv is the defacto standard way of distributing and using python on every platform. Since we are more in a "applicative" approach than a python lib or framework, it might make sens to offer other ways of using it.

If you send a PR with an update of the README I'll merge it.

Another way to do that is to do a:

pip install --user prosopopee

And this in your bashrc

export PATH="$HOME/.local/bin:"$PATH

The only reserve I have regarding recommanding distro packages are that if we start to had more dependancies, they might no be packaged.

(Since we have a very standard usage of those packages that's not a big surprise (but a good one).)

[julienmalik]

Understood, and that was my opinion too. Currently the number of dependencies is so small that it seems useful to me to at least mention it. I'll do the appropriate PR

[julienmalik]

Hum since your latest code split, this does not work anymore...

/usr/bin/python ../prosopopee/prosopopee/prosopopee.py
Traceback (most recent call last):
  File "../prosopopee/prosopopee/prosopopee.py", line 10, in <module>
    from .cache import CACHE
ValueError: Attempted relative import in non-package
make: *** [site] Error 1

So sad I will have to use pip :)

[Psycojoker]

Damn, I'm not sure on how to fix this in a clean way :x

[julienmalik]

Not sure it is clean-pip-compliant, but in the root of the repo, adding a prosopopee.py file with :

#!/usr/bin/env python

from prosopopee import prosopopee

if __name__ == '__main__':
    prosopopee.main()

and I'm good to go