Chore/1010 add support for python 314

[veenstrajelmer]

Description

• Please include a summary of the change and which issue is fixed.

• Please also include relevant motivation and context.

• List any dependencies that are required for this change.

• Fixes Add support for Python 3.14 #1010

Type of change

Check relevant points.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Please describe the tests that you ran to verify your changes.

• Provide instructions so we can reproduce.

• Please also list any relevant details for your test configuration

• Test A

• Test B

Checklist:

Prepare items below using:
[ ❌ ] (markdown: [ :x: ]) for TODO items
[ ✅ ] (markdown: [ :white_check_mark: ]) for DONE items
[ N/A ] for items that are not applicable for this PR.

• updated version number in setup.py/pyproject.toml/environment.yml.
• updated the lock file.
• added changes to History.rst.
• updated the latest version in README file.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• documentation are updated.

[veenstrajelmer]

Failing dependency installation (poetry error), so suggestion to first update the poetry version (#1013) and then rerun the tests in this PR.

[veenstrajelmer]

Awaiting these fixes:

• TRACKER: add support for Python 3.14 pandas-dev/pandas#62261 >> pandas already claims to work on py3.14
• REL: prepare release of version 0.12 geopandas/pyogrio#560

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[veenstrajelmer]

After updating the minimal lxml version from 5 to 6, the build on Python 3.14 is succesful. However, in the pytest step, there is an ImportError:

ImportError while loading conftest '/Users/runner/work/HYDROLIB-core/HYDROLIB-core/tests/conftest.py'.
tests/conftest.py:6: in <module>
    from hydrolib.core.dflowfm.bc.models import (
hydrolib/core/dflowfm/__init__.py:1: in <module>
    from .bc import *
hydrolib/core/dflowfm/bc/__init__.py:1: in <module>
    from .models import (
hydrolib/core/dflowfm/bc/models.py:22: in <module>
    from hydrolib.core.base.models import BaseModel, ModelSaveSettings
hydrolib/core/base/models.py:284: in <module>
    class FileModel(BaseModel, ABC):
.venv/lib/python3.14/site-packages/pydantic/v1/main.py:221: in __new__
    inferred = ModelField.infer(
.venv/lib/python3.14/site-packages/pydantic/v1/fields.py:504: in infer
    return cls(
.venv/lib/python3.14/site-packages/pydantic/v1/fields.py:434: in __init__
    self.prepare()
.venv/lib/python3.14/site-packages/pydantic/v1/fields.py:544: in prepare
    self._set_default_and_type()
.venv/lib/python3.14/site-packages/pydantic/v1/fields.py:576: in _set_default_and_type
    raise errors_.ConfigError(f'unable to infer type for attribute "{self.name}"')
E   pydantic.v1.errors.ConfigError: unable to infer type for attribute "filepath"
Error: Process completed with exit code 4.

Could this be resolved after the pydantic migration described in #732?

A similar error pops up when running only from hydrolib.core.base.models import BaseModel, but then also a warning is displayed: "c:\DATA\checkouts\hydrolib-core\hydrolib\core\base\models.py:15: UserWarning: Core Pydantic V1 functionality isn't compatible with Python 3.14 or greater.". So it seems that fixing #732 would indeed fix this problem.