>>> object(1)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: object.__new__() takes no parameters


This is misleading because object.__new__() takes one parameter:

>>> object.__new__(object)
<object object at 0x100413980>


I suggest changing "object.__new__() takes no parameters" to "object() takes no parameters".

Some other inconsistencies that I noticed:

>>> tuple.__new__(tuple, 1, 2, 3)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: tuple() takes at most 1 argument (3 given)

but

>>> list.__new__(list, 1, 2, 3)
[]

The latter is no inconsistency; tuples are immutable, lists are not.  Therefore, for lists, __init__ is the initializer, not __new__.  In order not to duplicate argument checking, __new__ does nothing special with them.

New changeset b5adf2a30b73 by R David Murray in branch '3.2':
#7963: fix error message when 'object' called with arguments.
http://hg.python.org/cpython/rev/b5adf2a30b73

New changeset 0e438442fddf by R David Murray in branch '3.3':
#7963: fix error message when 'object' called with arguments.
http://hg.python.org/cpython/rev/0e438442fddf

New changeset 1f3ce7ba410b by R David Murray in branch 'default':
Merge: #7963: fix error message when 'object' called with arguments.
http://hg.python.org/cpython/rev/1f3ce7ba410b

New changeset 0082b7bf9501 by R David Murray in branch '2.7':
#7963: fix error message when 'object' called with arguments.
http://hg.python.org/cpython/rev/0082b7bf9501

I've applied this.  Note that this makes the object.__new__ message consistent with, say, str.__new__.  That is, 'str.__new__(str, 2, 3)' results in the message "TypeError: str() argument 2 must be str, not int".  So the new object error message is consistent with that convention:  object.__new__(object, 1) now gives "TypeError: object() takes no parameters"