[issue1531415] parsetok.c emits warnings by writing to stderr

Pablo Galindo Salgado added the comment: Closed by https://github.com/python/cpython/pull/17365 -- resolution: -> fixed stage: test needed -> resolved status: open -> closed ___ Python tracker

[issue1531415] parsetok.c emits warnings by writing to stderr

Pablo Galindo Salgado added the comment: https://github.com/python/cpython/pull/17971 -- ___ Python tracker ___ ___

[issue1531415] parsetok.c emits warnings by writing to stderr

Pablo Galindo Salgado added the comment: The C version of pgen is gone so the circular dependency should not be a problem as as far as I can tell, Parser/parsetok.c does not emit warnings anymore (the functions are unused). Maybe we should just clean that code instead. --

[issue1531415] parsetok.c emits warnings by writing to stderr

Brett Cannon added the comment: Pablo, is this still a thing to care about? -- nosy: +pablogsal ___ Python tracker ___ ___

[issue1531415] parsetok.c emits warnings by writing to stderr

Michele Orrù maker...@gmail.com added the comment: This is not the proper workflow for bug tracking. No one is working on this right now is not the same as This bug is invalid. No one worked on this ticket almost *seven years* after I filed it. You are right. Sorry for that. --

[issue1531415] parsetok.c emits warnings by writing to stderr

Sean Reifschneider j...@tummy.com added the comment: Michele: Do you know what needs to be done to determine the resolution to the _warnings/pgen question? If not, maybe asking the question on python-dev could get some advice. -- nosy: +jafo ___

[issue1531415] parsetok.c emits warnings by writing to stderr

Michele Orrù maker...@gmail.com added the comment: May somebody check for this? Otherwise the bug could be considered invalid. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1531415 ___

[issue1531415] parsetok.c emits warnings by writing to stderr

Jean-Paul Calderone invalid@example.invalid added the comment: May somebody check for this? Otherwise the bug could be considered invalid. This is not the proper workflow for bug tracking. No one is working on this right now is not the same as This bug is invalid. No one worked on this

[issue1531415] parsetok.c emits warnings by writing to stderr

Brett Cannon br...@python.org added the comment: It's quite possible you are right, Michele. I don't know if anyone has looked at what exactly is required for _warnings.c compared to pgen. -- ___ Python tracker rep...@bugs.python.org

[issue1531415] parsetok.c emits warnings by writing to stderr

Michele Orrù maker...@gmail.com added the comment: For what I saw these days, Parser/tokenizer.c should import warnings.h (in order to use PyErr_WarnEx()), but Python/_warnings.c imports Python.h, that requires pgen ready. This leads to a circular dependency. Am I wrong / missing something?

[issue1531415] parsetok.c emits warnings by writing to stderr

Michele Orrù maker...@gmail.com added the comment: I am interested in solving this bug. If I understood correctly, that should be just a matter of spitting over sys.stdout whenever the user imports warnings.py, sys.stderr otherwise. Rewriting the code in C for python3.x would still be

[issue1531415] parsetok.c emits warnings by writing to stderr

Brett Cannon br...@python.org added the comment: Not quite, Michele. So this bug is about taking the stuff that is printed to stdout/stderr explicitly in parsetok.c and instead using the warnings functions, e.g. PyErr_Warn(), since _warnings is a built-in module (now) and thus is available to

[issue1531415] parsetok.c emits warnings by writing to stderr

Changes by Éric Araujo mer...@netwok.org: -- versions: -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1531415 ___ ___ Python-bugs-list

[issue1531415] parsetok.c emits warnings by writing to stderr

Changes by Ezio Melotti ezio.melo...@gmail.com: -- versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1531415 ___ ___

[issue1531415] parsetok.c emits warnings by writing to stderr

Terry J. Reedy tjre...@udel.edu added the comment: warning.py it still is in 3.1 -- nosy: +terry.reedy versions: +Python 3.2 -Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1531415