[Python-Dev] Incorrect documentation of the raw_input built-in function (original) (raw)
Jeroen Ruigrok van der Werven asmodai at in-nomine.org
Mon Jan 28 20:55:35 CET 2008
- Previous message: [Python-Dev] Incorrect documentation of the raw_input built-in function
- Next message: [Python-Dev] Incorrect documentation of the raw_input built-in function
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-On [20080128 19:51], Jeroen Ruigrok van der Werven (asmodai at in-nomine.org) wrote:
I cannot find anything explicitly in favour of or against this in POSIX. The stuff quoted below is what I could find. I do not think there's a hard mandate either way, but from my experience of having been a committer for both FreeBSD and DragonFly BSD for a number of years stderr was not preferred for prompting. stderr was always the domain of diagnostics.
Sorry, I made a mental typo here:
but from my experience of having been a committer for both FreeBSD and DragonFly BSD for a number of years stdout was not preferred for prompting. stderr was always the domain of diagnostics.
-- Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ We have met the enemy and they are ours...
- Previous message: [Python-Dev] Incorrect documentation of the raw_input built-in function
- Next message: [Python-Dev] Incorrect documentation of the raw_input built-in function
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]