You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Solution to issue cannot be found in the documentation.
I checked the documentation.
Issue
We observed a failure, on linux-64 only, to invoke a pybind11 exception translator when it was built with g++ 9.4 and the exception-throwing code was built with g++ 10.3.
The attached file gives a small example. If the handler and example files are built (using the given shell scripts) with the same g++ version, when running example.py everything works properly (the output includes "In translator"). But if the handler is built with g++ 9.4 and the example is built with g++ 10.3, it fails (the output does not contain that string). It also fails when built the other way, with the handler under 10.3 and the example under 9.4.
Solution to issue cannot be found in the documentation.
Issue
We observed a failure, on linux-64 only, to invoke a pybind11 exception translator when it was built with g++ 9.4 and the exception-throwing code was built with g++ 10.3.
The attached file gives a small example. If the handler and example files are built (using the given shell scripts) with the same g++ version, when running
example.py
everything works properly (the output includes "In translator"). But if the handler is built with g++ 9.4 and the example is built with g++ 10.3, it fails (the output does not contain that string). It also fails when built the other way, with the handler under 10.3 and the example under 9.4.This may be related to #77
minexample.txt
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: