Skip to content
Commits on Jun 30, 2013
  1. @aclark4life

    Cleanup WS, courtesy of @Arfrever

    aclark4life committed
    find * -type f "-(" -name "*.bdf" -o -name "*.c" -o -name "*.h" -o -name "*.py" -o -name "*.rst" -o -name "*.txt" "-)" -exec sed -e "s/[[:space:]]*$//" -i {} \;
Commits on Apr 12, 2013
  1. @wiredfool
Commits on Mar 8, 2013
  1. @aclark4life

    Merge pull request #81 from cgohlke/patch-2

    aclark4life committed
    64 bit proof alloc_array
  2. @cgohlke
  3. @cgohlke

    64 bit proof path_getattr_id

    cgohlke committed
  4. @cgohlke

    64 bit proof alloc_array

    cgohlke committed
Commits on Jan 10, 2013
  1. @fluggo

    py3k: Remove ancient Python hacks

    fluggo committed with Brian Crowell
  2. @cgohlke

    py3k: Allow slicing for paths

    cgohlke committed with Brian Crowell
    This is Gohlke's fix for two issues: negative indexes on paths were not
    resolved to the correct index, and path slicing didn't work.
    His fix for slicing is related to the one found at:
    With this commit, all 79 tests (82 minus the three skipped ones) run
    successfully on Python 2.6.8, Python 2.7.3rc2, and Python 3.2.3.
  3. @fluggo

    py3k: Add module initialization and unicode/bytes int/long thunks

    fluggo committed with Brian Crowell
    This commit:
    * Adds Python 3 module initialization functions. I split out the main init
      of each module into a static setup_module function.
    * Adds a py3.h which unifies int/long in Python 3 and unicode/bytes in
      Python 2. _imagingft.c unfortunately looks a little kludgy after this
      because it was already using PyUnicode functions, and I had to mix and
      match there manually.
    With this commit, the modules all build successfully under Python 3.
    What this commit does NOT do is patch all of the uses of PyArg_ParseTuple
    and Py_BuildValue, which all need to be checked for proper use of bytes
    and unicode codes. It also does not let run yet, because there
    are probably hundreds of issues to fix in the Python code itself.
  4. @fluggo

    py3k: Use new buffer protocol

    fluggo committed with Brian Crowell
    Other ports have taken advantage of the fact that Python 3 has wrappers for
    the old buffer protocol, but there's a significant disadvantage: you can't
    let the buffered object know when you're done with it.
    Since Python 2.6 supports the new protocol, we just go ahead and move to
  5. @fluggo

    py3k: Modernize type declarations

    fluggo committed with Brian Crowell
    This updates several Python type definitions and uses to bring us closer
    to Python 3 compatibility. This includes:
    * Replacing staticforward and statichere with static. These were a hack for
      old compilers and are not supported/needed anymore.
    * Using Py_TYPE() instead of ob_type; ob_type is hidden in Py3.
    * Replacing getattr with getters/setters. getattr is sort-of supported in
      Py3, but Py_FindMethod is not. So we just use the newer
      methods/getsetters mechanisms and start using PyType_Ready everywhere.
    * Use PyVarObject_HEAD_INIT for types, since types are PyVarObject.
    * Use PyMODINIT_FUNC for module initialization functions.
    There are some tab/space issues in this commit. I'm set for spaces; the
    source is a little schizo.
Commits on Jul 31, 2010
  1. @aclark4life

    Forking PIL

    aclark4life committed
Something went wrong with that request. Please try again.