On 28Dec2018 20:21, Daniel Ojalvo wrote:
I agree that previous behavior shouldn't be changed, but I would
suggest updating the documentation to point it out as a footnote. The
current behavior is correct just unclear. Most people just learning
about the open command wouldn't have this
On Sat, Dec 29, 2018 at 7:21 AM Daniel Ojalvo wrote:
>
> Thank you for the advice!
>
> I haven't used the opener argument before, but I'll keep it for future
> reference. I think it's still a little kludge-y, but it works.
It has a very similar effect to what you were proposing, but still
works
ng said, I think I would like to put in a feature request for a
non-blocking option. How should I go about doing so?
Thanks again,
Dan
-Original Message-
From: Chris Angelico
Sent: Thursday, December 27, 2018 7:10 PM
To: python-list@python.org
Subject: Re: Undocumented issue: Open system c
On Sat, Dec 29, 2018 at 4:24 AM Grant Edwards wrote:
>
> On 2018-12-27, Daniel Ojalvo via Python-list wrote:
>
> open("this_is_a_pipe")
> >
>
> Opening a tty device can also block[1]. However, if somebody is using
> the open() builtin on tty devices that's probably the least of their
>
On 2018-12-27, Daniel Ojalvo via Python-list wrote:
open("this_is_a_pipe")
>
Opening a tty device can also block[1]. However, if somebody is using
the open() builtin on tty devices that's probably the least of their
problems.
[1] Technically, opening any character-mode device could block
On Fri, Dec 28, 2018 at 1:38 PM Daniel Ojalvo via Python-list
wrote:
>
> Hello,
>
> I've been working on a python3 project and I came across an issue with the
> open system call that, at the very least, isn't documented. In my humble
> opinion, the
>
