[Python-Dev] [Issue1531415] Using PyErr_WarnEx on parsetok (original) (raw)
Michele Orrù maker.py at gmail.com
Wed Mar 14 17:22:23 CET 2012
- Previous message: [Python-Dev] 2012 Language Summit Report
- Next message: [Python-Dev] cpython: PEP 417: Adding unittest.mock
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
As pointed by Sean Reifschneider in issue 1531415, I'm writing this mail mainly to ask for advices concerning python's makefile.
Currently, Parser/parsetok.c writes directly to stderr in case no more memory is avaible. So, it would be nice™ to use, instead of a raw printf, the functions provided by Python/_warnings.c (PyErr_NoMemory and/or PyErr_WarnEx). This, right now, leads to a circular dependency, as described here: http://bugs.python.org/msg154939 .
So far I've seen some functions present both in Python/ and pgenmain.c : PyErrOccurred(), PyFatalError(const char *msg), PyExit(int). This means a dirty alternative could be to implement another function PyErr_WarnEx; but probably there is a better way to organize the makefile, becouse currently I'm using the entire $(PYTHON_OBJS) (seems needed by warnigs.o).
This is the first time I run into python c code, so please be patient :)
ù
- Previous message: [Python-Dev] 2012 Language Summit Report
- Next message: [Python-Dev] cpython: PEP 417: Adding unittest.mock
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]