ChainerX routines never raise Python primitive exception
See original GitHub issueCurrently, ChainerX routines raise only ChainerX specific exceptions. However, if a NumPy’s function raises a Python primitive exception, the corresponding ChainerX routine also should the same exception.
I have started wanting this compatibility when I was extending __getitem__
(https://github.com/chainer/chainer/pull/7561#issuecomment-505424397).
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
ChainerX Tutorial — Chainer 7.8.1 documentation
The following example demonstrates how you can create an array and access its most basic attributes. Note that the APIs are identical to...
Read more >Multi-engine multi-level simulation for system specification ...
the primitive components and objects, and to then develop them and the ... interface with programs written in C, C++, Java and Python....
Read more >THESE Fangyan LI | Manualzz
The overarching goal is to define the primitive components and objects, ... ect., and it can interface with programs written in C, C++,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Seems we need an exception policy in C++ code and binding code. I’ve faced the same problem when implementing clip function( https://github.com/chainer/chainer/pull/7285 ): https://github.com/chainer/chainer/blob/139de248629a3efccf6734565f64ab39a2fabbfb/chainerx_cc/chainerx/python/routines.cc#L674-L676
This issue is closed as announced. Feel free to re-open it if needed.