Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #26307 > unrolled thread

Re: profiling and optimizing

Started byPeter Otten <__peter__@web.de>
First post2012-07-31 15:23 +0200
Last post2012-07-31 15:23 +0200
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: profiling and optimizing Peter Otten <__peter__@web.de> - 2012-07-31 15:23 +0200

#26307 — Re: profiling and optimizing

FromPeter Otten <__peter__@web.de>
Date2012-07-31 15:23 +0200
SubjectRe: profiling and optimizing
Message-ID<mailman.2777.1343741027.4697.python-list@python.org>
Rita wrote:

> I recently inherented a large python process and everything is lovely. As
> a learning experience I would like to optimize the code so I ran it thru
> the profiler
> 
> python -m cProfile myscript.py
> 
> It seems majority of the time is taking in the deep copy but that seems to
> come from a function (or functions) in the code. Is there a way to
> optimize that? perhaps have a C implementation of the deep copy? Would
> that be feasible?

To give what the other respondents said a different angle: if you replace 
the deep with a shallow copy: do your unit tests start to fail? 

You don't have any? Add them before you start tinkering with the code ;)

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web