Closed DominicOram closed 1 year ago
Despite https://github.com/bluesky/event-model/commit/5abfa586b09897d86c1b709dd2926edf9f87b634 pinning the pydantic version in dev there are still potential issues with pydantic.
pydantic
dev
I should be able to do the following in my application that uses bluesky and pydantic:
bluesky
pip install bluesky pip install pydantic python >>> from bluesky.run_engine import RunEngine
The above will throw an exception.
The issue is that because the pin is in dev pip does not realise that bluesky requires the pin so installs the latest pydantic. The import check in https://github.com/bluesky/event-model/blob/main/event_model/documents/generate/type_wrapper.py then picks up the v2. Possible fixes are:
pip
event-model
Despite https://github.com/bluesky/event-model/commit/5abfa586b09897d86c1b709dd2926edf9f87b634 pinning the
pydantic
version indev
there are still potential issues withpydantic
.Expected Behavior
I should be able to do the following in my application that uses
bluesky
andpydantic
:Current Behavior
The above will throw an exception.
Possible Solution
The issue is that because the pin is in
dev
pip
does not realise thatbluesky
requires the pin so installs the latestpydantic
. The import check in https://github.com/bluesky/event-model/blob/main/event_model/documents/generate/type_wrapper.py then picks up the v2. Possible fixes are:event-model
to work for v2 (probably prefered)