Re: Backwards incompatible API change to Python schema object "properties"

2023-08-17 Thread Michael A. Smith
I can use a deprecation warning on those calls, sure. On Mon, Jul 31, 2023 at 1:14 PM Ryan Skraba wrote: > > Hello! I think this sounds alright to me -- I noticed that your draft > PR didn't delete the get_/set_props methods. Is there a mechanism we > can use to mark them as deprecated for the

Re: Backwards incompatible API change to Python schema object "properties"

2023-07-31 Thread Ryan Skraba
Hello! I think this sounds alright to me -- I noticed that your draft PR didn't delete the get_/set_props methods. Is there a mechanism we can use to mark them as deprecated for the length of one major release before removing them? I have no objection to improving the Python API :D Your PR is

Backwards incompatible API change to Python schema object "properties"

2023-07-28 Thread Michael A. Smith
Please take a look at AVRO-3816. I'm proposing a backwards incompatible change to the python schema implementation. So far I have a PR in draft that I believe _is_ backwards-compatible, but is just a step on the way - it doesn't solve the problem entirely. I'd like to get to the following advantag