Are you able to load those packages from other scripts? You can see if those packages are accessible when you open the interactive Python in the terminal and try to import those packages.

Do the following steps if you are unclear:

1. Open your Terminal
2. Type "python" to open the interactive Python interface
3. Type "import kitchen".

If the above fails, it is likely that it is an issue with your system.

Why do we use kitchen? Is it a recently added dependence?

2015-09-22 8:53 GMT+02:00 Hydriz Scholz [email protected]:

Are you able to load those packages from other scripts? You can see if
those packages are accessible when you open the interactive Python in the
terminal and try to import those packages.

Do the following steps if you are unclear:

1. Open your Terminal
2. Type "python" to open the interactive Python interface
3. Type "import kitchen".

If the above fails, it is likely that it is an issue with your system.

—
Reply to this email directly or view it on GitHub
#252 (comment).

Emilio J. Rodríguez-Posada, 22/09/2015 11:31:

Why do we use kitchen? Is it a recently added dependence?

It was added some time ago to reduce Unicode errors.

@stefek99 you seem to do same mistakes as me when I was at point 0 of learning curve.

• python works much better with virtualenv so make it installed

sudo apt-get install virtualenv

• then make some place where you put your dumpgenerator

cd
mkdir whateverwikiyouwanttoarchivename
cd whateverwikiyouwanttoarchivename

• then make inside that directory virtualenvironment, named e.g. venv (think of it is directory with bunch of python things just to make your project safely work)

virtualenv venv --no-site-packages

• note that --no-site-packages above -- it will make your life much easier as it will create full replica of python (not big, don't worry) and you won't have conflicts between system-wide python packages (e.g. via sudo apt-get instal ... or sudo pip install ...). Just forget for sudo pip ... altogether now.
• now switch to your environment

source venv/bin/activate

or
(that's dot instead of keyword source)

. venv/bin/activate

• you will see your command prompt switch to something like

(venv)username@host:~/path$

you did NOT launch any new shell, just rehashed some settings, so do NOT press on Ctrl+D to leave it, rather use keyword deactivate when you've done everything

• now you are very close - just pip install everything you need as dependency

pip install kitchen
pip install request

(note no sudo fired in progress)

• now you can fire your dumpgenerator

python dumpgenerator.py --api=___SOME___URL___HERE --xml

• it should work now, at least you should not get python error stacks
• path permission errors were because you didn't make that virtual environment (directory which we named venv just to have some handle), so pip has been trying to put it where system-wide python located, and it bumped into acls not allowing you to do so. When you added sudo, it basically forced installation into system-wide place. But it can create bunch of other problems, from future updates to conflict resolutions in version updates to package cache problems and few else. And when you fired dumpgenerator, the python interpreter didn't have proper environment, so it didn't see packages

Thank you.

Next time I do the backup I'll follow instructions from here.

Added a link to this task, thanks for your help @silpol!