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 Yogesh.Chaudhari
Recipients Ankur.Ankan, Arfrever, Yogesh.Chaudhari, asvetlov, eric.smith, flox, krinart, python-dev, terry.reedy
Date 2013-05-12.17:06:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
when you say: "If the type of the object really is "object", then it can use string formatting. It's only for non-objects that I want to add the error.". 

I am confused. Let me demonstrate what I'm thinking according to the statement above. 

First let us take a 'non-object':
>>> integer=1
>>> type(integer) != object
As of now it returns the following:
>>> integer.__format__(s)
Which seems natural.
But after this patch should it return an error

Also now consider an object:
>>> f = object()
>>> type(f)
<class 'object'>
This will return the following after the patch as it does now which is:
>>> f.__format__('')
'<object object at 0xb75b7b48>'

Does this mean that 'integer' should give an error, however, 'f' should give something that appears messy?

I may be mistaken in my interpretation of the statement, so kindly let me know if there is something else that I am not clearly understanding.
Date User Action Args
2013-05-12 17:06:33Yogesh.Chaudharisetrecipients: + Yogesh.Chaudhari, terry.reedy, eric.smith, Arfrever, asvetlov, flox, python-dev, krinart, Ankur.Ankan
2013-05-12 17:06:33Yogesh.Chaudharisetmessageid: <>
2013-05-12 17:06:33Yogesh.Chaudharilinkissue9856 messages
2013-05-12 17:06:33Yogesh.Chaudharicreate