Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.
Change-Id: I2d8467b98a3489ce7f59dcef0fd2b3c0956b0f53
Remove intersphinx from the docs build as it triggers network calls that
occasionally fail, and we don't really use intersphinx (links other
sphinx documents out on the internet)
This also removes the requirement for internet access during docs build.
This can cause docs jobs to fail if the project errors out on
warnings.
Change-Id: I71e941e2a639641a662a163c682eb86d51de42fb
Related-Bug: #1368910
We don't need vim modelines in each source file, it can be set in
user's vimrc.
Closes-Bug: #1229324
Change-Id: I1629d4e1752efc35e25b0d30f8d1d5171363de2b
* tox.ini: The LANG, LANGUAGE and LC_ALL environment overrides were
introduced originally during the testr migration in an attempt to be
conservative about the possibility that locale settings in the
calling environment could cause consistency problems for test runs.
In actuality, this should be unnecessary and any place where it does
cause issues ought to be considered an actual bug. Also, having
these in the configuration actively causes older pip to have
problems with non-ASCII content in some package metadata files under
Python 3, so drop it now.
Change-Id: Ia910ded1789a1a8fac7d82f1ce97300ad7bfefda
Closes-Bug: #1277495
Universal is used to identify pure-Python module(by bdist_wheel). For
these, it is sufficient to build a wheel with _any_ Python ABI version
and publish that to PyPI (by whatever means).
Change-Id: Ia277504b291412553981e52bcca1ea9f6bd09b3f
when loading from cfg file, cfg.get takes just 2 parameters not
three.
Added some basic tests and test for the specific change as well
Change-Id: I633d665f63271b6ada9196a0f08028d404b33110
No need to expose the weirdness of attributes which need to be
initialized by calling foo_string() methods.
Change-Id: I3248a62be1f8d9a81bb2e31258091c3ed692ab1a
Definitely no need to retain "compatibility methods". Let's just fix
the code which uses the old names.
cached_version_string() doesn't seem to do anything useful anymore
either.
Change-Id: I00b0033ef3ada170941caf13fea74918cce59048
Firstly, add a missing oslo/version/__init__.py.
Secondly, move tests from oslo/version/tests/ to tests/
Having the tests under oslo.version and using oslo.sphinx in the same
virtual env doesn't seem to work. The issue appears to be that because
the tests don't get installed under the namespace package in the venv's
site-packages, testr can't find them.
Personally, I'm a fan of keeping tests in a different directory from the
runtime code and this is what works for oslo.config and oslo.messaging.
Thirdly, avoid using 'setup.py develop' with tox.
There seems to be an issue with the 'setup.py develop' approach caused
by the fact that oslo is a namespace package and we install oslo.sphinx
into this namespace in the virtualenv. This results in the oslo.version
package not being found when it's not properly installed into the
virtualenv.
These really should be three separate commits, but any one of them alone
causes testr to stop pretending everything is fine so they all need to
be merged together.
Closes-Bug: #1242614
Change-Id: I5140fa62dc8bdd10a58bd2847b27514a926e3c19
Nova has a great feature that allows distro packagers to override
version strings by putting config files in known locations. We should
support this in our version processing code, because it's quite handy.
Change-Id: Ibb80649b45ecab90f982138cb07d2e5a8b7ac6d9
Upstream d2to1 has been rather unresponsive, and doing what we need
in this case is really easier without the extra complexity.
Change-Id: Ibd16944e76ad8398b57b6ddcbcd150cd462add3e
Things in the world are moving towards setuptools 0.7, and
there is not a path between distribute and setuptools. Our explicit
dependency on setuptools is causing us to have to write patches to
try to jump through additional hoops to get it to install in the
right contexts.
Fixes bug 1189941
Change-Id: Id7a749c02203100dab52160a551d3548c8a48fd6
If we're running the installation of dependencies for installation
ourselves anyway - just use pip and be done with it. This means
that our requirements will get installed consistently regardless of
whether we're using pip, python setup.py install or a tox environment.
Change-Id: If92557a33a76553ad36bd136fa87780857a894b1