Saxonica Developer Community

2024-07-12

• 
  Matt Patterson SaxonC

  18:10 · Closed issue

  Fixed by changes to build system to ensure that the XML Resolver's local cache of important unchanging documents (like the XHTML1 DTDs) are included in SaxonC.
  Fix will be included in the next maintenance release Bug #6469 (Resolved): SXXP0003 when parsing XHTML file with saxoncee 12.5.0

  I'm encountering an error when trying to parse an XHTML file using Python saxoncee version 12.5.0. The error message is as follows:
  ``` python
  File "python_saxon/saxonc.pyx", line 935, in saxoncee.PySaxonProcessor.parse_xml
  saxoncee...
• 
  Matt Patterson SaxonC

  17:56 · Commented on issue

  We managed to reproduce the report and find some places where we were incorrectly managing C++ resources, and fixing that stopped those segfaults from occuring.
  We need to do some more testing to ensure we've fixed all the problems wi... Bug #6466: Python interactive interpreter seg-faults on tab completion

  Hello,
  I installed the Python package `saxoncee ==12.4.2` in a Python 3.11.9 virtual environment, and upon trying to list the properties of an instance using tab completion, the interpreter crashed:
  ```
  ~ > uname -a
  Darwin pooh 22....

2024-07-08

• 
  Matt Patterson SaxonC

  21:37 · Edited issue

  Thanks, Martin.
  I can reproduce it with `saxonche` too, after following your example. Bug #6466 (In Progress): Python interactive interpreter seg-faults on tab completion

  Hello,
  I installed the Python package `saxoncee ==12.4.2` in a Python 3.11.9 virtual environment, and upon trying to list the properties of an instance using tab completion, the interpreter crashed:
  ```
  ~ > uname -a
  Darwin pooh 22....
• 
  Matt Patterson Reading around it seems like Readline causing segfaults in the REPL is a thing that has happened outside SaxonC in the past, with the culprits being versions of Readline Python was compiled against not quite matching with installed versi...

  10:47 · Edited issue
• 
  Matt Patterson

  10:20 · Edited issue

2024-07-05

• 
  Matt Patterson SaxonC

  13:24 · Edited issue

  There's a definite difference in behaviour between SaxonC and SaxonJ. This is a bug: we should be including, and using, a copy of the XHTML (and other common W3C) DTDs in SaxonC. Bug #6469 (In Progress): SXXP0003 when parsing XHTML file with saxoncee 12.5.0

  I'm encountering an error when trying to parse an XHTML file using Python saxoncee version 12.5.0. The error message is as follows:
  ``` python
  File "python_saxon/saxonc.pyx", line 935, in saxoncee.PySaxonProcessor.parse_xml
  saxoncee...
• 
  Matt Patterson I also cannot reproduce this with 12.5.0 and macOS 14.5 using the supplied script.
  However, I can see that an HTTP connection to www.w3.org is made to retrieve the XHTML DTD.
  If I prevent network connections being made to www.w3.or...

  11:14 · Commented on issue

2024-07-02

• 
  Matt Patterson SaxonC

  12:24 · Commented on issue

  This shouldn't manifest in the 12.5 Maintenance release, but we're leaving this issue open until we've fully revisited the underlying string-handling issue. Bug #6353: Unicode characters in filenames are causing errors in Windows

  As reported by a user in this SO post comment: https://stackoverflow.com/questions/77962974/saxon-xslt-processing-thousands-of-xml-files-in-a-complex-tree-structure/77963410?noredirect=1#comment137525632_77963410
  Thanks to silfer1200 ...

2024-06-18

• 
  Matt Patterson SaxonC

  13:51 · Commented on issue

  GraalVM's static analysis is missing quite a few classes that are loaded dynamically, which the EXSLT functions are (this was also the source of an issue with Windows-1252 encoded files on non-windows platforms).
  The only sane way to... Support #6445: Are EXSLT function supposed to be supported in SaxonC EE (12.4.2)?

  Hi,
  I am currently testing some code to be run with both XSLT 1.0 processors like xsltproc/libxslt as well as XSLT 3 processors like Saxon 12.
  I had thought that Saxon 12 EE supports most EXSLT functions and the documentation https...

2024-06-17

• 
  Matt Patterson SaxonC

  21:50 · Commented on issue

  I added more explicit instructions to the README.md in the pypi folder, which tackles part of this. The SaxonC/Python documentation on Saxonica.com should probably be updated to reflect that too. Bug #3726: Saxon License not being picked up relative to library file

  According to the documentation:
  http://saxonica.com/saxon-c/index.xml#license
  ~~~
  Location of the Saxon license file for commercial products: Saxon/C looks in the path relative to where the main library has been installed. For...