Donghee Na

I have made the requested changes; please review again

@ronaldoussoren @vstinner @ericsnowcurrently As the first step for the subinterpreter project, I would like to suggest maintaining restrictions for subinterpreter as the current PR. If there are requests which require...

@loongson-zn I will take a look, but it may takes some times to review from the view of supporting this platform is proper. Please keep patient

Sorry for the late response: Please consider that you can meet the requirement of [PEP-11](https://peps.python.org/pep-0011/) At least for tier 3, you would need at least one core dev and a...

> Thanks，this is [debian documentation](https://wiki.debian.org/Multiarch/Tuples) about LoongArch, we need cpython support LoongArch. My suggestion is, how about sending a downstream patch to Debian first?

> [PEP-11](https://peps.python.org/11) is for platforms, not architectures? 1. Who will maintain the loongarch64-unknown-linux-gnu ? 2. How can we verify the code for loongarch64-unknown-linux-gnu ? I am sure that such requirements...

And we requested similar requirements to Windriver team too : https://mail.python.org/pipermail/python-dev/2019-January/156031.html

@erlend-aasland cc @loongson-zn But on the other hand, if this is the only patch that they will need, I am okay to accept the patch anyway.

> Aside from the Loongson teams, there is [an active community around LoongArch](https://bbs.loongarch.org/) (also [Telegram user group](https://t.me/loongson_users)) with multiple porters and power users willing to help. I'm heavily involved in...

> @corona10 Currently, this is the only one patch. Because it affects binary compatibility, I believe it is necessary to merge as soon as possible. Okay, let's pass the CI...