should
安装:
pip install should
使用方法:
from should import it
# 一般的断言
it(1).should.be.int
it({}).should.be.no.ok
it(2).should.be.equal(2)
it(10).should.be.no.equal(8)
it([1,2,3]).should.contain(3)
# with 版异常断言, 不支持 no, 在 0.5 版本会被删除
with should.raises(ValueError):
int('abc')
# lambda 版异常断言
it(lambda: int('abc')).should.throw(ValueError)
it(lambda: int('123')).should.no.throw(ValueError)
更多例子请参考 test.py
License
The MIT License
Change Log
v0.4.7
添加 within 接口
should.py 文件中添加自文档
添加 proper / own_proper 接口
v0.4.6
fix #2. match 不支持多行
添加 search 接口, 与 match 等价, 但更贴近 Python re 的接口
v0.4.5
增加 match 接口, 进行正则匹配断言
增加 empty 属性, 直接判断容器或序列是否为空
只有连接词, be, have 会出现在 Assertion Error 中
throw 接口支持断言 throw 信息
v0.4.4
安装失败修复
v0.4.3
类型断言如 it(1).should.be.int 支持所有内建类型
添加 instanceof 断言, 支持其它类型或弱类型断言
链式调用 ‘be’/’have’ 时, Error 信息正确显示 have 和 be
Metadata
Release files for should 0.4.7
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 |
|---|---|---|---|---|
| should-0.4.7.tar.gz | 4.0 kB | Without provenance | Details for should-0.4.7.tar.gz |
Release files / should-0.4.7.tar.gz
| Download URL | should-0.4.7.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
adc4e24f5e38fe5deeae7e00813f610d4648bc8e59f166f85f8da964825c86b7
|
|
BLAKE2b-256 checksum How to use checksums |
0754102f714577260cb25fdb09eb82b27181a3806c922e9802587a2f305003fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for should 0.4.7
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.