This repository was archived by the owner on Feb 13, 2025. It is now read-only.
eliminate printf() calls #167
Comments
akruis
pushed a commit
that referenced
this issue
Aug 5, 2018
printf() was used to emit parts of an error message, if there is a pending error while entering Stackless subsystem.
|
Ported to master-slp: ef448f3 |
akruis
pushed a commit
that referenced
this issue
Aug 7, 2018
printf() was used to emit parts of an error message, if there is a pending error while entering Stackless subsystem. (cherry picked from commit 8a44a5f)
akruis
pushed a commit
that referenced
this issue
Aug 7, 2018
printf() was used to emit parts of an error message, if there is a pending error while entering Stackless subsystem. (cherry picked from commit 8a44a5f)
akruis
pushed a commit
that referenced
this issue
Aug 7, 2018
printf() was used to emit parts of an error message, if there is a pending error while entering Stackless subsystem. (cherry picked from commit 8a44a5f)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are two
printf(...)calls in Stackless/module/scheduling.c. They are used to emit an error message, if there is a pending error while entering Stackless subsystem. You won't see this message, unless you use the C-API. I noticed theprintf()calls while preparing a test for #166. Besides using printf() is a no-go by itself, the rest of the error message - emitted byPyErr_Print()- goes to stderr.Task: Replace the
printf()withPySys_WriteStderr(...).The text was updated successfully, but these errors were encountered: