Test that the top-level package can be imported

[tadamcz]

hopefully this would help catch things like #1164 ? (I need to check that this is actually true, i.e. the test actually fails)

[tadamcz]

To my puzzlement, the test passes?! Even though I am downstream of d865444, where I encountered the bug in #1164.

https://github.com/UKGovernmentBEIS/inspect_ai/actions/runs/12876243894/job/35898928948?pr=1165#step:6:83

What am I doing wrong?

[tadamcz]

The identical test fails (correctly, I believe) when I install Inspect d865444 in an environment on my laptop 🤔

What am I missing @jjallaire? Is hynek/build-and-inspect-python-package@v2 doing some nonstandard stuff?

[jjallaire]

I am not sure. I can't get the import inspect_ai to fail for me either (even before your change).

So it could be that there are contexts/environments that are sensitive to the __init__.py file and others that are not?

[tadamcz]

Pretty sure __init__.py is required as part of the Python spec:

The __init__.py files are required to make Python treat directories containing the file as packages (unless using a namespace package, a relatively advanced feature)

https://docs.python.org/3/tutorial/modules.html#packages

So anything that does not require it would be 'wrong', I believe. (I believe some IDEs are super-permissive when importing things, but I don't think this kind of thing should affect CI.)

[tadamcz]

I can't get the import inspect_ai to fail for me either

Well, I can get it to fail when I install Inspect (from source) in a new environment

[jjallaire]

Well, I can get it to fail when I install Inspect (from source) in a new environment

Okay, good. No idea why it was working for me then. Obviously we are better off with the __init__.py.