wlav
wlav
Can you check the output of: ``` $ python >>> import cppyy >>> cppyy.cppexec("std::cerr
That error is coming from: ``` gInterpreter->Declare( "#if defined(__GLIBCXX__) && __GLIBCXX__ >= 20220506\n" "template std::string::pointer std::string::_M_use_local_data();\n" "template std::wstring::pointer std::wstring::_M_use_local_data();\n" "#endif\n" ); ``` where that `__GLIBCXX__` is supposed to check for...
Looks like issue with `std::allocator`, not with that `std::string` constructor itself (which just uses it). Also, this Fedora system has gcc13, so may have had further changes that the original...
In fact, if I remove all other workarounds and just add this at the top of the script (after importing cppyy), then things run fine for me on the Fedora...
For CI, yes that may work, but it's a bit convoluted to build from source when not everything is released b/c of the way pip deals (or rather not deals)...
Release 3.1.1 works for me (famous last words) on that Fedora docker image ...
The test needs a doc string (see other examples) as that will be printed when running `pytest -v`.
Issue is fixed in repo, but probably useful to add further tests.
Yes, the `explicit` keyword is not exposed by Cling and thus ignored by cppyy. A pythonization that checks the type and rejects it, is the only workaround I can think...
Indeed, missed that. Regardless, if this is for ROOT, you'll have to submit a bug report on the ROOT repo, not here, as the ROOT project contains a fork of...