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

[Jean-Paul Calderone]

Jean-Paul Calderone <invalid at 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 ticket almost *seven years* after I filed it.

The "invalid" state in the issue tracker is for issues that have been filed that *do not describe a bug that exists at all* (or a feature is being rejected as a bad idea or something that will otherwise not be added to Python and will not be implemented).

Please do not close tickets as invalid just because no one is working on resolving them *right now*.  The purpose of closing issues is to keep track of useful development that is happening.  In and of itself, closing issues is a useless activity; it is only useful inasmuch as it reflects useful development.

----------
nosy: +exarkun

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue1531415>
_______________________________________