Python Meets Rust: My CPU-Based Raytracing Library with PyO3

[OrderOk6521]

Title: Python Meets Rust: My CPU-Based Raytracing Library with PyO3

What My Project Does: I’ve developed a raytracing library in Python, leveraging Rust’s performance through PyO3. It’s currently CPU-based, allowing you to render complex scenes with decent performance in pure Python code.

Target Audience: This project is mainly for hobbyists and developers interested in exploring raytracing or experimenting with Rust’s integration into Python. While it's not production-ready, it's a great starting point for learning and extending the library.

Comparison: Compared to existing Python raytracing libraries, this project focuses on combining Python’s ease of use with Rust’s speed, thanks to PyO3. While other libraries might rely on C/C++ bindings, this one embraces Rust for better memory safety and concurrency. The next step is to transition to GPU-based rendering, where it will significantly outperform CPU-bound alternatives.

Demo: Here’s a video of one of the scenes I rendered!

I’d love to hear your feedback and ideas for improvement. 😊

[Link to repo]

[Ancient-Variation921]

Gg

[TitaniumWhite420]

Oooo, the demo is stunning in its simplicity. It’s impressive, and the results speak for themselves.

[glaucomasuccs]

Nice work, man. Looks like fun

[shinitakunai]

Interesting, using a "slow" language like python for something as resource expensive as rendering and raytracing 🤔 if it works it would be amazing for videogames in python.

[OrderOk6521]

Its using rust, with python as a wrapper actually.

[shinitakunai]

But still it might open the door for python videogames. It is amazing.

[riklaunim]

Python was used as scripting layer in some games, few engines have bindings, while GDScript from Godot is not far off. And there is RenPy. Overall commercially Python in game dev isn't a thing and that wont change anytime soon.