[Python-Dev] [edk2] Official port of Python on EDK2 (original) (raw)

Thiebaud Weksteen tweek at google.com
Thu Nov 2 06:52:35 EDT 2017

Christian, Antoine, Brett: Thanks for the clarification on what an official support would require. As Christian mentioned, sending simple headers patches is an obvious starting point, no matter if the support becomes official or not.

Brian: Thanks for your email. As I suggested, by having the support directly within the Python community, you would avoid having to maintain a separate port. I don't think that having a new Python3 port as part of EDK2 is a good idea. What I am suggesting is that Intel should contribute directly to the Python repository by sending your modifications upstream and not expect someone to re-import Python into EDK2. That is, bringing your UEFI experience to Python and not the opposite. This would be a much better use of anyone's time.

Thanks, Thiebaud

On Thu, Nov 2, 2017 at 2:36 AM, Richardson, Brian < brian.richardson at intel.com> wrote:

Thiebaud:

Thank you. I have started discussions within Intel for updating the UEFI CPython implementation to Python 3.x. The TianoCore community would appreciate contributions by people with Python experience to bring this code up to current standards. Please review the contribution guidelines for TianoCore and let me know if you have any questions. http://www.tianocore.org/contrib/ Thanks ... br --- Brian Richardson, Senior Technical Marketing Engineer, Intel Software brian.richardson at intel.com -- @intelbrian (Twitter & WeChat) https://software.intel.com/en-us/meet-the-developers/evangel ists/team/brian-richardson -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces at lists.01.org] On Behalf Of Thiebaud Weksteen Sent: Wednesday, November 1, 2017 5:07 AM To: python-dev at python.org Cc: edk2-devel at lists.01.org Subject: [edk2] Official port of Python on EDK2 Hi, UEFI has become the standard for firmware (BIOS) interface. Intel has provided an open source implementation under the name EDK2 (part of the TianoCore initiative) [1] for some time. This implementation has evolved significantly and now provides the functionalities of a small OS with a standard library similar to POSIX. In 2011, a port of Python 2.7.1 was added to the EDK2 repository [2]. This port then evolved to 2.7.2 which is still defined as the reference port [3]. In 2015, another port was added of Python 2.7.10 in parallel of 2.7.2 [4]. Since then, both implementations have diverged from upstream and know vulnerabilities have not been fixed. I would like to bring support for edk2 in the official Python repository to remediate this situation, that is officially support edk2 as a platform. Technically, there would be three main aspects for the on-boarding work: 1) Fix headers and source to resolve definition conflicts, similarly to ABS definition in [5]; 2) Add the edk2module.c [6] to handle platform-specific functionalities, similarly to the posixmodule.c; 3) Add the build configuration file [7] and necessary modifications within Python to handle the edk2 toolchain; This work would target the master branch (that is Python 3). I would be interested in hearing your thoughts on this idea. Thanks, Thiebaud [1] https://github.com/tianocore/edk2 [2] https://github.com/tianocore/edk2/commit/006fecd5a177b4b7b6b 36fab6690bf2b2fa11829 [3] https://github.com/tianocore/edk2/blob/master/AppPkg/Applica tions/Python/PythonReadMe.txt [4] https://github.com/tianocore/edk2/commit/c8042e10763bca064df 257547d04ae3dfcdfaf91 [5] https://gist.github.com/tweksteen/ed516ca7ab7dfa8d18428f59d9c22a3e [6] https://github.com/tianocore/edk2/blob/master/AppPkg/Applica tions/Python/Efi/edk2module.c [7] https://github.com/tianocore/edk2/blob/master/AppPkg/Applica tions/Python/PythonCore.inf

edk2-devel mailing list edk2-devel at lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20171102/de3002b8/attachment.html>

More information about the Python-Dev mailing list