From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin@cygwin.com
Subject: Re: Tee and file redirections are very slow to write anything.
Date: Sun, 18 Apr 2021 19:45:58 +0100 [thread overview]
Message-ID: <DB3PR0202MB3561A1059D73FCFA609522C3E74A9@DB3PR0202MB3561.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <20210225192710.c12222669e0927e94dc71b3c@nifty.ne.jp>
[-- Attachment #1.1.1: Type: text/plain, Size: 648 bytes --]
Excellent, I shall give that a try. Thanks.
Hamish
On 25/02/2021 10:27, Takashi Yano via Cygwin wrote:
> On Thu, 25 Feb 2021 09:51:48 +0000
> "Henry S. Thompson wrote:
>> Hamish McIntyre-Bhatty via Cygwin writes:
>>
>>> I'm now thinking it may have been a Python script that was behaving this
>>> way - I might go and double check in case this isn't what I think it is.
>> I have noticed recently (on a Linux box) that Python3.8 logging exhibits
>> the problem you report, that is, no output until end of job.
> stdbuf does not take effect for python, however, you can use
> -u option or setting environment PYTHONUNBUFFERED=1.
>
[-- Attachment #1.1.2: OpenPGP_0x18F1759B3457223F.asc --]
[-- Type: application/pgp-keys, Size: 3175 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2021-04-18 18:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 20:33 Hamish McIntyre-Bhatty
2021-02-24 20:48 ` ASSI
2021-02-24 20:59 ` Hamish McIntyre-Bhatty
2021-02-24 21:58 ` Eliot Moss
2021-02-24 22:41 ` Duncan Roe
2021-02-24 23:26 ` Takashi Yano
2021-02-25 3:54 ` Eliot Moss
2021-02-24 23:50 ` Brian Inglis
2021-02-25 7:50 ` Brian Inglis
2021-02-25 9:21 ` Hamish McIntyre-Bhatty
2021-02-25 9:51 ` Henry S. Thompson
2021-02-25 10:27 ` Takashi Yano
2021-04-18 18:45 ` Hamish McIntyre-Bhatty [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB3PR0202MB3561A1059D73FCFA609522C3E74A9@DB3PR0202MB3561.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.uk \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).