Philipp Wagner

The module loading error that you resolved by setting LIBPYTHON_LOC seems unrelated to the segfault issue that we discussed earlier. I'd suggest to keep this issue to the segfault; I...

Let's keep this open for a backport into 1.7.

@abyszuk can you help us confirm that the issue is indeed resolved in master? First, download https://github.com/cocotb/cocotb/suites/8784257799/artifacts/398860678, which contains wheels from the lastest master release. Then install cocotb from these...

@Skavarei `sys.version_info.major` was added in Python 3.1 (https://docs.python.org/3/library/sys.html#sys.version_info), hence somehow you're not using Python 3.7 to execute the test, as Colin and Marlon pointed out. So you'll need to do...

It seems like we pick self-hosted runners at times even though we don't want to, see https://github.com/cocotb/cocotb/runs/8024112389?check_suite_focus=true Also: we need to add ~/.local/bin to PATH by default to mimic the...

Thanks @mcheah for your pull request. I'd like to understand the problem a bit better to see if the fix is really what we want. At first glance, it looks...

No cleanup should be necessary before/after installing a new version of cocotb, but things can certainly go wrong. * Did you install a previous version of cocotb into the same...

> We just reverted that commit. "We", meaning you personally, Kaleb, I assume? The cocotb project didn't revert the commit. https://github.com/cocotb/cocotb/issues/3080 tracks improving the documentation.

But what's the problem, and why does it work? I'd like to really understand what's going on here, this area of code is too fragile for experiments :-)

I would be interested in seeing how Debian compiles their 32b python packages on a 64b multiarch system (it they provide python that way).