Hi Michael, A logical place for me would be the docs. In this case, I would document the options in the PythonDoc and then use a tool to generate the docs. We can then make this part of the website: https://avro.apache.org/docs/1.9.2/
This is similar to what we've done in the past for Java/C/C# etc. Cheers, Fokko Op za 22 feb. 2020 om 19:00 schreef Michael A. Smith <mich...@smith-li.com>: > In https://github.com/apache/avro/pull/830 I propose that we offer > users the option to maintain Python's current behavior of allowing > spaces in enum symbols. In this implementation, the default behavior > is more spec-compliant, but users can choose to go back to the way it > was. Since Python has never implemented the spec change in > https://issues.apache.org/jira/browse/AVRO-1725 to this point, it's > certain that many python-only Avro users will find this new behavior a > sad surprise. (I'm certain of this because I'm one of those users who > was dismayed when I found my avro incompatible with the Java avro > implementation.) So I wanted to offer them an out. > > I'm not exactly sure how to document this other than in the Python > code itself, because it's not part of the spec. Any suggestions? >
