* Switch to Python 3.
  * Removed gustavo panizzo <gfa@zumbi.com.ar> from uploaders.

Release v1.4.2

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

argparse was external in python 2.6 but not anymore, remove it from
requirements.

This should help with pip 8.0 that gets confused in this situation.
Installation of the external argparse is not needed.

Change-Id: Ib7e74912b36c1b5ccb514e31fac35efeff57378d

Change-Id: If918eaeb47b0d35bda198119cbc0fc3f015d6a1e

Python 2.6/3.3 support would be dropped by Infra team from mitaka,
CI would no longer be testing it, so projects should drop it too.

Change-Id: I13250170bd04d07b97990ed52a8c7a0c0f7e76c6
Closes-Bug: #1526170

OpenStack projects are no longer being tested under Python 2.6, so
remove the trove classifier implying that this project supports 2.6.

Change-Id: I1f8cc2d5d25a2e00b7ad4d12b013b69695536ab8

To solve the problem of "db type could
not be determined" on py34 we have to run first the py34 env to, then, run
py27. This patch puts py34 first on the tox.ini list of envs to avoid this
problem to happen.

Change-Id: Id0d2de40081a59d5819d2e6c52c98135f26808b5
Closes-bug: #1489059

Replace assertEqual(None, *) with assertIsNone in tests to have
more clear messages in case of failure.

Change-Id: Ic2dca04e7cdd4f837c42b39dd1ce37604c8f101b
Closes-bug: #1280522

Caching is enabled by default from pip version 6.0

More info:
https://testrun.org/tox/latest/config.html#confval-downloadcache=path
https://pip.pypa.io/en/stable/reference/pip_install/#caching

Change-Id: I0a6561c0d667b1310cd544f1b1ec4c019ba16197

Commands from AWS::CloudFormation::Init, when supplied as list, should
be run with shell=False. Only when commands are given as string, they
are meant to be run on shell.

In principle, we are trying to give least access to the shell to avoid
any inadvertent shell injections.

Change-Id: I3dc6fe0c29a14f75be044846f737e1ade23a6d6b
Closes-Bug: 1498300

Make all internal commands as list to avoid any possibility of command
line injection. Commands supplied as string are susceptible to
substitution.

All the internal commands are supplied as list to CommandRunner. As a
convention, all the commands must be given as list to subprocess except
the commands read from file, like in case of cfn hooks and commands
section in metadata.

Few internal commands require shell redirects and they will be
implemented in another patch.

Change-Id: Ifabaf44e341144bc85508dc05c76b1d83e41ae44
Partial-Bug: #1312246

Control the privileges by setting the effective UID before running the
command. Earlier we used to run command using su -c "USER".

Original EUID is restored after running the command. This is required to
run multiple commands in succession with different run-as users.

Change-Id: I414fc6a802f11deb320b43c6d011f802a42c40c9
Partial-Bug: #1312246

This reverts commit e424af22.

Splitting command strings that were previously assumed to be interpreted
by the shell at whitespace and then passing them as separate args to
execvp will not work.

Change-Id: I7c37b5852ce9b20e63bdbbaddfb852463548aa90