1. 07 May, 2007 1 kayıt (commit)
    • Guido van Rossum's avatar
      Merged revisions 55007-55179 via svnmerge from · 805365ee
      Guido van Rossum yazdı
      svn+ssh://pythondev@svn.python.org/python/branches/p3yk
      
      ........
        r55077 | guido.van.rossum | 2007-05-02 11:54:37 -0700 (Wed, 02 May 2007) | 2 lines
      
        Use the new print syntax, at least.
      ........
        r55142 | fred.drake | 2007-05-04 21:27:30 -0700 (Fri, 04 May 2007) | 1 line
      
        remove old cruftiness
      ........
        r55143 | fred.drake | 2007-05-04 21:52:16 -0700 (Fri, 04 May 2007) | 1 line
      
        make this work with the new Python
      ........
        r55162 | neal.norwitz | 2007-05-06 22:29:18 -0700 (Sun, 06 May 2007) | 1 line
      
        Get asdl code gen working with Python 2.3.  Should continue to work with 3.0
      ........
        r55164 | neal.norwitz | 2007-05-07 00:00:38 -0700 (Mon, 07 May 2007) | 1 line
      
        Verify checkins to p3yk (sic) branch go to 3000 list.
      ........
        r55166 | neal.norwitz | 2007-05-07 00:12:35 -0700 (Mon, 07 May 2007) | 1 line
      
        Fix this test so it runs again by importing warnings_test properly.
      ........
        r55167 | neal.norwitz | 2007-05-07 01:03:22 -0700 (Mon, 07 May 2007) | 8 lines
      
        So long xrange.  range() now supports values that are outside
        -sys.maxint to sys.maxint.  floats raise a TypeError.
      
        This has been sitting for a long time.  It probably has some problems and
        needs cleanup.  Objects/rangeobject.c now uses 4-space indents since
        it is almost completely new.
      ........
        r55171 | guido.van.rossum | 2007-05-07 10:21:26 -0700 (Mon, 07 May 2007) | 4 lines
      
        Fix two tests that were previously depending on significant spaces
        at the end of a line (and before that on Python 2.x print behavior
        that has no exact equivalent in 3.0).
      ........
      805365ee
  2. 09 Şub, 2007 1 kayıt (commit)
  3. 06 Eyl, 2006 1 kayıt (commit)
  4. 08 Şub, 2006 1 kayıt (commit)
    • Armin Rigo's avatar
      Added the cProfile module. · a871ef2b
      Armin Rigo yazdı
      Based on lsprof (patch #1212837) by Brett Rosen and Ted Czotter.
      With further editing by Michael Hudson and myself.
      History in svn repo: http://codespeak.net/svn/user/arigo/hack/misc/lsprof
      
      * Module/_lsprof.c is the internal C module, Lib/cProfile.py a wrapper.
      * pstats.py updated to display cProfile's caller/callee timings if available.
      * setup.py and NEWS updated.
      * documentation updates in the profiler section:
         - explain the differences between the three profilers that we have now
         - profile and cProfile can use a unified documentation, like (c)Pickle
         - mention that hotshot is "for specialized usage" now
         - removed references to the "old profiler" that no longer exists
      * test updates:
         - extended test_profile to cover delicate cases like recursion
         - added tests for the caller/callee displays
         - added test_cProfile, performing the same tests for cProfile
      * TO-DO:
         - cProfile gives a nicer name to built-in, particularly built-in methods,
           which could be backported to profile.
         - not tested on Windows recently!
      a871ef2b
  5. 20 Eki, 2005 1 kayıt (commit)
    • Jeremy Hylton's avatar
      Merge ast-branch to head · 3e0055f8
      Jeremy Hylton yazdı
      This change implements a new bytecode compiler, based on a
      transformation of the parse tree to an abstract syntax defined in
      Parser/Python.asdl.
      
      The compiler implementation is not complete, but it is in stable
      enough shape to run the entire test suite excepting two disabled
      tests.
      3e0055f8
  6. 12 Tem, 2004 1 kayıt (commit)
  7. 25 Haz, 2004 1 kayıt (commit)
  8. 24 Mar, 2004 1 kayıt (commit)
  9. 22 Mar, 2004 1 kayıt (commit)
  10. 04 Eki, 2001 1 kayıt (commit)
    • Guido van Rossum's avatar
      Hopefully fix the profiler right. Add a test suite that checks that · f137f75a
      Guido van Rossum yazdı
      it deals correctly with some anomalous cases; according to this test
      suite I've fixed it right.
      
      The anomalous cases had to do with 'exception' events: these aren't
      generated when they would be most helpful, and the profiler has to
      work hard to recover the right information.  The problems occur when C
      code (such as hasattr(), which is used as the example here) calls back
      into Python code and clears an exception raised by that Python code.
      Consider this example:
      
          def foo():
              hasattr(obj, "bar")
      
      Where obj is an instance from a class like this:
      
          class C:
              def __getattr__(self, name):
                  raise AttributeError
      
      The profiler sees the following sequence of events:
      
          call (foo)
          call (__getattr__)
          exception (in __getattr__)
          return (from foo)
      
      Previously, the profiler would assume the return event returned from
      __getattr__. An if statement checking for this condition and raising
      an exception was commented out...  This version does the right thing.
      f137f75a