1. 30 Dec, 2014 1 commit
  2. 20 Dec, 2014 2 commits
  3. 18 Dec, 2014 2 commits
  4. 16 Dec, 2014 1 commit
  5. 18 Nov, 2014 4 commits
  6. 04 Nov, 2014 3 commits
  7. 22 Sep, 2014 1 commit
  8. 22 Aug, 2014 2 commits
  9. 22 Jul, 2014 1 commit
  10. 28 Jun, 2014 2 commits
  11. 29 May, 2014 2 commits
  12. 14 Mar, 2014 2 commits
  13. 13 Nov, 2013 7 commits
  14. 12 Nov, 2013 1 commit
  15. 08 May, 2013 1 commit
  16. 27 Apr, 2013 1 commit
    • Garrett Regier's avatar
      Fix Gjs plugin loader · 8c54d0ee
      Garrett Regier authored
      The garbage collection now takes a runtime instead of a contex
      so just use Gjs's gc method to do the right thing and jsvals
      cannot be compared anymore.
  17. 14 Feb, 2013 2 commits
  18. 05 Jan, 2013 1 commit
    • Paolo Borelli's avatar
      Support py2 and py3 at the same time · 590b5e1c
      Paolo Borelli authored
      This patch reworks the build system so that we use the same sources to
      build both a python2 loader and a python3 loader. The python 2 one
      keeps the same name for backward compatibility, while the python 3 one
      is explicitely called "python3".
      Supporting py2 and py3 in the same build is tricky since the existing
      autotools support is limited, so we make some assumptions:
       - there are separate --enable-python2 and --enable-python3 flags,
         --enable-python has been removed
       - the py3 loader is in a separate dir but compliles the files from the
         py2 loader
       - for py2 we only check the binary and the python2-config tool, while
         for py3 we use the proper AM_PATH_PYTHON macro
       - for py2 we manually detect pyexecdir, hopefully with the same logic
         used by the AM_PATH_PYTHON macro
       - we do not check for Python.h header anymore since it is not strictly
         needed and autoconf caching makes it difficult
       - for we build the demos only for python3 (unit tests instead are
         replicated for both)
  19. 22 Nov, 2012 1 commit
    • Ryan Lortie's avatar
      Workaround gjs single-include issue · 2307c53e
      Ryan Lortie authored
      gjs features single-include guards for the headers in gjs/ with
      gjs/gjs-module.h being the only header you are supposed to include.
      Unfortunately, the headers in gi/ (which do not appear to have their own
      master include file) individually include files from gjs/.
      We can workaround the issue by first #include <gjs/gjs-module.h> which
      will skip the single-include guard on the files the second time they get
      included (from the headers in gi/).
  20. 12 Oct, 2012 1 commit
    • Jesse van den Kieboom's avatar
      Better SIGINT handling for python signals module · 252e2f4e
      Jesse van den Kieboom authored
      Even though PyInitialize_Ex does not initialize signal handlers,
      the python signal module does install a handler for SIGINT when
      the handler for SIGINT is set to SIG_DFL on importing the signal
      To avoid applications not handling SIGINT we set a custom SIGINT
      handler (if the current SIGINT handler is SIG_DFL) before
      initializing the python interpreter. This signal handler when
      invoked simply chains to the default SIGINT handler.
  21. 17 Jul, 2012 2 commits