/dports/devel/py-cysignals/cysignals-1.11.1/docs/source/ |
H A D | interrupt.rst | 97 Using ``sig_on()`` and ``sig_off()`` 112 sig_on() 120 ``sig_on()`` returns. The reason is that ``sig_on()`` is implemented using 127 sig_on() 142 sig_on() 165 to ``sig_on()`` (the first one if there is a stack) and ``sig_on()`` will raise 187 sig_on() 192 sig_on() 204 sig_on() 230 sig_on() [all …]
|
H A D | signals.rst | 4 Apart from handling interrupts, :ref:`sig_on() <section_sig_on>` 9 If the code inside ``sig_on()`` would generate a segmentation fault or call the 17 from cysignals.signals cimport sig_on, sig_off 20 sig_on() 32 A segmentation fault or ``abort()`` unguarded by ``sig_on()`` would simply 33 terminate the Python Interpreter. This applies only to ``sig_on()``, the 36 Instead of ``sig_on()``, there is also a function ``sig_str(s)``, which takes a 37 C string ``s`` as argument. It behaves the same as ``sig_on()``, except that the 59 same as ``sig_on()``: a simple ``KeyboardInterrupt`` is raised.
|
H A D | sigerror.rst | 11 function may only be called within a ``sig_on()`` block (otherwise the Python 17 ``sig_on()`` machinery such that the exception will be seen by ``sig_on()``. 29 the ``sig_on()`` in a ``try``/``except`` block. 37 from cysignals.signals cimport sig_on, sig_off 40 sig_on() # This must be INSIDE the try
|
H A D | sigadvanced.rst | 43 mentioned above, ``sig_on()`` makes no attempt to clean anything up (restore 45 impossible for ``sig_on()`` to do that. If you want to add some cleanup code, 47 ``sig_on()``, except that any exception raised (like ``KeyboardInterrupt`` or 83 ``with nogil`` blocks. If ``sig_on()`` needs to raise an exception, the GIL is 93 The GIL should never be released or acquired inside a ``sig_on()`` block. If 94 you want to use a ``with nogil`` block, put both ``sig_on()`` and
|
H A D | crash.rst | 8 fault outside a ``sig_on()`` block. 19 in it and is not properly wrapped with sig_on(), sig_off().
|
/dports/math/py-fpylll/fpylll-0.5.6/src/fpylll/fplll/ |
H A D | bkz.pyx | 316 sig_on() 327 sig_on() 331 sig_on() 335 sig_on() 346 sig_on() 350 sig_on() 391 sig_on() 402 sig_on() 406 sig_on() 410 sig_on() [all …]
|
H A D | pruner.pyx | 130 sig_on() 395 sig_on() 406 sig_on() 422 sig_on() 472 sig_on() 483 sig_on() 499 sig_on() 550 sig_on() 1000 sig_on() 1013 sig_on() [all …]
|
H A D | lll.pyx | 232 sig_on() 245 sig_on() 250 sig_on() 255 sig_on() 268 sig_on() 273 sig_on() 319 sig_on() 323 sig_on() 341 sig_on() 605 sig_on() [all …]
|
H A D | gso.pyx | 1729 sig_on() 1740 sig_on() 1756 sig_on() 1762 sig_on() 1773 sig_on() 1789 sig_on() 1806 sig_on() 1811 sig_on() 1816 sig_on() 1840 sig_on() [all …]
|
H A D | svpcvp.pyx | 11 from cysignals.signals cimport sig_on, sig_off 124 sig_on() 128 sig_on() 132 sig_on() 215 sig_on()
|
H A D | wrapper.pyx | 5 from cysignals.signals cimport sig_on, sig_off 69 sig_on()
|
H A D | enumeration.pyx | 9 from cysignals.signals cimport sig_on, sig_off 370 sig_on() 396 sig_on() 421 sig_on() 447 sig_on() 472 sig_on() 497 sig_on()
|
/dports/devel/py-cysignals/cysignals-1.11.1/src/cysignals/ |
H A D | tests.pyx | 199 sig_on() 227 sig_on() 241 sig_on() 262 sig_on() 279 sig_on() 297 sig_on() 399 sig_on() 834 sig_on() 855 sig_on() 873 sig_on() [all …]
|
H A D | signals.pxd.in | 36 int sig_on() except 0 45 # Macros behaving exactly like sig_on, sig_str and sig_check but 48 int sig_on_no_except "sig_on"()
|
H A D | cysignals_config.h.in | 14 * Should sig_on() use sigsetjmp(env, 0) instead of setjmp(env)? This
|
H A D | macros.h | 206 #define sig_on() _sig_on_(NULL)
|
/dports/irc/ircII/ircii-20210314/source/ |
H A D | irc.c | 124 static void sig_on(int); 258 sig_on(int signo) in sig_on() function 930 (void) MY_SIGNAL(SIGPIPE, (sigfunc *) sig_on, 0); in main() 933 (void) MY_SIGNAL(SIGSTOP, (sigfunc *) sig_on, 0); in main() 940 (void) MY_SIGNAL(SIGUSR2, (sigfunc *) sig_on, 0); in main() 944 (void) MY_SIGNAL(SIGPWR, (sigfunc *) sig_on, 0); in main() 947 (void) MY_SIGNAL(SIGCHLD, (sigfunc *) sig_on, 0); in main() 950 (void) MY_SIGNAL(SIGURG, (sigfunc *) sig_on, 0); in main() 977 (void) MY_SIGNAL(SIGLWP, (sigfunc *) sig_on, 0); in main() 980 (void) MY_SIGNAL(SIGSYS, (sigfunc *) sig_on, 0); in main() [all …]
|
/dports/math/libbraiding/libbraiding-1.1/ |
H A D | library.pyx | 61 sig_on() 89 sig_on() 117 sig_on() 129 sig_on() 141 sig_on() 160 sig_on() 171 sig_on() 182 sig_on() 194 sig_on() 210 sig_on() [all …]
|
/dports/math/py-cypari2/cypari2-2.1.2/cypari2/ |
H A D | gen.pyx | 100 sig_on() 244 sig_on() 506 sig_on() 533 sig_on() 543 sig_on() 554 sig_on() 573 sig_on() 592 sig_on() 619 sig_on() 651 sig_on() [all …]
|
H A D | convert.pyx | 44 from cysignals.signals cimport sig_on, sig_off, sig_error 395 sig_on() 557 sig_on() 561 sig_on() 565 sig_on() 569 sig_on() 573 sig_on() 584 sig_on() 589 sig_on() 625 sig_on() [all …]
|
H A D | pari_instance.pyx | 684 sig_on() 710 sig_on() 768 sig_on() 799 sig_on() 1065 sig_on() 1138 sig_on() 1160 sig_on() 1181 sig_on() 1206 sig_on() 1242 sig_on() [all …]
|
H A D | closure.pyx | 36 from cysignals.signals cimport sig_on, sig_off, sig_block, sig_unblock, sig_error 126 # is very likely called within sig_on() and interrupting arbitrary 139 sig_on() 230 sig_on()
|
H A D | stack.pyx | 23 from cysignals.signals cimport (sig_on, sig_off, sig_block, sig_unblock, 59 PyErr_SetString(SystemError, "calling remove_from_pari_stack() inside sig_on()") 125 sig_on() 158 sig_on()
|
/dports/math/py-cypari2/cypari2-2.1.2/venv/lib/python3.7/site-packages/cysignals/ |
H A D | signals.pxd | 36 int sig_on() except 0 45 # Macros behaving exactly like sig_on, sig_str and sig_check but 48 int sig_on_no_except "sig_on"()
|
/dports/devel/py-cysignals/cysignals-1.11.1/example/ |
H A D | cysignals_example.pyx | 19 This function can be safely called within a sig_on block.
|