[Python-Dev] Re: Pay for PR review and merging for VxWorks RTOS
Hi, Dong-hee: Thanks for your comments. If that is helpful for coredev's review, I can set it up. However, since the porting to VxWorks has not been done, I am afraid that we are not allowed to connect the Buildbot to avoid breaking the existing CI. Is it possible just setting a Buildbot 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 VxWorks RTOS > 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 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 modules to support subprocess module. > However, this is not significant amount of codes, just around 500 lines of C > codes. Hopes any core dev could help to review and merge the simple > compatibility patches. If I can be granted the commit privileges, that will > be great. To ensure the quality, I will get the patches reviewed enough well > before merging. > > For long term support for VxWorks RTOS, I am an engineer from Wind River. > Wind River is willing to officially provide the support and I am willing to > be the maintainer. Buildbot is also not a problem. Once the patches have been > merging done, we will connect the buildbot for VxWorks. > > > > Thanks, > > Peixing > > > > From: Kyle Stanley > Sent: Thursday, August 6, 2020 9:27 AM > To: Xin, Peixing > Cc: python-dev@python.org; Meng, Bin > Subject: Re: [Python-Dev] Pay for PR review and merging for VxWorks > RTOS > > > > 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 > support for the platform. > > > > In order to provide support for a new platform that we don't presently have > support for in CPython, it requires the following: > > > > 1) An existing core developer willing to provide long-term support for the > platform. Alternatively, someone else can be granted commit privileges, for > the purpose of maintaining that platform and fixing any issues that come up > in that CI that are specific to it. However, this is done on a case-by-case > basis, as it still requires a decent amount of trust with that individual. > > > > 2) A stable buildbot provided, to test against new changes made to CPython. > > > > The purpose of the above is to ensure that any substantial platform-specific > code added to CPython receives proper care; this is opposed to a large > addition of new code for a platform that has nobody to take care of it when > issues come up. Especially as a group of mostly volunteers (and those paid by > their employers to contribute), the latter wouldn't be sustainable. I > personally think it would be fantastic to have official support for real-time > OSs in CPython, but in this ecosystem, it requires being able to place trust > in someone that's willing and adequately proficient in the related areas to > provide long-term support for them. > > > > For more details, see PEP 11: > https://www.python.org/dev/peps/pep-0011/#supporting-platforms. > > > > > > On Wed, Aug 5, 2020 at 7:44 AM Xin, Peixing wrote: > > Hi, Python developers: > > > > Anyone interested in PR review and merging for VxWorks RTOS? We can give a > proper pay for that. Contact me if you have interest. > > > > Thanks, > > Peixing > > > > ___ > Python-Dev mailing list -- python-dev@python.org To unsubscribe send > an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/HA > TTYX3BWEIPVVUL7FMSNSCFYOBPS6OD/ Code of Conduct: > http://python.org/psf/codeofconduct/ > > ___ > Python-Dev mailing list -- python-dev@python.org To unsubscribe send > an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/TJ > M24KANKBKLQSFZIH42V4G4WLZ7MGO3/ Code of Conduct: > http://python.org/psf/codeofconduct/ -- Software Development Engineer at Kakao corp. Tel: +82 010-3353-9127 Email: donghee.n...@gmail.com |
[Python-Dev] Re: Python Documentation, Python language improvement, and productive discussion
Add my name. From: python-dev-requ...@python.org Sent: Sunday, August 9, 2020 11:00 AM To: python-dev@python.org Subject: Python-Dev Digest, Vol 205, Issue 17 Send Python-Dev mailing list submissions to python-dev@python.org To subscribe or unsubscribe via the World Wide Web, visit https://mail.python.org/mailman3/lists/python-dev.python.org/ or, via email, send a message with subject or body 'help' to python-dev-requ...@python.org You can reach the person managing the list at python-dev-ow...@python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Python-Dev digest..." Today's Topics: 1. Re: Python Documentation, Python language improvement, and productive discussion (Mats Wichmann) -- Date: Sun, 9 Aug 2020 09:39:32 -0600 From: Mats Wichmann Subject: [Python-Dev] Re: Python Documentation, Python language improvement, and productive discussion To: python-dev@python.org Message-ID: <421995fd-99ae-99a5-0262-33d243c93...@python.org> Content-Type: text/plain; charset=utf-8 On 8/5/20 10:43 AM, Dominic Davis-Foster wrote: > Hi Carol, > > I was wondering if you've been able to set up the workgroup yet? I'd > certainly be interested in participating the there's an opportunity. > > > Stay safe > > Dom Indeed, I was wondering if there were any updates - I'm also interested in participating. -- mats -- Subject: Digest Footer ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ -- End of Python-Dev Digest, Vol 205, Issue 17 *** ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/LB4UEY5BQB4PDLOTSVYLCCAOFL6ZBYS5/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Python Documentation, Python language improvement, and productive discussion
Hi folks, Thanks for the interest. I apologize for the delay in getting this workgroup started. I'm happy that there is strong interest in working on documentation and improving it for all users. I will do my best to get the workgroup charter drafted this week and then open an interest list for initial workgroup members. Luciano, I agree that rewriting asyncio docs and typing are helpful improvements and welcome your contributions to accessible and high quality docs. Warmly, Carol On Sun, Aug 9, 2020 at 9:21 AM Luciano Ramalho wrote: > I am also interested in helping with making Python's documentation > more user friendly. > > Yuri Selivanov's rewrite of the asyncio documentation was brilliant. > We need more of that. > > My recent contribution to Python's doc doesn't compare with > Selivanov's awesome rewrite, but it involved reorganizing existing > documentation. > > The typing module chapter in the library reference is comprehensive, > and the top 1/3 of it has good narrative explanations to the core > concepts. But the remaining 2/3 of the content is in a single section > titled "Classes, functions, and decorators" that covers more than 70 > objects, and there's no apparent ordering. > > With the help of Guido, I split that section in subsections, and > arranged the entries within the subsections by relevance to most > users—subjective, yes, but not too harmful if we made bad calls, > because now there are fewer entries per subsection. > > Before: > https://docs.python.org/3.8/library/typing.html > > After: > https://docs.python.org/3.10/library/typing.html > > Cheers, > > Luciano > > On Sun, Aug 9, 2020 at 12:43 PM Mats Wichmann wrote: > > > > On 8/5/20 10:43 AM, Dominic Davis-Foster wrote: > > > Hi Carol, > > > > > > I was wondering if you've been able to set up the workgroup yet? I'd > certainly be interested in participating the there's an opportunity. > > > > > > > > > Stay safe > > > > > > Dom > > > > Indeed, I was wondering if there were any updates - I'm also interested > > in participating. > > > > -- mats > > ___ > > Python-Dev mailing list -- python-dev@python.org > > To unsubscribe send an email to python-dev-le...@python.org > > https://mail.python.org/mailman3/lists/python-dev.python.org/ > > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/MRV5SQCC2GC6MLIUCSPJZL3AQCXVDUEG/ > > Code of Conduct: http://python.org/psf/codeofconduct/ > > > > -- > Luciano Ramalho > | Author of Fluent Python (O'Reilly, 2015) > | http://shop.oreilly.com/product/0636920032519.do > | Technical Principal at ThoughtWorks > | Twitter: @ramalhoorg > ___ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/P6S4Q3H6VOXVJTXX4UCRRYDCIDLC2M4C/ > Code of Conduct: http://python.org/psf/codeofconduct/ > ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/ZTIK4R7HNPV2HZJ6TJHONGCCYUOSL5CW/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Python Documentation, Python language improvement, and productive discussion
I am also interested in helping with making Python's documentation more user friendly. Yuri Selivanov's rewrite of the asyncio documentation was brilliant. We need more of that. My recent contribution to Python's doc doesn't compare with Selivanov's awesome rewrite, but it involved reorganizing existing documentation. The typing module chapter in the library reference is comprehensive, and the top 1/3 of it has good narrative explanations to the core concepts. But the remaining 2/3 of the content is in a single section titled "Classes, functions, and decorators" that covers more than 70 objects, and there's no apparent ordering. With the help of Guido, I split that section in subsections, and arranged the entries within the subsections by relevance to most users—subjective, yes, but not too harmful if we made bad calls, because now there are fewer entries per subsection. Before: https://docs.python.org/3.8/library/typing.html After: https://docs.python.org/3.10/library/typing.html Cheers, Luciano On Sun, Aug 9, 2020 at 12:43 PM Mats Wichmann wrote: > > On 8/5/20 10:43 AM, Dominic Davis-Foster wrote: > > Hi Carol, > > > > I was wondering if you've been able to set up the workgroup yet? I'd > > certainly be interested in participating the there's an opportunity. > > > > > > Stay safe > > > > Dom > > Indeed, I was wondering if there were any updates - I'm also interested > in participating. > > -- mats > ___ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/MRV5SQCC2GC6MLIUCSPJZL3AQCXVDUEG/ > Code of Conduct: http://python.org/psf/codeofconduct/ -- Luciano Ramalho | Author of Fluent Python (O'Reilly, 2015) | http://shop.oreilly.com/product/0636920032519.do | Technical Principal at ThoughtWorks | Twitter: @ramalhoorg ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/P6S4Q3H6VOXVJTXX4UCRRYDCIDLC2M4C/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Python Documentation, Python language improvement, and productive discussion
On 8/5/20 10:43 AM, Dominic Davis-Foster wrote: > Hi Carol, > > I was wondering if you've been able to set up the workgroup yet? I'd > certainly be interested in participating the there's an opportunity. > > > Stay safe > > Dom Indeed, I was wondering if there were any updates - I'm also interested in participating. -- mats ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/MRV5SQCC2GC6MLIUCSPJZL3AQCXVDUEG/ Code of Conduct: http://python.org/psf/codeofconduct/
