8000 Testing python 2.6, 2.7, and 3.2 by msabramo · Pull Request #948 · matplotlib/matplotlib · GitHub
[go: up one dir, main page]

Skip to content

Testing python 2.6, 2.7, and 3.2 #948

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 27, 2012
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Tweaks to devel/coding_guide.rst suggested by @mdboom
  • Loading branch information
msabramo committed Jun 21, 2012
commit f964e67b6cdae964a8f01105484be5335e10e605
10 changes: 8 additions & 2 deletions doc/devel/coding_guide.rst
Original file line number Diff line number Diff line change
Expand Up @@ -517,8 +517,14 @@ Python environments, including multiple versions of Python (e.g.: 2.6, 2.7,
3.2, etc.) and even different Python implementations altogether (e.g.: CPython,
PyPy, Jython, etc.)

It's a good idea to run ``tox`` in your working directory before submitting a
pull request with your changes. To do so:
Testing all 4 versions of Python (2.6, 2.7, 3.1, and 3.2) requires having four
versions of Python installed on your system and on the PATH. Depending on your
operating system, you may want to use your package manager (such as apt-get,
yum or MacPorts) to do this, or use `pythonbrew
<https://github.com/utahta/pythonbrew>`_.

tox makes it easy to determine if your working copy introduced any regressions
before submitting a pull request. Here's how to use it:

.. code-block:: bash

Expand Down
0