[issue11792] asyncore module print to stdout

2014-06-14 Thread Giampaolo Rodola'
Giampaolo Rodola' added the comment: Looking back at this: a warning seems a bit too invasive to me as there are cases where avoiding to override a certain methods are legitimate. I will just close this out as won't fix, also because asyncore has been deprecated by asyncio. -- resoluti

[issue11792] asyncore module print to stdout

2011-05-31 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- versions: -Python 2.5, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue11792] asyncore module print to stdout

2011-04-08 Thread Éric Araujo
Éric Araujo added the comment: Some guidance on print vs. warnings vs. logging on http://docs.python.org/dev/howto/logging#when-to-use-logging -- nosy: +eric.araujo ___ Python tracker

[issue11792] asyncore module print to stdout

2011-04-07 Thread Samuele Kaplun
Samuele Kaplun added the comment: Hi Giampaolo, shouldn't then the 2nd option I was proposing (i.e. to call warning.warn) the best behavior, given your explanation? [...] Warning messages are typically issued in situations where it is useful to alert the user of some condition in a program,

[issue11792] asyncore module print to stdout

2011-04-07 Thread Giampaolo Rodola'
Giampaolo Rodola' added the comment: asyncore is a minimalistic and generic framework; as such it should not "privilege" a specific application such as mod_wsgi or make any other assumption. I'd say it's fine to let user decide what to do in its own subclass. Furthermore, log_info() is used

[issue11792] asyncore module print to stdout

2011-04-07 Thread Samuele Kaplun
Samuele Kaplun added the comment: Thanks for looking into it. Indeed that's the workaround I implemented in our application. On the other hand it would be nice if either: * the log_info method would print to stderr, * would use warning.warn() * would use the logging module to allow for fine g

[issue11792] asyncore module print to stdout

2011-04-07 Thread Giampaolo Rodola'
Giampaolo Rodola' added the comment: What change are you proposing exactly? Btw, overriding log_info() in such cases seems reasonable to me, without changing anything in asyncore. -- ___ Python tracker __

[issue11792] asyncore module print to stdout

2011-04-07 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- assignee: -> giampaolo.rodola nosy: +giampaolo.rodola stage: -> needs patch versions: +Python 3.2, Python 3.3 -Python 2.6 ___ Python tracker ___

[issue11792] asyncore module print to stdout

2011-04-07 Thread Samuele Kaplun
New submission from Samuele Kaplun : The method "log_info" of the "dispatcher" class of the asyncore.py module, uses print statement to print to stdout. This lead to conflicts when asyncore is used within e.g. mod_wsgi, as writing to stdout is not supposed to be valid. -- components: