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 ncoghlan
Recipients Ben.Wolfson, barry, belopolsky, eric.araujo, eric.smith, flox, mark.dickinson, ncoghlan, petri.lehtinen, r.david.murray, rhettinger
Date 2013-02-18.14:39:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361198344.09.0.735278539958.issue12014@psf.upfronthosting.co.za>
In-reply-to
Content
This actually came up on the core-mentorship list (someone was trying to translate old mod-formatting code that used a colon in the lookup names and discovered this odd behaviour)

My own preference is to let this quote from PEP 3101 dominate the behaviour: "The rules for parsing an item key are very simple. If it starts with a digit, then it is treated as a number, otherwise it is used as a string."

That means Petri's suggested solution (allowing any character except a closing square bracket and braces in the item key) sounds good to me.
History
Date User Action Args
2013-02-18 14:39:04ncoghlansetrecipients: + ncoghlan, barry, rhettinger, mark.dickinson, belopolsky, eric.smith, eric.araujo, r.david.murray, flox, Ben.Wolfson, petri.lehtinen
2013-02-18 14:39:04ncoghlansetmessageid: <1361198344.09.0.735278539958.issue12014@psf.upfronthosting.co.za>
2013-02-18 14:39:04ncoghlanlinkissue12014 messages
2013-02-18 14:39:03ncoghlancreate