Mainly for storage size, especially for embedded devices. Installation time is small factor. Normally we just want one type of .pyc files. Getting all types installed at default looks burden to distributors. In some cases we even don't want any .pyc files at all. For example, if we copy the installed .py and .pyc file from one file system to another one (say from NTFS to FAT), probably the mtime of .py file could be changed due to the resolution limit of FAT file system. Thanks, Peixing -----Original Message----- From: Antoine Pitrou Sent: Wednesday, May 12, 2021 5:36 PM To: python-dev@python.org Subject: [Python-Dev] Re: Necessary or not for enhancement of issue44097: “add configure option to control the groups of .pyc files to install” [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Peixing, On Wed, 12 May 2021 09:27:46 +0000 "Xin, Peixing" wrote:

I created issue44097 for build enhancement: “add configure option to control the groups of .pyc files to install” and PR 23920 for the solution. From the only a few of comments I’ve got, someone thinks this enhancement makes sense. However, someone expressed opposition to this. So what is your opinion on this PR? Necessary or not? I want to hear more views on this. Thanks.

If it's only a matter of storage size, you can easily delete the unwanted files. Is there another concern? Regards Antoine. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@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/G3FGJZ3P... Code of Conduct: http://python.org/psf/codeofconduct/