This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients Dennis Sweeney, mark.dickinson, serhiy.storchaka, steven.daprano, terry.reedy
Date 2022-01-17.09:31:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As Steven have noted the compiler-time optimization is not applicable here because name frozenset is resolved at run-time.

In these cases where a set of constants can be replaced with a frozenset of constants (in "x in {1,2,3}" and in "for x in {1,2,3}") the compiler does it.

And I don't think there is an issue which is worth changing the language. Creating a frozenset of constants is pretty rare, and it is even more rare in tight loops. The most common cases (which are pretty rare anyway) are already covered.
Date User Action Args
2022-01-17 09:31:36serhiy.storchakasetrecipients: + serhiy.storchaka, terry.reedy, mark.dickinson, steven.daprano, Dennis Sweeney
2022-01-17 09:31:36serhiy.storchakasetmessageid: <>
2022-01-17 09:31:36serhiy.storchakalinkissue46393 messages
2022-01-17 09:31:35serhiy.storchakacreate