Message 256104 - 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	serhiy.storchaka
Recipients	martin.panter, rhettinger, serhiy.storchaka
Date	2015-12-08.09:08:05
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
I agree that it would be nice to have. But this feature has a cost. $ ./python -m timeit -s 'from urllib.parse import ParseResult' -- "ParseResult('http', '[email protected]:[email protected]:080', '/doc/', '', 'query=yes', 'frag')" Unpatched: 1.61 usec per loop Patched: 2.1 usec per loop $ ./python -m timeit -s 'from urllib.parse import urlparse' -- 'urlparse("http://[email protected]:[email protected]:080/doc/?query=yes#frag")' Unpatched: 8.87 usec per loop Patched: 9.22 usec per loop Is this cost significant? The cost can be decreased by using global _tuple_new = tuple.__new__. But this couples the code too tight to implementation details of namedtuple.

I agree that it would be nice to have. But this feature has a cost.

$ ./python -m timeit -s 'from urllib.parse import ParseResult' -- "ParseResult('http', '[email protected]:[email protected]:080', '/doc/', '', 'query=yes', 'frag')"
Unpatched: 1.61 usec per loop
Patched:   2.1 usec per loop

$ ./python -m timeit -s 'from urllib.parse import urlparse' -- 'urlparse("http://[email protected]:[email protected]:080/doc/?query=yes#frag")'

Unpatched: 8.87 usec per loop
Patched:   9.22 usec per loop

Is this cost significant?

The cost can be decreased by using global _tuple_new = tuple.__new__. But this couples the code too tight to implementation details of namedtuple.

History
Date	User	Action	Args
2015-12-08 09:08:06	serhiy.storchaka	set	recipients: + serhiy.storchaka, rhettinger, martin.panter
2015-12-08 09:08:05	serhiy.storchaka	set	messageid: <[email protected]>
2015-12-08 09:08:05	serhiy.storchaka	link	issue23416 messages
2015-12-08 09:08:05	serhiy.storchaka	create