Permission was validated prior to adding these markings.

Patch contributed by Robert Zimmerman.

original values after patching.

Patch contributed by Sean McCully.

Fixed the case of the "Ctrl-" prefixes.

boolean result instead of raising an exception.

Patch by A Kaptur.

Patch from Berker Peksag.

Patch from Ilia Kurenkov.

Initial patch by Aaron Hill.

Patch from https://github.com/testing-cabal/mock/issues/215

could in Python 3.3.

Patch from Nicola Palumbo and Laurent De Buyst.

This was a regression vs Python 3.4. Patch from Ignacio Rossi

This was a regression vs Python 3.4. Patch from Ignacio Rossi

assertWarnsRegex() assertments now check the type of the first argument
to prevent possible user error.  Based on patch by Daniel Wagner-Hall.

Patch by Martin Panter.

assertWarnsRegex() checks now emits a deprecation warning when callable is
None or keyword arguments except msg is passed in the context manager mode.

assertWarnsRegex() checks are not longer successful if the callable is None.

Added tests for assertRaises().

Behavior equivalent to m.configure_mock().  Patch by Kasia Jachim.

Behavior equivalent to m.configure_mock().  Patch by Kasia Jachim.

The concept of .pyo files no longer exists. Now .pyc files have an
optional `opt-` tag which specifies if any extra optimizations beyond
the peepholer were applied.

Issue #22903: The fake test case created by unittest.loader when it fails importing a test module is now picklable.

Patch by Håkan Lövdahl.

Patch by Håkan Lövdahl.

implementation in issue #21408 they are redundant.

returned NotImplemented.  Removed incorrect implementations of __ne__().

Issue #22894: TestCase.subTest() would cause the test suite to be stopped when in failfast mode, even in the absence of failures.

Fixed an output of sets in examples.

When used in the real world it can under some situations trigger
"    assert not _relpath.startswith('..'), "Path must be within the project"
     AssertionError: Path must be within the project
"

Because _get_name_from_path was not expecting to be called with the top level
directory.

We were not honouring load_tests in a package/__init__.py when that was the
start_dir parameter, though we do when it is a child package. The fix required
a little care since it introduces the possibility of infinite recursion.

Previously the ImportError was only shown if the top level containing
package failed to import, with other ImportErrors showing up as
AttributeError - hiding the real cause. As part of this,
`TestLoader.loadTestsFromNames` now captures errors to self.errors.

These tests were undebuggable as written, and there's no testing fallacy
involved in using the method we're testing to test the output of that method,
so switch to that.

This makes it possible to examine the errors from unittest discovery
without executing the test suite - important when the test suite may
be very large, or when enumerating the test ids from a test suite.

Patch by Févry Thibault.