Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tag: r0.6.0
Commits on Apr 17, 2012
  1. raineszm

    Updated manifest.

    raineszm authored
  2. raineszm
Commits on Mar 31, 2012
  1. raineszm
Commits on Nov 27, 2011
  1. Made RubyPython.start work better on failure.

    authored
    Fixed Ruby 1.8 compatibility.
Commits on Nov 23, 2011
  1. Refactored the load of the Python DLL through FFI.

    authored
    No more hinky require/load hacks; now it's all module_eval hacks.
    
    --HG--
    rename : lib/rubypython/pythonexec.rb => lib/rubypython/interpreter.rb
  2. Deprecating RubyPython.legacy_mode.

    authored
    Legacy mode is not useful in the general case (at least compared to the
    continued ability to call Python methods against objects). Providing
    deprecation warnings on the setting of legacy mode (will happen once per Ruby
    interpreter).
Commits on Nov 15, 2011
  1. Merge of git and mercurial histories because of a previously broken h…

    authored
    …g-git setup for the 0.5.3 tree.
Commits on Oct 23, 2011
  1. Starting work on 0.6.0. Adding RubyPython::Tuple.

    Austin Ziegler authored
    To simplify cases where actual Python tuples are required, adding a
    class (a subclass of ::Array) to allow for explicit conversion to tuple
    objects.
    
    The semantics are best handled with the class method
    RubyPython::Tuple.tuple(), which makes a #dup of the Array parameter.
    This matches the result of the tuple() method in Python.
  2. Adding RubyPython::Tuple.

    authored
    To simplify cases where actual Python tuples are required, adding a
    class (a subclass of ::Array) to allow for explicit conversion to tuple
    objects.
    
    The semantics are best handled with the class method
    RubyPython::Tuple.tuple(), which makes a #dup of the Array parameter.
    This matches the result of the tuple() method in Python.
  3. Properly reflecting RubyPython 0.5.3.

    Austin Ziegler authored
  4. tagging r0.5.3 for release

    authored
Commits on Oct 21, 2011
  1. Post 0.5.2 items found.

    Austin Ziegler authored
  2. tagging r0.5.2 for release

    authored
  3. Real release version is 0.5.2.

    Austin Ziegler authored
  4. Multiple commits for 0.5.1 release.

    Austin Ziegler authored
    1. Merged from Zach's Hg master on Bitbucket.
       a. b9743fe24e61: Added traceback to PythonError.
       b. 9db92195bad8: Use :python_exe instead of :python. Bugfix.
       c. 719d8f8bf44c: Fix the documentation about :python_exe.
       d. 9c0d3dce2a06: First pass Windows support improvements.
       e. d25def6cf56b: Documentation on PythonError#traceback.
    2. Improved the Windows support.
  5. Final preparation for the 0.5.1 bugfix release.

    authored
    Noted that Zach also made the Python traceback available.
  6. Making Windows DLL detection more robust.

    authored
    Both Ben Doerr and Zach had fixes for this. Zach's is the one that this
    is based on with a bit more added robustness (using %SYSTEMROOT% prior
    to using C:\Windows as a fallback). Ben's additional locations have been
    added. yak^ on irc:irc.freenode.net/#python suggests using sys.dllhandle
    with ctypes, thus:
    
      import sys
      from ctypes import *
    
      name = create_string_buffer(256)
      windll.kernel32.GetModuleFileNameA(sys.dllhandle, name, 256)
      print name.value
    
    It returns C:\Windows\System32\python27.dll on his system.
Commits on Aug 21, 2011
  1. raineszm

    Changed a few things in the PythonExec module to hopefully allow ruby…

    raineszm authored
    …python find the correct DLL on Windows.
Commits on May 29, 2011
  1. raineszm
  2. raineszm
  3. raineszm

    Small bugfix to the start_from_virtualenv method. The :python_exe opt…

    raineszm authored
    …ion is now used instad of :python
  4. raineszm
Commits on Mar 18, 2011
  1. tagging r0.5.0 for release

    authored
  2. Ignoring pkg/*

    authored
  3. Prepping for release.

    authored
Commits on Mar 17, 2011
  1. Documentation improvements:

    authored
    * The following modules have been excluded from documentation as they are
      implementation details and not important to end users. The documentation
      comments may have been improved, but that's because I believe we still need
      good documentation to maintain the project.
      * BlankObject
      * Macros
      * PyObject (and any contained classes like AutoPyPointer)
      * Python (and any contained classes like DummyStruct)
    * The Conversion module is currently visible to end users, but it may not be
      ideal for this to be the case both because of the naming and the fact that
      everything is returned in terms of pointers.
    * Documented legacy mode. I've documented it as to be phased out in v1.0; I'd
      like to make moves toward that next release (start having it print warnings).
    * Removed reference to :python_lib from the options documentation as it's not
      used in the current load scheme. I don't think it'd be that hard, but it will
      require a bit of extra work.
    * Attempted to document pygenerator.rb; I don't like this file (it doesn't
      define a new class, but new methods on the RubyPython module), and there are
      parts of it that seem a little "smelly" (is there really only one instance
      ever of #generator_type?). This should be refactored for the next version.
    * Improved the documentation of PyMainClass to be more useful to the end user.
    * Documented PythonExec even though it's primarily an internal class, because I
      added a method (RubyPython.python) that will return this object.
    * Substantially changed the RubyPyProxy documentation.
    * Made RubyPyProxy#_wrap private (there's no reason, *ever*, that a user should
      call it.)
    * Added block handling to RubyPyProxy#method_missing as had been documented in
      the class.
    * Attempted to document the RubyPython.Type method. I'm not sure this is doing
      what I say it's doing, and there's no specs for it. Will need to add.
Something went wrong with that request. Please try again.