On Fri, Feb 7, 2025, 5:30 AM Markus Armbruster wrote:
> John Snow writes:
>
> > On Fri, Jan 31, 2025 at 8:18 AM Markus Armbruster
> wrote:
> >
> >> Cc: John Snow for Python typing expertise.
> >>
> >> Daniel P. Berrangé writes:
> >>
> >> > This replaces use of the constants from the QapiSpecia
John Snow writes:
> On Fri, Jan 31, 2025 at 8:18 AM Markus Armbruster wrote:
>
>> Cc: John Snow for Python typing expertise.
>>
>> Daniel P. Berrangé writes:
>>
>> > This replaces use of the constants from the QapiSpecialFeatures
>> > enum, with constants from the auto-generate QapiFeatures enu
On Fri, Jan 31, 2025 at 8:18 AM Markus Armbruster wrote:
> Cc: John Snow for Python typing expertise.
>
> Daniel P. Berrangé writes:
>
> > This replaces use of the constants from the QapiSpecialFeatures
> > enum, with constants from the auto-generate QapiFeatures enum
> > in qapi-features.h
> >
Daniel P. Berrangé writes:
> This replaces use of the constants from the QapiSpecialFeatures
> enum, with constants from the auto-generate QapiFeatures enum
> in qapi-features.h
>
> The 'deprecated' and 'unstable' features still have a little bit of
> special handling, being force defined to be t
Cc: John Snow for Python typing expertise.
Daniel P. Berrangé writes:
> This replaces use of the constants from the QapiSpecialFeatures
> enum, with constants from the auto-generate QapiFeatures enum
> in qapi-features.h
>
> The 'deprecated' and 'unstable' features still have a little bit of
> s
This replaces use of the constants from the QapiSpecialFeatures
enum, with constants from the auto-generate QapiFeatures enum
in qapi-features.h
The 'deprecated' and 'unstable' features still have a little bit of
special handling, being force defined to be the 1st + 2nd features
in the enum, regar
