Thomas Kluyver added the comment:
It seems pretty arbitrary and newcomer-unfriendly to decide that Python doesn't
support running setup.py inside IDLE.
Exhibit A: confused newcomer trying to install distribute, getting unhelpful
error message.
Changes by Serhiy Storchaka storch...@gmail.com:
--
resolution: - duplicate
status: open - pending
superseder: - IDLE and Command line present different behavior for sys.stdin
___
Python tracker rep...@bugs.python.org
Terry J. Reedy added the comment:
Thomas, please re-read the messages starting msg145215 where it was decided
that this is not an issue about setup.py in particular. There appears to now
only be a problem if IDLE is run without a subprocess, and that option may
disappear in 3.4 as unneeded.
Terry J. Reedy added the comment:
Even though the title of #9290 says stdin, the patches are for all std**
streams, so should cover this.
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12967
Changes by Terry J. Reedy tjre...@udel.edu:
--
stage: needs patch - committed/rejected
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12967
___
___
Serhiy Storchaka added the comment:
If this issue only about 'errors' attribute of IDLE RPC Proxy for standard IO
streams, then it should be closed as outdated. If this issue about 'errors'
attribute of IDLE standard IO streams (even when running IDLE without a
subprocess), then the patches
Roger Serwy roger.se...@gmail.com added the comment:
Issue13532 has an applied patch (422242dbce30) for the subprocess that makes
the stdout, stderr, and stdin inherit from io.TextIOBase. This includes the
errors attribute, albeit set to ''.
The fix does not apply when running IDLE without a
Glenn Linderman v+pyt...@g.nevcal.com added the comment:
So this looks like it might be a simple fix... in issue 1602, there was a patch
for Windows console for 3.1... sadly not applied then, or 3.2, or 3.3 (yet).
But in 3.2, the fix sprouted a failure just like this one: the console output
Changes by Terry J. Reedy tjre...@udel.edu:
--
nosy: +serwy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12967
___
___
Python-bugs-list mailing
Terry J. Reedy tjre...@udel.edu added the comment:
Thank you for redirecting this issue. The goal should be to make the proxies
completely transparent. They mostly are, but occasional issues arise when they
are not. Sometimes the source of a problem is not clear. I wonder, for
instance,
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12967
___
___
Ned Deily n...@acm.org added the comment:
I don't have a strong opinion about whether running setup.py in IDLE is
supported. But that's not the real issue here. The problem is that the IDLE
RPC proxy of the standard IO streams is incomplete, in particular, the 'errors'
attribute of
Changes by Éric Araujo mer...@netwok.org:
--
nosy: -eric.araujo, tarek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12967
___
___
13 matches
Mail list logo
