[prev in list] [next in list] [prev in thread] [next in thread] 

List:       avro-dev
Subject:    [jira] [Updated] (AVRO-1788) python api differs unnecessarily between python2 and python3
From:       "Suraj Acharya (JIRA)" <jira () apache ! org>
Date:       2016-09-29 2:35:21
Message-ID: JIRA.12935015.1454043537000.694162.1475116521137 () Atlassian ! JIRA
[Download RAW message or body]


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

Suraj Acharya updated AVRO-1788:
--------------------------------
    Status: Patch Available  (was: Open)

> 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
> 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)


[prev in list] [next in list] [prev in thread] [next in thread]