# Future library for python

**URL:** <https://discourse.openrobotics.org/t/future-library-for-python/48129>\
**Category:** Gazebo General\
**Created:** [February 6, 2025, 6:23pm UTC](https://discourse.openrobotics.org/t/future-library-for-python/48129 "2025-02-06T18:23:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kakcalu13](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/kakcalu13/32/26887_2.png) [@kakcalu13](https://discourse.openrobotics.org/u/kakcalu13)\
**Post date:** [February 6, 2025, 6:23pm UTC](https://discourse.openrobotics.org/t/future-library-for-python/48129/1 "2025-02-06T18:23:22Z")

</div>

I wanted to share this. I’m currently on Windows using WSL. I will re-test this on my Mac M2 and Linux (just to double-check).

I tried Python Transport, but it required too much work and effort. I needed to download, install dependencies, build from source, and even download binaries, etc. Then I had to specify Python paths and all that stuff - too much of a headache. So I’m making a free and open-source library for Python \<\> native Gazebo that works with any Python version (I hope)

Right now, I’m just fetching data using my yet-to-be-created library. I will share the GitHub repository maybe this weekend or in two weekends. I’m designing this for anyone who wants to just use Gazebo without using ROS2, Transport, or any heavy-duty work.

Here are the pending tasks:

1. I need to find a way to make it scalable and work with various topic.
2. I need to make it work with services, lists, topics, etc.
3. I need to ensure that all data is delivered as is.
4. I need to come up with an appropriate name for the library so anyone can use pip or easily Google for Gazebo + Python.

Look at this video using my own project and Gazebo api