[ 
https://issues.apache.org/jira/browse/AVRO-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16960494#comment-16960494
 ] 

ASF subversion and git services commented on AVRO-2578:
-------------------------------------------------------

Commit 3e79dfec8461fb0157f068cff7ba24be8cdfa9d8 in avro's branch 
refs/heads/master from Michael A. Smith
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=3e79dfe ]

AVRO-2578: Support Both Capitalizations of Parse (#666)

* AVRO-2578: Provide Parse in Both Capitalizations

* AVRO-2578: Normalize Calls to Parse

* AVRO-2578: Test Both Schema Parse Capitalizations

* AVRO-2578: Test Both Capitalizations of Protocol.Parse

* AVRO-2578: Add Deprecation Warnings for Capital-P Parse

* AVRO-2578: Fix Tests for Py3.5


> py3 avro should support both capitalizations of 'parse'
> -------------------------------------------------------
>
>                 Key: AVRO-2578
>                 URL: https://issues.apache.org/jira/browse/AVRO-2578
>             Project: Apache Avro
>          Issue Type: Bug
>          Components: python
>            Reporter: Michael A. Smith
>            Assignee: Michael A. Smith
>            Priority: Major
>
> It would be easier for people transitioning between python2 and python3 to 
> not have to do
> {code:java}
> try:
>     from avro.schema import parse
> except ImportError:
>     from avro.schema import Parse as parse{code}
> In order to keep the best compatibility, we should probably support both 
> capitalizations.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to