Changelog
1.4.1 (2020-10-26)
assert_is_empty() and assert_is_not_empty() now consume generators if necessary
implement “assert_almost_now()”
stop testing Python 2.6/3.3 (support for these versions will be removed in the next release)
1.4.0 (2019-01-18)
implement “assert_is(expr1, expr2)” and “assert_is_not(expr1, expr2)”
implement “assert_path_exists()”, “assert_path_not_exists()”, “assert_file_exists()”, and “assert_file_not_exists()”
1.3.4 (2017-11-29)
prevent nosetests from running “skip_test” as an actual test case
1.3.3 (2017-09-20)
provide a PEP8 compliant “skip_test” (and export “skipTest” via “__all__”)
1.3.2 (2017-05-08)
assert_length() now consumes generators if this is necessary to get the length
1.3.1 (2016-09-26)
instruct test runners to suppress traceback lines from PythonicTestcase when displaying a test failure.
1.3.0 (2016-01-23)
export ‘SkipTest’ class via unittest (Python 2.7+), unittest2 or nose.plugins.skip
support for “@expect_failure” decorator. It works very similar to unittest’s “@expectedFailure”. However failing tests are reported as “skipped” not “passing” if the test runner does not support “expected failures” (such as nosetests 1.x).
1.2.2 (2016-01-20)
rename project to “PythonicTestcase” to workaround pip’s automatic replacement of underscores with dashes. This simplifies installation from a private index.
1.2.1 (2015-11-23)
fix: assert_raises does not catch some (expected) exceptions on Python 2.6
1.2.0 (16.11.2015)
implement assert_not_raises
1.1.0 (22.10.2015)
assert_raises can return a context manager
1.0.2 (07.10.2015)
fix sdist by including Changelog.txt
1.0.1 (07.10.2015)
use gpg signing for pypi release (no code changes)
1.0 (07.10.2015)
initial pypi release
Metadata
Release files for PythonicTestcase 1.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| PythonicTestcase-1.4.1.tar.gz | 7.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| PythonicTestcase-1.4.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 14.3 kB
Release files / PythonicTestcase-1.4.1.tar.gz
| Download URL | PythonicTestcase-1.4.1.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d79e26ff574a76398c76361eab5a8b545e4e733772a5ef4c5fe7b7d80ac2d6b6
|
|
BLAKE2b-256 checksum How to use checksums |
b46a152cfe4c2b9998ac340930ac237f71c2776d86dcbfb490e4bf2812831471
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.8.6
|
Release files / PythonicTestcase-1.4.1-py2.py3-none-any.whl
| Download URL | PythonicTestcase-1.4.1-py2.py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
9cbf0f1362f9f1469abd3cc9a7550b08487135e1104014a878e4e0fa254b723a
|
|
BLAKE2b-256 checksum How to use checksums |
6c60100c04b25666915272c0044daf35a0728b0cb1c4eb314d89cd4b72c2f3a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.8.6
|
Security for PythonicTestcase 1.4.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.