1. 21 Oct, 2019 1 commit
  2. 30 Sep, 2019 1 commit
  3. 26 Sep, 2019 1 commit
  4. 06 Jan, 2019 1 commit
  5. 05 Mar, 2018 1 commit
  6. 07 Oct, 2017 1 commit
  7. 06 Oct, 2017 1 commit
  8. 04 Sep, 2017 1 commit
  9. 27 Jul, 2017 1 commit
    • Patrick Monnerat's avatar
      small changes for OS/400 · d1f90624
      Patrick Monnerat authored
      OS/400 version V5R3 is not supported by IBM anymore.
      In addition, the iSeries system I have here for development has been changed
      and the new system is not able to compile for an OS version lower than V6R1.
      
      Thus I made some updates to the libxml2 os400 scripts accordingly:
      
      - Oldest supported OS version is now V6R1.
      - Adjust ILE/RPG wrappers comments.
      - Update copyright year range.
      - Do not log compiler informational messages.
      d1f90624
  10. 01 Jun, 2017 1 commit
  11. 09 May, 2016 1 commit
  12. 15 Apr, 2016 1 commit
  13. 11 Mar, 2016 1 commit
  14. 20 Nov, 2015 1 commit
  15. 16 Oct, 2014 2 commits
  16. 13 Oct, 2014 1 commit
  17. 06 Oct, 2014 1 commit
    • John Beck's avatar
      python/tests/sync.py assumes Python dictionaries are ordered · 6bea543e
      John Beck authored
      For https://bugzilla.gnome.org/show_bug.cgi?id=734017
      
      Solaris has had libxml2 version 2.9.1 for a while, with Python versions 2.6 and
      2.7.  While preparing to also build a module for Python 3.4, we ran into an
      issue with the test case sync.py failing. The failure involved parsing a
      string that included a Python dictionary, then complaining when the order of
      the parsed result did not match the original order.  But Python dictionaries
      are unordered by definition; see section 5.5 of
      https://docs.python.org/2/tutorial/datastructures.html .  For whatever reason,
      Python 2.6 and 2.7 always happened to report the pair of values back in their
      original order, but with Python 3.4 the order is random.  The attached patch
      allows for either order; it also fixes a typo that was repeated several times
      thanks to the magic of copy & paste.
      6bea543e
  18. 03 Oct, 2014 1 commit
    • Ron Angeles's avatar
      Add methods for python3 iterator · b3e488b0
      Ron Angeles authored
      xmlCoreDepthFirstItertor and xmlCoreBreadthFirstItertr only
      implement a python2-compatible iterator interface. The next()
      method has been changed to __next__(). An alias has been
      defined to keep python2 compatibility.
      b3e488b0
  19. 02 Oct, 2013 1 commit
  20. 12 Jul, 2013 1 commit
  21. 11 Jul, 2013 1 commit
  22. 03 Jun, 2013 1 commit
  23. 03 May, 2013 1 commit
  24. 02 May, 2013 1 commit
  25. 19 Apr, 2013 2 commits
  26. 02 Apr, 2013 1 commit
  27. 01 Apr, 2013 1 commit
  28. 30 Mar, 2013 5 commits
  29. 27 Mar, 2013 1 commit
  30. 27 Feb, 2013 1 commit
  31. 25 Feb, 2013 2 commits
    • Alexey Neyman's avatar
      Fix a few problems with setEntityLoader · a9016c49
      Alexey Neyman authored
      1. Setting entity loader does not increment the refcount on the Python object
      passed in. This works only if the object is not deleted. For example, the
      following code results in segmentation fault in Python interpreter when
      attempting to process any document:
      
      [[[
      def register_entity_loader():
          def entity_loader(URL, ID, ctxt):
              ...
          libxml2.setEntityLoader(entity_loader
      
      register_entity_loader()
      ]]]
      
      2. setEntityLoader() does not verify if the passed object is callable. If it
      is not, current implementation attempts to call it anyway and failing that,
      silently moves on to default entity loader. Attached patch makes
      setEntityLoader raise ValueError exception if non-callable object is
      passed.
      
      3. In debug mode, pythonExternalEntityLoader() outputs the result object to
      stderr, while the messages before and after the object (description + newline)
      go to stdout. Attached patch makes them all go to stdout.
      a9016c49
    • Alexey Neyman's avatar
      Python binding for xmlRegisterInputCallback · 48da90bc
      Alexey Neyman authored
      It is possible to make xmlIO handle any protocol by means of
      xmlRegisterInputCallback(). However, that function is currently only
      available in C API. So, the natural solution seems to be implementing Python
      bindings for the xmlRegisterInputCallback.
      
      * python/generator.py: skip xmlPopInputCallbacks
      * python/libxml.c python/libxml.py python/libxml_wrap.h: implement the
        wrappers
      * python/tests/input_callback.py python/tests/Makefile.am: also add a test case
      48da90bc
  32. 21 Feb, 2013 1 commit
    • Alexey Neyman's avatar
      Python bindings: DOM casts everything to xmlNode · e32ceb93
      Alexey Neyman authored
      I noticed another issue with Python bindings of libxml: the access methods do
      not cast the pointers to specific classes such as xmlDtd, xmlEntityDecl, etc.
      For example, with the following document:
      
      <?xml version="1.0"?>
      <!DOCTYPE root [<!ELEMENT root EMPTY>]>
      <root/>
      
      the following script:
      
      import libxml2
      doc = libxml2.readFile("c.xml", None, libxml2.XML_PARSE_DTDLOAD)
      print repr(doc.children)
      
      prints:
      
      <xmlNode (root) object at 0xb74963ec>
      
      With properly cast nodes, it outputs the following:
      
      <xmlDtd (root) object at 0xb746352c>
      
      The latter object (xmlDtd) enables one to use DTD-specific methods such as
      debugDumpDTD(), copyDTD(), and so on.
      e32ceb93
  33. 11 Sep, 2012 1 commit