A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/attachments/20140608/7fde3b51/attachment.html below:

<p dir="ltr"><br>
On 8 Jun 2014 05:44, "Glenn Linderman" <<a href="mailto:v%2Bpython@g.nevcal.com">v+python@g.nevcal.com</a>> wrote:<br>
><br>
> I wonder if the dynamically constructed classes approach could lead to the same space and time efficiencies... seems like I recall there being a discussion of efficiency, I think primarily space efficiency, as a justification for the present implementation. namedtuple predates of the improvements in metaclasses, also, which may be a justification for the present implementation.</p>

<p dir="ltr">As far as I am aware, there's nothing magical in the classes namedtuple creates that would require a custom metaclass - it's just that what it does would likely be even harder to read if written out explicitly rather than letting the compiler & eval loop deal with it.</p>

<p dir="ltr">However, we've drifted off topic for python-dev at this point. If anyone wanted to experiment with alternative implementations, python-ideas would be the place to discuss that.</p>


<p dir="ltr">Cheers,<br>
Nick.</p>

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4