jakirkham / npctypes

100%

master: 100%

LAST BUILD ON BRANCH fix_doctest_win

branch: fix_doctest_win

CHANGE BRANCH

x

Reset

• fix_doctest_win
• config_pypi_deploy
• fix_doctest_win_2
• master
• q_sec_str
• recut_cookie
• req_numpy
• shared_arrays
• update_doc_copyright
• use_cookie_tmplt
• use_np_113_print_style_doctests
• v0.0.1
• v0.0.2
• v0.0.3
• v0.0.4
• v0.0.5
• versioneer_0.17

Build # 83

Build Type

push

travis-ci

Committed by jakirkham

Commit Message

Use NumPy 32-bit int in `tinfo` doctest.

Appears that on Windows `int` means 32-bit int even when a 64-bit build
of Python was made. So instead of relying on `int` generally, which will
vary between 64-bit or 32-bit for Unix or Windows respectively, specify
the number of bits with a NumPy type. Also as there is a chance of
representation subtleties between Unix and Windows with a 64-bit int
(e.g. `L` postfix) chose a type that is least likely to run into these
issues in the doctest. In particular, switch to a 32-bit int from NumPy.
This both specifies a specific type of integer and picks one where its
max and min values will fall within what a 32-bit int can represent.

Run Details

58 of 58 relevant lines covered (100.0%)

4.0 hits per line