Saxonica Developer Community

2024-11-20

• 
  Matt Patterson SaxonC

  19:03 · Commented on issue

  Bastian Politycki wrote in #note-4:
  >
  > That's great! Is there already a detailed schedule? The saxonche-stubs package is indeed not complete.
  We can't commit to a date or release, unfortunately. I'll be taking a look at your packa... Bug #6563: Missing py stubs in saxonche (12.5)

  SaxonC 12.5 Python wheels do not include the stubs, which are essential for IDEs to provide autocompletion, type inference, and better code assistance.
  Stubs (.pyi files) are required when the library is a compiled C extension, or IDE...

2024-11-19

• 
  Matt Patterson SaxonC

  17:57 · Replied in forum

  This is something we're actively exploring as we look at improving the build process and setup for Saxon C more generally.
  Obviously, I'm not making any commitment here - one of the things it would require is adding more complexity t... Saxon/C Help and Discussions: RE: Can Saxonica provide the executables/binaries of Transform/Query/Validate command line tools of the SaxonC 12 editions for download?

  For some reasons, for SaxonC, you provide the Python packages for each platform but you don't publish any executables/binaries of the Transform/Query (and for SaxonC EE) Validate command line tools, only the runtime libaries and the sour...

2024-10-31

• 
  Matt Patterson SaxonC

  12:15 · Created issue

  Bug #6576 (New): EE-Python erroring out when trying to create a Processor

  With the current refactored-build version of SaxonC, when trying to run anything using EE, there's an exception:
  ```
  Flag is true to create SaxonProcessor with license
  Java DEBUG: j_getErrorMessageWithErrorCode called
  Java Debug: E...

2024-08-30

• 
  Matt Patterson SaxonC

  18:17 · Created issue

  Bug #6522 (New): The documentation for Saxon\SchemaValidator is incorrect

  The PHP `Saxon\SchemaValidator` documentation for `getValidationReport()` incorrectly states that the property to set to get a validation report as an XmlNode is `report` and not `report-node`. No mention is made there or in the document...

2024-08-21

• 
  Matt Patterson SaxonC

  17:10 · Commented on issue

  We don't expose the configuration directly in SaxonC, so we need something there... If applied to Saxon J, with `isLicensedFeature`, you still need to specify which edition, rather than a generic have-i-successfully-provided-my-license-t... Feature #6517: There isn't a simple way to verify that Saxon has found and accepted a license file, regardless of edition

  With a Saxon EE license, a call to isSchemaAware on the Processor will verify whether or not your EE license has been found and accepted. There's no equivalent for PE.
  Some kind of `isLicensed()` method on Configuration or Processor w...
• 
  Matt Patterson With a Saxon EE license, a call to isSchemaAware on the Processor will verify whether or not your EE license has been found and accepted. There's no equivalent for PE.
  Some kind of `isLicensed()` method on Configuration or Processor w...

  16:49 · Created issue

2024-08-14

• 
  Matt Patterson Saxon

  13:39 · Commented on issue

  Looking back in the Gradle output I saw this:
  ```python
  Traceback (most recent call last):
  File "<string>", line 1, in <module>
  ImportError: cannot import name 'get_platform' from 'wheel.bdist_wheel' (/Users/matt/Documents/work/s... Bug #6509: Python-related Gradle tasks failing with python error

  gradle tasks that touch python-related parts of the build started failing with this message:
  ``` shell
  FAILURE: Build failed with an exception.
  * What went wrong:
  Execution failed for task ':eec_python_build_wheel'.
  > Failed to ...
• 
  Matt Patterson gradle tasks that touch python-related parts of the build started failing with this message:
  ``` shell
  FAILURE: Build failed with an exception.
  * What went wrong:
  Execution failed for task ':eec_python_build_wheel'.
  > Failed to ...

  13:34 · Created issue

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....