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 rhettinger
Recipients ezio.melotti, rhettinger, serhiy.storchaka, terry.reedy
Date 2014-11-09.20:37:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1415565449.39.0.917267073538.issue22823@psf.upfronthosting.co.za>
In-reply-to
Content
> The same timing for frozenset((1,2,3)) (.29) is faster than the best
> timing for frozenset({1,2,3}), (.36),

I don't see the tuple form used anywhere in the code.
The timing is a bit quicker for the tuple form because the peephole optimizer constant folds the tuple (use dis to see this).


> so I will not change that 
> unless discussed and agreed on.

Maybe, I should just make the patch.  It's becoming harder to talk about than to just fix.
History
Date User Action Args
2014-11-09 20:37:29rhettingersetrecipients: + rhettinger, terry.reedy, ezio.melotti, serhiy.storchaka
2014-11-09 20:37:29rhettingersetmessageid: <1415565449.39.0.917267073538.issue22823@psf.upfronthosting.co.za>
2014-11-09 20:37:29rhettingerlinkissue22823 messages
2014-11-09 20:37:29rhettingercreate