ipynose
print nosetests result in the iPython (notebook)
iPython notebook example here.
Usage
from ipynose import ipynose
1. no path
nosetests without specific path. (-v option default)
ipynose.show_nose_result()
1) If empty, Error should occur ... SKIP: showing class skipping
First node should be equal to last node ... SKIP: showing class skipping
1) Last node should contaions inserted self.item ... SKIP: showing class skipping
Initial Queue ... SKIP: showing class skipping
1) 'peek' returns first node item. ... SKIP: showing class skipping
test_dequeue ... ok
test_enqueue_when_empty ... ok
test_enqueue_when_not_empty ... ok
test_make_queue ... ok
test_peek ... ok
----------------------------------------------------------------------
Ran 10 tests in 0.014s
OK (SKIP=5)
2. Specific path
nosetests for specific file. (-v option default)
EXAMPLE_TEST_PATH = "py/queue/tests/test_queue.py"
ipynose.show_nose_result(EXAMPLE_TEST_PATH)
test_dequeue ... ok
test_enqueue_when_empty ... ok
test_enqueue_when_not_empty ... ok
test_make_queue ... ok
test_peek ... ok
----------------------------------------------------------------------
Ran 5 tests in 0.001s
OK
Metadata
Release files for ipynose 0.0.2
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 | Actions |
|---|---|---|---|---|
| ipynose-0.0.2.tar.gz | 2.1 kB | Without provenance | Details for ipynose-0.0.2.tar.gz |
Release files / ipynose-0.0.2.tar.gz
| Download URL | ipynose-0.0.2.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4bdfa6343f4cab93333cfa8d61acb33c2f53397e83b0ed17c5c384b1a513a09
|
|
BLAKE2b-256 checksum How to use checksums |
a93818ebe4d7a7f15a1ab907116fbecfa2930ae72554ff25b920d2a36b1cc28f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ipynose 0.0.2
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.