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 | belopolsky |
|---|---|
| Recipients | belopolsky, rhettinger |
| Date | 2008年02月27日.13:29:53 |
| SpamBayes Score | 0.35701072 |
| Marked as misclassified | No |
| Message-id | <1204118995.79.0.0868784215009.issue2197@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I did not think of the insertion after creation change of semantics. Do I understand that this is important when keys have custom comparison/hash methods with side-effects. If it is important for the language to guarantee the create/insert order in building dict literals, it would be unfortunate if that order were specified differently for dict and set literals. I will think some more about the stack issue. There is a valid argument that large dict literals will be more common than large set literals, so the stack issue is more important for dicts. BTW, what is the status of making set literal a frozen set proposal? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年02月27日 13:29:56 | belopolsky | set | spambayes_score: 0.357011 -> 0.35701072 recipients: + belopolsky, rhettinger |
| 2008年02月27日 13:29:55 | belopolsky | set | spambayes_score: 0.357011 -> 0.357011 messageid: <1204118995.79.0.0868784215009.issue2197@psf.upfronthosting.co.za> |
| 2008年02月27日 13:29:54 | belopolsky | link | issue2197 messages |
| 2008年02月27日 13:29:53 | belopolsky | create | |