Message 154962 - Python tracker

➜

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	vstinner
Recipients	giampaolo.rodola, loewis, nkxyz, vstinner
Date	2012-03-05.16:40:34
SpamBayes Score	1.8405132e-07
Marked as misclassified	No
Message-id	<CAMpsgwZe0m-eZxyA2Orgy5k0CE5+GNeXgmPLfyc3+iaddfTY_w@mail.gmail.com>
In-reply-to	<1330964375.88.0.447993480055.issue14170@psf.upfronthosting.co.za>

Content
> Victor: why do you think this is a duplicate of #11395? That issue deals with long output strings, which doesn't seem to be the case here. IOError('[Errno 28] No space left on device') was exactly the #11395 error message. Without the full test script, i cannot be sure that it's a duplicate. "C:\Users\__test.py, line 96": it looks like the program has ~100 lines and so may write something else to the console. There are buffers in TextIOWrapper, BufferedWriter and the Windows console itself. By the way, Python maps the Windows error ERROR_DISK_FULL (112) to ENOSPC (28). It's maybe something completly different.

> Victor: why do you think this is a duplicate of #11395? That issue deals with long output strings, which doesn't seem to be the case here.

IOError('[Errno 28] No space left on device') was exactly the #11395
error message. Without the full test script, i cannot be sure that
it's a duplicate. "C:\Users\__test.py, line 96": it looks like the
program has ~100 lines and so may write something else to the console.
There are buffers in TextIOWrapper, BufferedWriter and the Windows
console itself. By the way, Python maps the Windows error
ERROR_DISK_FULL (112) to ENOSPC (28).

It's maybe something completly different.

History
Date	User	Action	Args
2012-03-05 16:40:35	vstinner	set	recipients: + vstinner, loewis, giampaolo.rodola, nkxyz
2012-03-05 16:40:34	vstinner	link	issue14170 messages
2012-03-05 16:40:34	vstinner	create