Skip to content

Conversation

@zrgt
Copy link
Contributor

@zrgt zrgt commented Oct 7, 2025

Needed to support Debian >13 systems

fixes #417

Needed to support Debian >13 systems
@s-heppner s-heppner changed the base branch from develop to Experimental/Adapter/RDF October 9, 2025 13:45
@s-heppner s-heppner changed the base branch from Experimental/Adapter/RDF to develop October 9, 2025 13:45
@s-heppner s-heppner merged commit f22422c into eclipse-basyx:develop Oct 9, 2025
15 checks passed
@s-heppner s-heppner deleted the fix/update_pyecma_lxml_libs branch October 10, 2025 07:48
moritzsommer pushed a commit to rwth-iat/basyx-python-sdk that referenced this pull request Oct 21, 2025
The current version of `lxml>=4.2,<5` fails on modern Debian 13 
machines, as there is a dependency conflict with a base library.

This adapts both `lxml` and `pyecma376-2` versions to work with the new
Linux base libraries.

Fixes eclipse-basyx#417
@s-heppner s-heppner mentioned this pull request Oct 27, 2025
zrgt added a commit to rwth-iat/basyx-python-sdk that referenced this pull request Nov 18, 2025
The current version of `lxml>=4.2,<5` fails on modern Debian 13 
machines, as there is a dependency conflict with a base library.

This adapts both `lxml` and `pyecma376-2` versions to work with the new
Linux base libraries.

Fixes eclipse-basyx#417
s-heppner added a commit that referenced this pull request Dec 5, 2025
Prepare Release v2.0.0

# Release Notes

Version 2.0.0 of the BaSyx-Python SDK comes with a major refactoring of the server and a renewed concept for data persistence.

Previously, the server code was split between the `sdk` and `server` packages (due to historic development of the code). 
Now all the code relevant just for the server is located in `server`, where it belongs. Since this means, some code that was previously in `sdk` is not there anymore, this is a breaking change and warranted the new major release.

> [!note]
> This release does not have any changes in implemented AAS specification versions. It is the preparotory release in order to get ready for the new versions of the specifications, as well as new features for the SDK, such as Registry and Discovery server.

> [!warning]
> Due to these major refactorings, there were some backward incompatible changes. Please check the documentation, if you encounter any issues.

# Changelog

**Notable:**
- Backward Incompatible: Refactor server functionality from `sdk` to `server` (See: #388)
- Backward Incompatible: Refactor `backend` concept for data persistence (See: #370)
- Backward Incompatible: Refactor server `start-up` options (See: #418)
- Remove support for Python 3.9 (as it is EoL) (See #433)

**Improvements:**
- Clarify documentation of running the server with Docker (See: #398)
- Document running the server without Docker (See: #403)
- Improve XML serialization (See: #406)
- Improve server reading of JSON and XML files (See: #408)
- Add more utility methods for `Referable` and `Key` handling (See: #410)

**Bugfixes:**
- Fix type issues found with a new version of `mypy` (See: #399)
- Fix parsing of `ConceptDescription`s in the server (See: #420)
- Update `pyecma376-2` and `lxml` dependencies (See: #419)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants