1. 08 Eki, 2014 1 kayıt (commit)
  2. 07 Kas, 2013 1 kayıt (commit)
  3. 06 Kas, 2013 1 kayıt (commit)
  4. 23 Eki, 2013 1 kayıt (commit)
  5. 01 Agu, 2013 1 kayıt (commit)
    • Victor Stinner's avatar
      Issue #18609, #18408: _ctypes_add_traceback() now clears the current exception · 044c5168
      Victor Stinner yazdı
      while adding the traceback, because it may call indirectly a Python function
      and Python functions must not be called with an exception set.
      
      In the case of the issue #18609, _ctypes_add_traceback() called the iso8859-1
      decoder which is implemented in Python. Python has a ISO-8859-1 codec
      implemented in C. It is not used because PyUnicode_Decode() only uses the C
      codec for other names (aliases) of this codec ("latin-1", "latin1" and
      "iso-8859-1").
      044c5168
  6. 12 Eyl, 2011 2 kayıt (commit)
  7. 16 Mar, 2011 2 kayıt (commit)
  8. 16 Eyl, 2010 1 kayıt (commit)
  9. 05 Eyl, 2010 1 kayıt (commit)
  10. 10 Agu, 2010 1 kayıt (commit)
  11. 08 Agu, 2010 3 kayıt (commit)
  12. 09 May, 2010 4 kayıt (commit)
  13. 30 Mar, 2010 2 kayıt (commit)
    • Thomas Heller's avatar
      b102ddad
    • Thomas Heller's avatar
      Merged revisions 79115,79424,79491 via svnmerge from · 5006ba0f
      Thomas Heller yazdı
      svn+ssh://pythondev@svn.python.org/python/branches/branch_libffi-3_0_10-win
      
      ........
        r79115 | thomas.heller | 2010-03-19 22:14:47 +0100 (Fr, 19 Mrz 2010) | 7 lines
      
        Work in progress.  2 tests fail on x86/win32 because the stack
        checking code in ffi_call_win32 is not yet implemented.
      
        Remove most files from _ctypes/libffi_msvc, only two include files
        stay (updated from _ctypes/libffi/...).  Other files are used in the
        cross-platform _ctypes/libffi directory.
      ........
        r79424 | thomas.heller | 2010-03-25 19:28:02 +0100 (Do, 25 Mrz 2010) | 1 line
      
        Build _ctypes on Win64.
      ........
        r79491 | thomas.heller | 2010-03-29 21:30:33 +0200 (Mo, 29 Mrz 2010) | 4 lines
      
        On Windows, ctypes does no longer check the stack before and after
        calling a foreign function.
        This allows to use the unmodified libffi library.
      ........
      5006ba0f
  14. 23 Şub, 2010 4 kayıt (commit)
  15. 08 Eyl, 2009 1 kayıt (commit)
  16. 21 Tem, 2009 1 kayıt (commit)
    • Alexandre Vassalotti's avatar
      Merged revisions 72487-72488,72879 via svnmerge from · 7b82b40a
      Alexandre Vassalotti yazdı
      svn+ssh://pythondev@svn.python.org/python/trunk
      
      ........
        r72487 | jeffrey.yasskin | 2009-05-08 17:51:06 -0400 (Fri, 08 May 2009) | 7 lines
      
        PyCode_NewEmpty:
        Most uses of PyCode_New found by http://www.google.com/codesearch?q=PyCode_New
        are trying to build an empty code object, usually to put it in a dummy frame
        object. This patch adds a PyCode_NewEmpty wrapper which lets the user specify
        just the filename, function name, and first line number, instead of also
        requiring lots of code internals.
      ........
        r72488 | jeffrey.yasskin | 2009-05-08 18:23:21 -0400 (Fri, 08 May 2009) | 13 lines
      
        Issue 5954, PyFrame_GetLineNumber:
        Most uses of PyCode_Addr2Line
        (http://www.google.com/codesearch?q=PyCode_Addr2Line) are just trying to get
        the line number of a specified frame, but there's no way to do that directly.
        Forcing people to go through the code object makes them know more about the
        guts of the interpreter than they should need.
      
        The remaining uses of PyCode_Addr2Line seem to be getting the line from a
        traceback (for example,
        http://www.google.com/codesearch/p?hl=en#u_9_nDrchrw/pygame-1.7.1release/src/base.c&q=PyCode_Addr2Line),
        which is replaced by the tb_lineno field.  So we may be able to deprecate
        PyCode_Addr2Line entirely for external use.
      ........
        r72879 | jeffrey.yasskin | 2009-05-23 19:23:01 -0400 (Sat, 23 May 2009) | 14 lines
      
        Issue #6042:
        lnotab-based tracing is very complicated and isn't documented very well.  There
        were at least 3 comment blocks purporting to document co_lnotab, and none did a
        very good job. This patch unifies them into Objects/lnotab_notes.txt which
        tries to completely capture the current state of affairs.
      
        I also discovered that we've attached 2 layers of patches to the basic tracing
        scheme. The first layer avoids jumping to instructions that don't start a line,
        to avoid problems in if statements and while loops.  The second layer
        discovered that jumps backward do need to trace at instructions that don't
        start a line, so it added extra lnotab entries for 'while' and 'for' loops, and
        added a special case for backward jumps within the same line. I replaced these
        patches by just treating forward and backward jumps differently.
      ........
      7b82b40a
  17. 08 May, 2009 1 kayıt (commit)
    • Jeffrey Yasskin's avatar
      PyCode_NewEmpty: · 1aa47002
      Jeffrey Yasskin yazdı
      Most uses of PyCode_New found by http://www.google.com/codesearch?q=PyCode_New
      are trying to build an empty code object, usually to put it in a dummy frame
      object. This patch adds a PyCode_NewEmpty wrapper which lets the user specify
      just the filename, function name, and first line number, instead of also
      requiring lots of code internals.
      1aa47002
  18. 24 Nis, 2009 2 kayıt (commit)
  19. 16 Nis, 2009 3 kayıt (commit)
  20. 02 Şub, 2009 1 kayıt (commit)
  21. 09 Haz, 2008 1 kayıt (commit)
  22. 06 Haz, 2008 2 kayıt (commit)
    • Thomas Heller's avatar
      Merged revisions 63977 via svnmerge from · 9cac7b61
      Thomas Heller yazdı
      svn+ssh://pythondev@svn.python.org/python/trunk
      
      ........
        r63977 | thomas.heller | 2008-06-06 10:33:46 +0200 (Fri, 06 Jun 2008) | 31 lines
      
        Issue #1798: Add ctypes calling convention that allows safe access of errno.
      
        ctypes maintains thread-local storage that has space for two error
        numbers: private copies of the system 'errno' value and, on Windows,
        the system error code accessed by the GetLastError() and
        SetLastError() api functions.
      
        Foreign functions created with CDLL(..., use_errno=True), when called,
        swap the system 'errno' value with the private copy just before the
        actual function call, and swapped again immediately afterwards.  The
        'use_errno' parameter defaults to False, in this case 'ctypes_errno'
        is not touched.
      
        On Windows, foreign functions created with CDLL(...,
        use_last_error=True) or WinDLL(..., use_last_error=True) swap the
        system LastError value with the ctypes private copy.
      
        The values are also swapped immeditately before and after ctypes
        callback functions are called, if the callbacks are constructed using
        the new optional use_errno parameter set to True: CFUNCTYPE(...,
        use_errno=TRUE) or WINFUNCTYPE(..., use_errno=True).
      
        New ctypes functions are provided to access the ctypes private copies
        from Python:
      
        - ctypes.set_errno(value) and ctypes.set_last_error(value) store
          'value' in the private copy and returns the previous value.
      
        - ctypes.get_errno() and ctypes.get_last_error() returns the current
          ctypes private copies value.
      ........
      9cac7b61
    • Thomas Heller's avatar
      Issue #1798: Add ctypes calling convention that allows safe access of errno. · fbb9c0bf
      Thomas Heller yazdı
      ctypes maintains thread-local storage that has space for two error
      numbers: private copies of the system 'errno' value and, on Windows,
      the system error code accessed by the GetLastError() and
      SetLastError() api functions.
      
      Foreign functions created with CDLL(..., use_errno=True), when called,
      swap the system 'errno' value with the private copy just before the
      actual function call, and swapped again immediately afterwards.  The
      'use_errno' parameter defaults to False, in this case 'ctypes_errno'
      is not touched.
      
      On Windows, foreign functions created with CDLL(...,
      use_last_error=True) or WinDLL(..., use_last_error=True) swap the
      system LastError value with the ctypes private copy.
      
      The values are also swapped immeditately before and after ctypes
      callback functions are called, if the callbacks are constructed using
      the new optional use_errno parameter set to True: CFUNCTYPE(...,
      use_errno=TRUE) or WINFUNCTYPE(..., use_errno=True).
      
      New ctypes functions are provided to access the ctypes private copies
      from Python:
      
      - ctypes.set_errno(value) and ctypes.set_last_error(value) store
        'value' in the private copy and returns the previous value.
      
      - ctypes.get_errno() and ctypes.get_last_error() returns the current
        ctypes private copies value.
      fbb9c0bf
  23. 04 Haz, 2008 2 kayıt (commit)
    • Thomas Heller's avatar
      Revert revisions 63943 and 63942 (Issue #1798: Add ctypes calling · d5bb9215
      Thomas Heller yazdı
      convention that allows safe access to errno)
      
      This code does not yet work on OS X (__thread storage specifier not
      available), so i needs a configure check plus a more portable
      solution.
      d5bb9215
    • Thomas Heller's avatar
      Issue #1798: Add ctypes calling convention that allows safe access to · e70c3378
      Thomas Heller yazdı
      errno (and LastError, on Windows).
      
      ctypes maintains a module-global, but thread-local, variable that
      contains an error number; called 'ctypes_errno' for this discussion.
      This variable is a private copy of the systems 'errno' value; the copy
      is swapped with the 'errno' variable on several occasions.
      
      Foreign functions created with CDLL(..., use_errno=True), when called,
      swap the values just before the actual function call, and swapped
      again immediately afterwards.  The 'use_errno' parameter defaults to
      False, in this case 'ctypes_errno' is not touched.
      
      The values are also swapped immeditately before and after ctypes
      callback functions are called, if the callbacks are constructed using
      the new optional use_errno parameter set to True: CFUNCTYPE(..., use_errno=TRUE)
      or WINFUNCTYPE(..., use_errno=True).
      
      Two new ctypes functions are provided to access the 'ctypes_errno'
      value from Python:
      
      - ctypes.set_errno(value) sets ctypes_errno to 'value', the previous
        ctypes_errno value is returned.
      
      - ctypes.get_errno() returns the current ctypes_errno value.
      
      ---
      
      On Windows, the same scheme is implemented for the error value which
      is managed by the GetLastError() and SetLastError() windows api calls.
      
      The ctypes functions are 'ctypes.set_last_error(value)' and
      'ctypes.get_last_error()', the CDLL and WinDLL optional parameter is
      named 'use_last_error', defaults to False.
      
      ---
      
      On Windows, TlsSetValue and TlsGetValue calls are used to provide
      thread local storage for the variables; ctypes compiled with __GNUC__
      uses __thread variables.
      e70c3378
  24. 26 May, 2008 1 kayıt (commit)