avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suraj Acharya (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AVRO-1788) python api differs unnecessarily between python2 and python3
Date Thu, 29 Sep 2016 02:34:20 GMT

     [ https://issues.apache.org/jira/browse/AVRO-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Suraj Acharya reassigned AVRO-1788:
-----------------------------------

    Assignee: Suraj Acharya

> 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
>          Components: python
>            Reporter: Alexander Hasha
>            Assignee: Suraj Acharya
>            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)

Mime
View raw message