GitHub user manu-chroma opened a pull request:

    https://github.com/apache/avro/pull/235

    schema.py: No sys traceback in parse exception

    In the ``SchemaParseException``, do not provide sys traceback. 
    
    For our project CWL Tool, we're using `avro/py` in our python 3 builds. 
More on this has been discussed here: 
https://issues.apache.org/jira/browse/AVRO-2046 
    
    For doing this, we use `autotranslate` tool which converts `avro/py` code 
to python2and3 compatible code during runtime. 
    The problem arises when it tries to convert this `raise Exception` command. 
There is no way to achieve this in a cross-compatible way without the use of 
external lib.
     
    Thus, I've created this PR. This is a very minimal change and really solves 
our problem for the time being. We really hope you'll consider this or at least 
give your feedback on the same.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/manu-chroma/avro patch-1

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/avro/pull/235.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #235
    
----
commit 92525fda5cbae1ea7b9e5e255a52ad7e8f0ff71f
Author: Manvendra Singh <manvendra0...@gmail.com>
Date:   2017-07-17T08:53:28Z

    schema.py: No sys traceback in parse exception
    
    In the ``SchemaParseException``, do not provide sys traceback. 
    
    For our project CWL Tool, we're using `avro/py` in our python 3 builds. 
More on this has been discussed here: 
https://issues.apache.org/jira/browse/AVRO-2046 
    
    For doing this, we use `autotranslate` tool which converts `avro/py` code 
to python2and3 compatible code during runtime. 
    The problem arises when it tries to convert this `raise Exception` command. 
There is no way to achieve this in a cross-compatible way without the use of 
external lib.
     
    Thus, I've created this PR. This is a very minimal change and really solves 
our problem for the time being. We really hope you'll consider this or at least 
give your feedback on the same.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to