This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | serhiy.storchaka |
|---|---|
| Recipients | ajaksu2, loewis, roger.serwy, serhiy.storchaka, terry.reedy |
| Date | 2012年07月12日.09:44:25 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1342086266.59.0.454698051115.issue7163@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Reply to Roger's emailed answer to my Rietveld comment. > On 07/11/2012 11:10 AM, storchaka@gmail.com wrote: > > http://bugs.python.org/review/7163/diff/4367/Lib/idlelib/OutputWindow.py > > File Lib/idlelib/OutputWindow.py (right): > > > > http://bugs.python.org/review/7163/diff/4367/Lib/idlelib/OutputWindow.py#newcode43 > > Lib/idlelib/OutputWindow.py:43: return len(s) > > write() should return count of bytes if argument is bytes. > Only strings should be passed into the write method in 3.3. The code > for decoding bytes is a historical artifact that should be removed. You > can witness this evolution by using hgtk datamine. We can ask the author. Martin, why OutputWindow.write accepts bytes in a724279fc931? Should it be deleted if it is deprecated artifact or should OutputWindow.write return bytes count for bytes if it will return character count for string? > On 2.7, byte counts (AFAIK) are not returned for sys.stdout.write. On Python2 sys.stdout.write does not returns any count. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年07月12日 09:44:26 | serhiy.storchaka | set | recipients: + serhiy.storchaka, loewis, terry.reedy, ajaksu2, roger.serwy |
| 2012年07月12日 09:44:26 | serhiy.storchaka | set | messageid: <1342086266.59.0.454698051115.issue7163@psf.upfronthosting.co.za> |
| 2012年07月12日 09:44:26 | serhiy.storchaka | link | issue7163 messages |
| 2012年07月12日 09:44:25 | serhiy.storchaka | create | |