| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
This has enough users around OpenStack to justify adding it to
'fixtures' proper. It's intentionally dumb, since the main purpose of
this is to avoid people calling `resetwarnings` in their variant of the
fixture, as that clears *all* filters including those we don't control.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
|
| |
|
|
|
|
| |
It's EOL
Signed-off-by: Stephen Finucane <stephen@that.guru>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Fixes #53.
|
| | |
|
| |
|
|
|
|
|
| |
These are all EOL. We don't need to support them any longer. There's
additional cleanup here but that will be done separately.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
- docs.
- cleanup patches of boundmethods to not leave cruft behind.
- NEWS entry.
Sem-Ver: api-break
|
| | |
|
| |
|
|
| |
Sem-Ver: api-break
|
| |
|
|
| |
CompoundFixture combines multiple fixtures into one.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When using the FakeLogger, have mis-formatted logging messages raise an
exception.
Normally when using the logging module, mis-formatted logging messages
will not raise an exception. Instead the exception will be printed but
not raised.
Change this behavior so that mis-formatted log messages can be caught
during unit-testing.
Closes-Bug: #1503049
Change-Id: I8d3e94d131289300ae020eb1d63306489e986335
|
| |
|
|
|
|
| |
If folk have installed both, they probably want the bugfixes from the
rolling backport vs the potentially stale Python 3.3 or 3.4 etc
version.
|
| | |
|
| | |
|
| |
|
|
|
| |
The change to handle resource leaks incorrectly ignored BaseException
- e.g. KeyboardInterrupt.
|
| | |
|
| |
|
|
|
|
|
|
| |
Fixture.setUp should no longer be overridden in subclasses. Instead
override _setUp. This permits the Fixture base class to detect failures
during _setUp and trigger any registered cleanups, attach any details
to the failure exception and propogate that to callers.
(Robert Collins, #1456361, #1456353)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Capturing the warnings module output (which is typically used
for deprecating code or functions or modules) is quite useful and
is a frequent operation that can be required to perform. So provide
a fixture that is similar (but not the same) as the warnings
``catch_warnings`` context manager that can be used to gather all
warnings emitted and allows people to later analyze them to ensure
they are as they expect.
|
| | |
|
| | |
|
| |
|
|
|
| |
PEP 475 led to ``time.sleep()`` not being interrupted when a received signal
handler eats the signal (rather than raising an exception). (Robert Collins)
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The logging fixture is extremely useful to be used a temp buffer for
collecting log messages into a buffer, and only decide if we're going
to emit them after some event in the future (like the failure or
success of some future criteria). However, in it's current form we are
not given access to the datefmt variable of the underlying Formatter,
which means we always end up with the default python time string for
%(asctime), which looks incorrectly localized many places.
This merely adds the ability to pass the datefmt param through to the
Formatter.
Signed-off-by: Sean Dague <sean@dague.net>
|
| |
|
|
| |
No functional changes.
|
| |
|
|
|
|
|
|
|
|
| |
~~~~~~
CHANGES
-------
* Fixed 0.3.15 on Python 2.6 - version info is a plain tuple there.
(Robert Collins)
|
| | |
|
| |\
| |
| |
| | |
(Steve Kowalik)
|
| | |
| |
| |
| | |
(Steve Kowalik)
|
| |\ \
| |/ |
|
| | | |
|
| |\ \
| |/
| |
| | |
(Steve Kowalik)
|
| | |
| |
| |
| | |
(Steve Kowalik, #1358085)
|
| |/
|
|
| |
(Dan Kenigsberg)
|
| | |
|
| |
|
|
| |
(Robert Collins)
|
| | |
|
| |
|
|
| |
(Robert Collins, #1102688)
|