PEP461 is only available on Python 3.5.  Our CI (Travis) is set to run
on Python 3.4, and there's no reason not to be compatible with those
older Python versions IMO.

Let's then use a syntax that will produce the same content, but will
work on all Python 3.x versions.

Reference: https://docs.python.org/3.5/whatsnew/3.5.htmlSigned-off-by: NCleber Rosa <crosa@redhat.com>

The prevailing coding style of Avocado (unittest.TestCase) tests is to
use the specialized assert methods, such as assertNotRegexpMatches.

Unfortunately, the regular expression related assertion methods have
been through a messy renaming.  In theory, assertNotRegexpMatches and
assertRegexpMatches should be available in Python 3.0 and 3.1, but not
in Python >= 3.2, where it got renamed to assertRegex and
assertNotRegex.

In practice, in my system with Python 3.6.3, I see:

>>> unittest.TestCase.assertNotRegexpMatches
<function TestCase._deprecate.<locals>.deprecated_func at 0x7f3b85b709d8>

But in Travis, with Python 3.4, it's not available:

ERROR: test_directives_regex (selftests.unit.test_safeloader.DocstringDirectives)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/avocado-framework/avocado/selftests/unit/test_safeloader.py", line 135, in test_directives_regex
    self.assertNotRegexpMatches(directive, safeloader.DOCSTRING_DIRECTIVE_RE)
AttributeError: 'DocstringDirectives' object has no attribute 'assertNotRegexpMatches'

Let's simplify things and just use a regex match and check for its
result.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

* https://github.com/avocado-framework/avocado:
  utils.cpu: Update cpu info pattern for aarch64

arm64 or aarch64 pattern is not easy to identify in the
cpuinfo. For v7 there is model name in the cpuinfo and it
could be regonize as arm for 32 bit. But in v8 only could
found 'CPU architecture' in the cpuinfo and current code
will fail to match and return i386 which is wrong.

For fix this, if 'CPU architecture' found in cpuinfo, use
platform.machine to return the arch name.
Signed-off-by: NWayne Sun <gsun@redhat.com>

Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

* https://github.com/avocado-framework/avocado:
  Packaging: add bash RPM sub package
  Packaging: remove man page sources from binary RPM packages
  Packaging: remove examples from Python side of installation
  Packaging: remove unused function _get_resource_files()
  Settings: remove variables from the main module namespace
  Packaging: exclude optional_plugins tests in addition to selftests
  Packaging: add missing configuration files for RPM packages
  Packaging: make config files data files of the avocado module

To remove some of the bloat (even if little) of the base
python-avocado package, let's move content that is not useful to
Python developers out of the way.

This should also make the experience of content more similar across
users of the Python module (say, from a `pip install`) and users of
the python-avocado package.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

There's little to no point in providing these files, since the
generated man pages are already packaged.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Leaving them only in the source distribution generation (if one runs
python setup.py sdist) and in the "example" RPM package.

Because the copying of those files won't be performed by the Python
module installation code, it must be done in the SPEC file.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>

The main module namespace has a lot of variables which are only
used in the main class initialization method.  Let's avoid poluting
the module namespace and move those to where they're used.  If
we want to put variables at the global module namespace, we
should consider if they're useful to other modules, make them
all caps, and document them.

A nicer refactor could be done here, but IMO, this is still an
improvement.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The selftests from the main source directory (and package) are already
excluded from being considered modules to be distributed.  Let's also
exclude the tests that have recently been moved to their own modules.

Without this change, the "tests" module will be installed in Python's
library location, and will contain the files from all of those
directories.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

These files weren't being installed by the setup.py code, and thus
ended up missing from RPM packages.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

In a pure Python world[1] the "avocado" module requires the existence
of these configuration files.  Let's make those configuration files
"data files" of that module.

Since the configuration location can now be a different, the settings
module needs adjustments to also attempt to load them from package
resources (which is tied to the data files).

Finally, when using RPM packages, we need to put the configuration
back into the system location (/etc).

[1] - that is, ignoring operating system or distribution specific
      conventions and packaging technologies
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

* https://github.com/avocado-framework/avocado:
  avocado/core/job.py: don't attempt to run git if .git doesn't exist
  Revert "avocado/core/job.py: don't attempt to run git if .git doesn't exist"

When looking for the GIT commit info to log in the Avocado job log,
we can optmize things a little by not running git if the ".git" directory
doesn't exist at the top level.

py2to3 is not being used anymore, so we don't need to check if we're
running from modules from the build directory.

Also, as another optmization, let's not look for the git binary until
we're sure we'll be running it.

Update: Use abspath to get "base_dir" location to avoid using "" when
avocado is executed from main git directory.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

The 6323773d commit breaks avocado
execution from head of the git source as the base_dir is "" and then
"os.chdir" fails.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Signed-off-by: NAmador Pahim <apahim@redhat.com>

Signed-off-by: NAmador Pahim <apahim@redhat.com>

Signed-off-by: NAmador Pahim <apahim@redhat.com>

When looking for the GIT commit info to log in the Avocado job log,
we can optmize things a little by not running git if the ".git" directory
doesn't exist at the top level.

py2to3 is not being used anymore, so we don't need to check if we're
running from modules from the build directory.

Also, as another optmization, let's not look for the git binary until
we're sure we'll be running it.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Let's break down the types and description of the CmdResult init
method.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

We're (hopefully) about to change the specifics about the Python
versions we support.  But, until then, let's be clear about the
Python version (2.7) that we support.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>

pyliblzma is not required in python >= 3.3, and backports.lzma
works for all versions prior to that one. Let's update
the requirements.txt file to only install that backport
when necessary.
Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>

Python wheel packages are really convenient.  Let's create and
distrubute them in addition to the source packages.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

* https://github.com/avocado-framework/avocado:
  avocado/core/loader.py: implement ordered test discovery

Because only package based installs (such as RPM) will probably build
and install them.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

And move that information to the documentation directory, where people
will probably look for instructions if they feel like building the
docs.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Which is also supposed to be the most universal installation
method: pip based installs in the user's own directories.

Then, give information on virtual environment based installations.

The README file was missing the section on pip based installs, so
let's add it there.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

* https://github.com/avocado-framework/avocado:
  spell: comply with new checks

Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

* https://github.com/avocado-framework/avocado:
  vmimage: add JeOS Image Provider

Signed-off-by: NAmador Pahim <apahim@redhat.com>

make spell is now covering more cases. This patch fixes the actual spell
errors and adds the required exceptions.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

The docstring given on `_greedy_path()` has examples that don't match
the implementation.  To prevent the implementation from deviating
(again?) let's turn those into tests.

Also, to make the purpose of that function more clear, this
changes its name to `_greedy_path_to_re()`.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The order in which test classes and methods are found is relevant
to the loader result.  Currently, this ordering is not dependable
as the loader findings are stored on a regular dictionary.

This change makes the ordering dependable, and so happens to also
make the test pass on a Python 3 environment.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

WIth the new repository, now it is possible to add our own JeOS Image
Provider to the vmimage module.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

Signed-off-by: NAmador Pahim <apahim@redhat.com>

Signed-off-by: NAmador Pahim <apahim@redhat.com>

"file" is not available on python3, let's use "open" to get file
instance.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

The subprocess.DEVNULL is not available on Python2.

This reverts commit e51acbfa.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>