>
Cc: Kyle Stanley mailto:aeros...@gmail.com>>;
python-dev@python.org<mailto:python-dev@python.org>; Meng, Bin
mailto:bin.m...@windriver.com>>; Duan, Kun
mailto:kun.d...@windriver.com>>
Subject: Re: [Python-Dev] Re: Pay for PR review and merging for VxWorks RTOS
> B
thout connecting to CI?
>
> Thanks,
> Peixing
>
> -Original Message-
> From: Dong-hee Na
> Sent: Friday, August 7, 2020 4:01 PM
> To: Xin, Peixing
> Cc: Kyle Stanley ; python-dev@python.org; Meng, Bin <
> bin.m...@windriver.com>; Duan, Kun
> Subje
t for reviewing use without connecting to CI?
Thanks,
Peixing
-Original Message-
From: Dong-hee Na
Sent: Friday, August 7, 2020 4:01 PM
To: Xin, Peixing
Cc: Kyle Stanley ; python-dev@python.org; Meng, Bin
; Duan, Kun
Subject: Re: [Python-Dev] Re: Pay for PR review and merging for Vx
> Buildbot is also not a problem.
The early issue from the core developer side, it would be helpful to
review if the Buildbot is supported by Wind River for VxWorks.
2020년 8월 6일 (목) 오후 1:16, Xin, Peixing 님이 작성:
>
> Hi, Stanley:
>
>
>
> Thanks for your comments.
>
>
>
> Almost all the patches are
Hi, Stanley:
Thanks for your comments.
Almost all the patches are simple compatibility patch. But the subprocess
module is an exception. Like windows, VxWorks have no fork/exec API provided.
Instead, VxWorks uses rtpSpawn() to spawn a new process. So we have to
implement VxWorks’ own extension
What exactly does the PR involve? Is it a relatively simple compatibility
patch or something that adds significant amounts of platform-specific code?
The former can be reviewed (and potentially merged) by any core dev
knowledgeable in the areas being changed, but the latter requires long-term
suppo
