Files
intellecton/venv/lib/python3.12/site-packages/numpy/__pycache__/conftest.cpython-312.pyc
T

67 lines
9.6 KiB
Plaintext
Raw Normal View History

Ë
vRjÌ!ã
ó4dZddlZddlZddlZddlZddlmZddlmZddl Z ddl
Z
ddl Z ddl m
Z
ddlmZ ddlmZdZ ddlZdZdaiZe j0j3ej4j7ej8«d
««e j:j=d dd¬ «e j:j=d
ddddee j@«¬«ej4j7ej4jCe"«dd«Z#e j:jIej4jKe#«rd nd
«dejLd<dZ'dZ(dZ)erejT«Z)dZ+dZ,e
jZd¬«d«Z.e
j^dd¬«d«Z0e
j^d¬«d«Z1er³ed*d«Z2e2e_3ejhjkd«ejhjkd «de_6ddl7Z7e7jpe7jrze_:e jvjxejzd!<hd"£e_>d#d#d$d%d&d'd(œe_?gd)¢e_@yy#e$rd ZYŒHwxYw#e$rd ZYŒOwxYw)+z=
Pytest configuration and fixtures for the Numpy test suite.
éN)Úcontextmanager)ÚPath)Ú get_fpu_mode)Ú NOGIL_BUILD)Ú dt_configTFz .hypothesisz
numpy-profile)ÚnameÚdeadlineÚ
print_blobznp.test() profile)rr r
ÚdatabaseÚ derandomizeÚsuppress_health_checkz..z
pytest.iniÚNUMPY_EXPERIMENTAL_DTYPE_APIcó|jdd«|jdd«|jdd«|jdd«ts7|jdd«|jdd«|jdd«yy) NÚmarkersz=valgrind_error: Tests that are known to error under valgrind.z:leaks_references: Tests that are known to leak references.zslow: Tests that are very slow.z,slow_pypy: Tests that are very slow on pypy.zOparallel_threads(n): run the given test function in parallel using `n` threads.zCiterations(n): run the given test function `n` times in each threadz8thread_unsafe: mark the test function as single-threaded)Úaddinivalue_lineÚPARALLEL_RUN_AVALIABLE)Úconfigs úQ/home/antigravity/intellecton/venv/lib/python3.12/site-packages/numpy/conftest.pyÚpytest_configurer>s—Ø
×јIØIà
×јIØFà
×ј
×јIØ ×Ñ  ð

ð ×Ñ  Ø 
ð ×Ñ  Ø 
ð có.|jdddd¬«y)Nz--available-memoryÚstorezïSet amount of memory available for running the test suite. This can result to tests requiring especially large amounts of memory to be skipped. Equivalent to setting environment variable NPY_AVAILABLE_MEM. Default: determinedautomatically.)ÚactionÚdefaultÚhelp)Ú addoption)Úparsers rÚpytest_addoptionrTs!Ø
×ÑÐ)°'À4ðõ.rcóf|jjd«}||tjd<yy)available_memoryÚNPY_AVAILABLE_MEM)rÚ getoptionÚosÚenviron)ÚsessionÚ
available_mems rÚpytest_sessionstartr(cs1Ø—N,Ð-?Ó@€MØÐ Ø*7Œ
Ð!rcó´trÒtsËtj«r¶|}|j «|j dddd¬«|j
d«|j
d«|j
d«|j
d«|j
d «|j
d
«|j
d «tjd d
¬«yyyy)NzGIL re-enabledú=T)ÚsepÚredÚboldz3The GIL was re-enabled at runtime during the tests.z;This can happen with no test failures if the RuntimeWarningz9raised by Python when this happens is filtered by a test.Úz;Please ensure all new C modules declare support for runningz:without the GIL. Any new tests that intentionally imports z:code that re-enables the GIL should do so in a subprocess.zGIL re-enabled during testsé)Ú
returncode) rÚgil_enabled_at_startÚsysÚ_is_gil_enabledÚensure_newlineÚsectionÚlineÚpytestÚexit)ÚterminalreporterÚ
exitstatusrÚtrs rÚpytest_terminal_summaryr<iÝÕ/´C×4GÑ4GÔ4IØ
ˆØ
×ÑÔØ
а$¸Tˆ
Ô
Ð
Ð
Ð
Œ Ø
Ð
Ð
Ð Ð1¸aÖ5JÐ/€{r)Útryfirstcó<t«}t|an|tk7rt|ft|<|at|j«j
tt «j
dz dz k(r0|jtjjd¬««yy)
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.
f2pyÚtestszf2py tests are thread-unsafe)Úreason) rÚ
_old_fpu_modeÚ_collect_resultsrÚfspathÚparentÚ__file__Ú
add_markerr7ÚmarkÚ
thread_unsafe)ÚitemÚmodes rÚpytest_itemcollectedrLxsô ‹>€DäÐØ
Ø