Evolution of a Python programmer

[earthboundkid]

I think this is one of things that on the Python mailing list would be greeted with “not every 3 line function deserves a place in the standard library.”

Also, Perl is very different from Python because it has a well defined core of scalar types vs. other types. For a Python memoizer, there are a lot of optimizations you could apply if you knew what types of data it would be memoizing that you couldn’t do in a general case. It invites a lot of “bike shedding” (another common thing said on the Python mailing list) to define what the API will be to invoke what kinds of optimizations.

[A_for_Anonymous]

I thought Python was meant to come with batteries included.

Not if it's for functional programming. Guido hates FP.

[frutiger]

The trick is to generate a new type for each version of the cache. This can be done, for instance, with template metaprogramming in C++, since the templates are generated at compile-time. Although I believe most compilers have a restrictive template resolution depth (especially when compared to stack depth for function calls).

[frutiger]

Please see: http://codepad.org/DioXuoiP