Message 362810 - Python tracker

➜

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	gvanrossum
Recipients	Aaron Hall, brandtbucher, gvanrossum, josh.r, mark.dickinson, rhettinger, scoder, serhiy.storchaka, slam, steve.dower, xtreak
Date	2020-02-27.15:43:45
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAP7+vJLY8wBcMNRBBiPBR5_ZQDu5O1F68gWAaQPCS7F-9=Qv8w@mail.gmail.com>
In-reply-to	<1582787071.25.0.714591248026.issue36144@roundup.psfhosted.org>

Content
I had just come to a different conclusion. Maybe ChainMap should just not grow `\|` and `\|=` operators? That way there can be no confusion. `dict() \| ChainMap()` and `ChainMap() \| dict()` will fail because ChainMap doesn't inherit from dict. (Note that in your last message, `d1 \|= cm2` will fail for this reason. You can of course fix that with `d1 \|= dict(cm2)`, although IIUC there's no reason one of the maps couldn't be some other [Mutable]Mapping.)

I had just come to a different conclusion. Maybe ChainMap should just not
grow `|` and `|=` operators? That way there can be no confusion. `dict() |
ChainMap()` and `ChainMap() | dict()` will fail because ChainMap doesn't
inherit from dict. (Note that in your last message, `d1 |= cm2` will fail
for this reason. You can of course fix that with `d1 |= dict(cm2)`,
although IIUC there's no reason one of the maps couldn't be some other
[Mutable]Mapping.)

History
Date	User	Action	Args
2020-02-27 15:43:45	gvanrossum	set	recipients: + gvanrossum, rhettinger, mark.dickinson, scoder, serhiy.storchaka, steve.dower, josh.r, Aaron Hall, slam, xtreak, brandtbucher
2020-02-27 15:43:45	gvanrossum	link	issue36144 messages
2020-02-27 15:43:45	gvanrossum	create