Follow usage of pydantic from Gammapy or pursue something different?

[chaimain]

Pydantic v2 has brought up large changes from its earlier versions (See Migration guide).

Gammapy adapted to these changes in the PR 4750 and in Asgardpy it was done in #165 (some of the changes highlighted here).

There is no "complete" solution to all the input types used in either pipeline. Is it worth investigating the time and effort to make changes in Asgardpy?

So far, no breaking changes have been seen in Asgardpy's workflow.

[chaimain]

• In this pipeline, we need only 4 custom input types - Angle, Energy, Path and Time.
• We always need a single entry for Angle and Path types, whereas for Energy (either only min and max, or a range of edges) and Time (intervals with an associated frame type), always a list of entries. Currently only TimeInterval is defined.
• Only Angle and Energy input types are of astropy.units.Quantity.

[chaimain]

As the changes will involve breaking the Config structure again (generalized usage of EnergyRangeConfig), it is probably better to make these changes for v0.5.1