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 arigo
Recipients arigo, brett.cannon, docs@python, fijall, loewis, lukasz.langa, pitrou
Date 2011-02-04.16:22:12
SpamBayes Score 3.51708e-10
Marked as misclassified No
Message-id <>
Martin: I kind of agree with you, although I guess that for pratical reasons if you don't have a reasonable sys.getsizeof() implementation then it's better to raise TypeError than return 0 (like CPython, which may raise "TypeError: Type %.100s doesn't define __sizeof__").

I agree that it's not really useful to mark functions as CPython-specific in the documentation, if only because whenever a new implementation like PyPy comes along, then it's going to have a rather different set of functions that it wants to consider implementation details.  I would say that more than half the functions in the sys module marked CPython-specific in the doc are implemented in PyPy just fine, and there is an equal number of functions not marked CPython-specific that have no chance to be implemented in PyPy.
Date User Action Args
2011-02-04 16:22:14arigosetrecipients: + arigo, loewis, brett.cannon, pitrou, docs@python, lukasz.langa, fijall
2011-02-04 16:22:14arigosetmessageid: <>
2011-02-04 16:22:12arigolinkissue10994 messages
2011-02-04 16:22:12arigocreate