Message 300968 - 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	gregory.p.smith
Recipients	gregory.p.smith
Date	2017-08-28.23:01:53
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1503961313.68.0.46157569619.issue31296@psf.upfronthosting.co.za>
In-reply-to

Content
The PyPI pexpect.spawn API is incompatible with multithreaded code thanks to its dependency on pty.fork() and running non async signal safe code between fork() and exec(). https://github.com/pexpect/ptyprocess/issues/43 https://github.com/pexpect/pexpect/issues/369 If subprocess supported pty.fork() and pexpect.pty_spawn.spawn like actions, pexpect could use that by default instead of the threading incompatible pty.fork(). (this is a brainstorm, see what the pexpect maintainers want in the above github issues)

The PyPI pexpect.spawn API is incompatible with multithreaded code thanks to its dependency on pty.fork() and running non async signal safe code between fork() and exec().
 https://github.com/pexpect/ptyprocess/issues/43
 https://github.com/pexpect/pexpect/issues/369

If subprocess supported pty.fork() and pexpect.pty_spawn.spawn like actions, pexpect could use that by default instead of the threading incompatible pty.fork().

(this is a brainstorm, see what the pexpect maintainers want in the above github issues)

History
Date	User	Action	Args
2017-08-28 23:01:53	gregory.p.smith	set	recipients: + gregory.p.smith
2017-08-28 23:01:53	gregory.p.smith	set	messageid: <1503961313.68.0.46157569619.issue31296@psf.upfronthosting.co.za>
2017-08-28 23:01:53	gregory.p.smith	link	issue31296 messages
2017-08-28 23:01:53	gregory.p.smith	create