Matt Patterson
- Login: matt@saxonica.com
- Introduction email sent: No
- Which product do you use?: Saxon
- Registered on: 2023-05-02
- Last connection: 2024-10-09
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 12 | 10 | 22 |
Reported issues | 7 | 2 | 9 |
Projects
Project | Roles | Registered on |
---|---|---|
Saxon | Manager, Developer | 2023-05-02 |
Non-Conformances | Manager, Developer | 2023-05-02 |
Saxon-CE | Manager, Developer | 2023-05-02 |
SaxonC | Manager, Developer | 2023-05-02 |
SaxonJS | Manager, Developer | 2023-05-02 |
SaxonMirrorHE | Manager, Developer | 2023-05-02 |
W3C QT Specifications | Manager, Developer | 2023-05-02 |
Activity
2024-08-30
-
Bug #6522 (New): The documentation for Saxon\SchemaValidator is incorrectThe 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
-
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 editionWith 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... -
Some kind of `isLicensed()` method on Configuration or Processor w...
2024-08-14
-
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 errorgradle 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 ... -
``` shell
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':eec_python_build_wheel'.
> Failed to ...
2024-07-12
-
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.0I'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... -
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 completionHello,
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
-
Thanks, Martin.
I can reproduce it with `saxonche` too, after following your example. Bug #6466 (In Progress): Python interactive interpreter seg-faults on tab completionHello,
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.... -
-
Also available in: Atom