Question: Compiling for Python 3.11 and Source of .so files

[renhong-zhang]

Hi Taccel Team,

First off, great work on the simulator! I'm trying to integrate it into my existing workflow which uses a Python 3.11 environment.

I've followed the installation instructions, but I noticed that the warp_ipc directory contains shared object (.so) files compiled specifically for Python 3.10:

warp_ipc/collision_detection.cpython-310-x86_64-linux-gnu.so
warp_ipc/ipc_integrator.cpython-310-x86_64-linux-gnu.so
warp_ipc/sim_model.cpython-310-x86_64-linux-gnu.so

This will cause an ImportError in my Python 3.11 environment.

My questions are:

1. Are the sources for these .so files open-sourced?
2. If so, where can I find them in the repository so I can try to recompile them for Python 3.11?

Thank you for your help!

[renhong-zhang]

Also, I've noticed that the setup.py script, specifically in the generate_stubs function, deletes the original .py files from warp_ipc/ after they are compiled by Cython.

# setup.py -> generate_stubs()
os.remove(f"warp_ipc/{fname_noext}.py")

This behavior makes it difficult to switch between Python environments or recover from a failed build, as the source Python files required for compilation are removed from the source directory itself when using an editable install (pip install -e .).

Could you consider making the deletion of the source .py files optional, perhaps controlled by an environment variable? This would greatly improve the development and multi-environment user experience. Thanks for your consideration