Mailman 3 June 2013 - Python-ideas

Re: [Python-ideas] Timing hefty or long-running blocks of code
by Clay Sweetser 03 Jun '13

03 Jun '13

I quite like this proposal. To me, the main advantage of such a context manager/decorator over the current timeit module is that it can be used for pieces of code that either can't or shouldn't be arbitrarily repeated. For example, I am currently writing a plugin for the sublime text editor, and it would be very convenient for me to be able to get a quick summery of timing statistics for functions that make use of the editor's plugin api to modify documents. My only suggestion for the proposed function is to allow the output of statistics similar to the ones the timeit module allows, such as the mean runtime of a block of code. Sincerely, Clay Sweetser

4 5

ThreadPool worker function
by Luca Sbardella 03 Jun '13

03 Jun '13

While using the ThreadPool in the multiprocessing.pool module, I needed to use a different implementation for the *worker* function. Since there is no way to overwrite it directly, I'm overwriting the Process attribute with a method: def myworker(...): ... class ThreadPool(pool.ThreadPool): def Process(self, target=None, **kwargs): return Thread(target=myworker, **kwargs) which is good enough, works for 2.6 and up. On the other hand, *worker* could be defined as a class attribute in the same way as the Process. Something like this: def default_worker(...): ... class Pool(object): Process = Process worker = default_worker ... Less verbose and less of a hack IMO.

1 0

Loaded questions
by Guido van Rossum 02 Jun '13

02 Jun '13

On Sun, Jun 2, 2013 at 7:11 PM, Daniel Holth <dholth(a)gmail.com> wrote: > When will the stdlib get a decent iterator/stream-based JSON API? As a reminder, a loaded question is not a good way to suggest a new feature. If you want a feature, great. If you don't feel you have the skills to implement it, you can still play*. But if you want a feature, please say something like "I think it would be cool if the stdlib had X" and we can discuss whether we all feel the same way. To most people, "when will the stdlib get a decent X" reads as either implying "the stdlib has a lousy X" or "the stdlib is stupid (or whatever negative adjective) for not having X." And many of the folks here who together have made the stdlib what it is and never missed X will feel offended. Do you think it is a good thing to start a request by offending the person you are asking? (Don't answer. :-) It's possible you didn't mean this at all. Likely, even. So next time, think about how the words you use might be interpreted by others, and leave your loaded questions at home. Please. :-) __________ * Though if nobody can be found who wants a feature badly enough to implement it, it won't happen, and you shouldn't complain about it -- we're all volunteers here, and nobody has enough time to implement every desirable feature. -- --Guido van Rossum (python.org/~guido)

1 0