19 lines
1.8 KiB
Plaintext
19 lines
1.8 KiB
Plaintext
|
B
|
|||
|
|
U<>]x <00> @ s<> d Z ddlmZmZmZ ddlZddlZddlmZ da i Z
|
|||
|
|
dd<06> Z e<05> <0C> dd<08> <00>Z
ejd d
|
|||
|
|
d <0B>d d
<0A> <00>Zejd
|
|||
|
|
d<0E>dd<10> <00>ZdS )z=
|
|||
|
|
Pytest configuration and fixtures for the Numpy test suite.
|
|||
|
|
<EFBFBD> )<03>division<6F>absolute_import<72>print_functionN)<01> get_fpu_modec C s | <00> dd<02> | <00> dd<03> d S )N<>markersz=valgrind_error: Tests that are known to error under valgrind.z slow: Tests that are very slow.)Zaddinivalue_line)<01>config<69> r <00>1/tmp/pip-install-i8dhxrtk/numpy/numpy/conftest.py<70>pytest_configure s r
|
|||
|
|
c C s0 t <00> }tdkr|an|tkr,t|ft| < |adS )z<>
|
|||
|
|
Check FPU precision mode was not changed during test collection.
|
|||
|
|
|
|||
|
|
The clumsy way we do it here is mainly necessary because numpy
|
|||
|
|
still uses yield tests, which can execute code at test collection
|
|||
|
|
time.
|
|||
|
|
N)r <00>
_old_fpu_mode<64>_collect_results)<02>item<65>moder r r <00>pytest_itemcollected s r <00>functionT)<02>scope<70>autousec c sZ t <00> }dV t <00> }||kr*td<02>||<02><02><01>t<03>| j<05>}|dk rV|\}}td<03>||<02><02><01>dS )zC
|
|||
|
|
Check FPU precision mode was not changed during the test.
|
|||
|
|
Nz@FPU precision mode changed from {0:#x} to {1:#x} during the testzIFPU precision mode changed from {0:#x} to {1:#x} when collecting the test)r <00>AssertionError<6F>formatr <00>get<65>node)<04>requestZold_modeZnew_modeZcollect_resultr r r <00>check_fpu_mode, s
|
|||
|
|
r )r c C s t | d< d S )N<>np)<01>numpy)Zdoctest_namespacer r r <00>add_npA s r )<11>__doc__<5F>
|
|||
|
|
__future__r r r Zpytestr Z numpy.core._multiarray_testsr r r r
|
|||
|
|
Zhookimplr Zfixturer r r r r r <00><module> s
|