Platform Specific Dependencies

[hmc-cs-mdrissi]

I have a codebase that is tested to run on both mac/linux. One of dependencies only works on linux and I try to do,

if sys.platform == "linux"
  import linux_dep
  ...
else:
  ...

The ci I'm using has linux machines. Running ci job on mac is less convenient and would prefer not to require. Is there a good way to have pyright fail if I accidentally do import linux_dep outside a guarded area? I'm aware of pyright --pythonplatform=Darwin. That when run on linux machine with linux_dep installed won't fail though if it's imported outside guard.

I do have some control over linux_dep's codebase and could make changes to it if that'd help. Like I could add assert sys.platform == "linux" inside of it, but that would mostly just lead to a lot of code being unreachable and wouldn't error either.

edit: This question maybe fits better in typing discussion as while I expect answer will involve --pythonplatform somehow, rest of it is not pyright specific. I'll cross post it there.

[erictraut]

What I typically do in cases like this is to isolate the platform-specific behaviors into a single submodule within my code base. That way, the ugly (and somewhat fragile) conditional imports are relegated to a single place rather than scattered throughout my code.

I don't know if that approach is feasible in your case, but I've found it greatly reduces the chances of a bug like this making it into production.