openstack/ironic
Code Issues Proposed changes

Merge "Remove references to py34 from developer guide"

Browse Source
This commit is contained in:
Jenkins 2017-03-06 23:39:20 +00:00 committed by Gerrit Code Review
commit 96d7d6ad61
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/source/dev/dev-quickstart.rst
View File

@ -8,9 +8,9 @@ This is a quick walkthrough to get you started developing code for Ironic.
This assumes you are already familiar with submitting code reviews to This assumes you are already familiar with submitting code reviews to
an OpenStack project. an OpenStack project.
The gate currently runs the unit tests under Python 2.7, Python 3.4 The gate currently runs the unit tests under Python 2.7 and Python 3.5. It
and Python 3.5. It is strongly encouraged to run the unit tests locally prior is strongly encouraged to run the unit tests locally prior to submitting a
to submitting a patch. patch.
.. note:: .. note::
Do not run unit tests on the same environment as devstack due to Do not run unit tests on the same environment as devstack due to
@ -77,11 +77,11 @@ it, follow the instructions for installing prerequisites above and
sudo tar xzf Python-3.5.2.tgz sudo tar xzf Python-3.5.2.tgz
cd Python-3.5.2 cd Python-3.5.2
sudo ./configure sudo ./configure
# Install Python 3.5 without replacing the system-wide Python version:
sudo make altinstall sudo make altinstall
# This will install Python 3.5 without replacing 3.4. To check if 3.5 was installed properly # Check if Python 3.5 was installed properly:
run this command:
python3.5 -V python3.5 -V
- On Fedora 23:: - On Fedora 23::
@ -120,7 +120,7 @@ Running Unit and Style Tests
All unit tests should be run using tox. To run Ironic's entire test suite:: All unit tests should be run using tox. To run Ironic's entire test suite::
# to run the py27, py34, py35 unit tests, and the style tests # to run the py27, py35 unit tests, and the style tests
tox tox
To run a specific test or tests, use the "-e" option followed by the tox target To run a specific test or tests, use the "-e" option followed by the tox target
@ -130,13 +130,13 @@ name. For example::
tox -epy27 -epep8 tox -epy27 -epep8
.. note:: .. note::
If tests are run under py27 and then run under py34 or py35 the following error may occur:: If tests are run under py27 and then run under py35 the following error may occur::
db type could not be determined db type could not be determined
ERROR: InvocationError: '/home/ubuntu/ironic/.tox/py35/bin/ostestr' ERROR: InvocationError: '/home/ubuntu/ironic/.tox/py35/bin/ostestr'
To overcome this error remove the file `.testrepository/times.dbm` To overcome this error remove the file `.testrepository/times.dbm`
and then run the py34 or py35 test. and then run the py35 test.
You may pass options to the test programs using positional arguments. You may pass options to the test programs using positional arguments.
To run a specific unit test, this passes the -r option and desired test To run a specific unit test, this passes the -r option and desired test