[
https://issues.apache.org/jira/browse/AVRO-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526607#comment-15526607
]
Alexander Hasha commented on AVRO-1788:
---------------------------------------
For reference, here is what I was working on when I submitted the issue. This
commit shows changes I had to make to make a python app using `avro` Python 2
and 3 compatible.
https://github.com/blaze/odo/pull/386/commits/ee5e6f384fb809decbcf709aaf74df072a99d067
> python api differs unnecessarily between python2 and python3
> ------------------------------------------------------------
>
> Key: AVRO-1788
> URL: https://issues.apache.org/jira/browse/AVRO-1788
> Project: Avro
> Issue Type: Wish
> Reporter: Alexander Hasha
> Priority: Minor
>
> It is difficult to use the python avro module in projects that maintain
> simultaneous compatibility between python 2 and python 3, because there are
> small differences in the API between the two versions in the module that seem
> unnecessary.
> For example, to parse a schema string in python 2:
> {code}
> from avro.schema import parse
> {code}
> and in python 3:
> {code}
> from avro.schema import Parse
> {code}
> In Python2, DatumReader's constructor has keyword argument "writers_schema",
> and in Python 3 it becomes "writer_schema" (no s).
> Would it be possible to align method names and arguments across the two
> modules?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
