You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Michael A. Smith (Jira)" <ji...@apache.org> on 2020/07/12 19:33:00 UTC

[jira] [Assigned] (AVRO-2893) Isolate Exception Classes to Simplify Import Graph

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

Michael A. Smith reassigned AVRO-2893:
--------------------------------------

    Assignee: Michael A. Smith

> Isolate Exception Classes to Simplify Import Graph
> --------------------------------------------------
>
>                 Key: AVRO-2893
>                 URL: https://issues.apache.org/jira/browse/AVRO-2893
>             Project: Apache Avro
>          Issue Type: Improvement
>          Components: python
>            Reporter: Michael A. Smith
>            Assignee: Michael A. Smith
>            Priority: Major
>
> Many of the python avro modules implement custom exceptions. Other modules import those exceptions. Since imports cannot be cyclic, this means you can't use, say, {{avro.schema.AvroException}} in {{avro.io}} and at the same time use {{avro.io.BinaryDecoder}} in {{avro.schema}}.
> I propose that exception classes should be moved into {{avro.errors}} and that that module should strictly not import anything else from {{avro.*}}.



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