N-o-Z

@TinoSM Hi, we are prioritizing this issue and will investigate what is required in order to update the pydantic version for our auto generated client or find a workaround for...

The update introduces breaking changing resulting in updates in the openapi-generator and the pydantic version upgrade. Pydantic: Changes in default and optional parameter locations and some changes in data types....

For more information regarding the changes in pydantic: [Migration Guide - Pydantic](https://docs.pydantic.dev/latest/migration/)

@TinoSM I'm not familiar with any shading mechanism in Python. AFAIK, for each virtual environment you can have a single version of a package. @ozkatz that would have been the...

> @N-o-Z we can either override the templates or add a post processing step, no? Templates won't help us here IMHO, I can investigate the option of a post processing...

> @N-o-Z , while a pain to maintain a compatibility matrix, I think the best long term solution is option 2: > > > 2. Break away from the lakeFS...

Another option: Step back from using lakefs-sdk as the underlying API client implementation and perform the http request directly **Pros:** 1. Decoupling of lakeFS SDK and lakeFS releases from HL...

Below is a table summarizing all the suggestions so far: **Solution** | **Effort** | **Risk** | **Friction** -- | -- | -- | -- ~~Bump lakeFS major version~~ | Minimal,Requires...

@ozkatz Naive approach didn't work: ``` ../../../venv/test-pydantic/lib/python3.10/site-packages/_pytest/assertion/rewrite.py:186: in exec_module exec(co, module.__dict__) tests/integration/conftest.py:9: in from lakefs import client lakefs/__init__.py:5: in from lakefs.client import Client lakefs/client.py:12: in import lakefs_sdk ../../../venv/test-pydantic/lib/python3.10/site-packages/lakefs_sdk/__init__.py:21: in from...

@hjain5164 hi! Thanks for picking up the glove - are you still interested in taking this issue?