This should help reduce warning spew when building with newer compilers. The pybind11::module type has been renamed pybind11::module_ to avoid conflicts with c++20 modules, according to the pybind11 changelog, so this CL also updates gem5 source to use the new type. There is supposedly an alias pybind11::module which is for compatibility, but we still get linker errors without changing to pybind11::module_. Change-Id: I0acb36215b33e3a713866baec43f5af630c356ee Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/40255 Maintainer: Bobby R. Bruce <bbruce@ucdavis.edu> Reviewed-by: Bobby R. Bruce <bbruce@ucdavis.edu> Tested-by: kokoro <noreply+kokoro@google.com>
36 lines
768 B
Python
36 lines
768 B
Python
# -*- coding: utf-8 -*-
|
|
import os
|
|
|
|
import pytest
|
|
|
|
import env # noqa: F401
|
|
|
|
from pybind11_tests import eval_ as m
|
|
|
|
|
|
def test_evals(capture):
|
|
with capture:
|
|
assert m.test_eval_statements()
|
|
assert capture == "Hello World!"
|
|
|
|
assert m.test_eval()
|
|
assert m.test_eval_single_statement()
|
|
|
|
assert m.test_eval_failure()
|
|
|
|
|
|
@pytest.mark.xfail("env.PYPY and not env.PY2", raises=RuntimeError)
|
|
def test_eval_file():
|
|
filename = os.path.join(os.path.dirname(__file__), "test_eval_call.py")
|
|
assert m.test_eval_file(filename)
|
|
|
|
assert m.test_eval_file_failure()
|
|
|
|
|
|
def test_eval_empty_globals():
|
|
assert "__builtins__" in m.eval_empty_globals(None)
|
|
|
|
g = {}
|
|
assert "__builtins__" in m.eval_empty_globals(g)
|
|
assert "__builtins__" in g
|