1 new commit in tox:
https://bitbucket.org/hpk42/tox/commits/50f3b98fc65b/
Changeset: 50f3b98fc65b
User: aconrad
Date: 2014-12-20 00:54:58+00:00
Summary: explain how to disable PYTHONHASHSEED
Affected #: 2 files
diff -r 7109f1184d9f0303b050fce006cd90fa3db9e26e -r
50f3b98fc65b951ab07e6b5e3fbd5a2fc9c48f2c CHANGELOG
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -95,7 +95,7 @@
- merged PR125: tox now sets "PYTHONHASHSEED" to a random value
and offers a "--hashseed" option to repeat a test run with a specific seed.
- You can also use --hashsheed=notset to instruct tox to leave the value
+ You can also use --hashsheed=noset to instruct tox to leave the value
alone. Thanks Chris Jerdonek for all the work behind this.
- fix issue132: removing zip_safe setting (so it defaults to false)
diff -r 7109f1184d9f0303b050fce006cd90fa3db9e26e -r
50f3b98fc65b951ab07e6b5e3fbd5a2fc9c48f2c doc/example/basic.txt
--- a/doc/example/basic.txt
+++ b/doc/example/basic.txt
@@ -191,10 +191,14 @@
command-line option to ``tox``. You can also override the hash seed value
per test environment in ``tox.ini`` as follows::
- [testenv:hash]
+ [testenv]
setenv =
PYTHONHASHSEED = 100
+If you wish to disable this feature, you can pass the command line option
+``--hashseed=noset`` when ``tox`` is invoked. You can also disable it from the
+``tox.ini`` by setting ``PYTHONHASHSEED = 0`` as described above.
+
.. _`in Python 3.3`:
http://docs.python.org/3/whatsnew/3.3.html#builtin-functions-and-types
.. _PYTHONHASHSEED:
http://docs.python.org/using/cmdline.html#envvar-PYTHONHASHSEED
Repository URL: https://bitbucket.org/hpk42/tox/
--
This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.
_______________________________________________
pytest-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pytest-commit