The only place we use SWIG is for exposing wxWidgets controls to Python, because we have to use SWIG for that.  In general our experience with SWIG hasn&#39;t been very good, so any Python bindings are likely to be either through Boost.Python or the straight-C Python API.<div>

<br></div><div>Josh<br><br><div class="gmail_quote">On Fri, Jan 7, 2011 at 12:43 PM, Travis Deyle <span dir="ltr">&lt;<a href="mailto:beambot@gmail.com">beambot@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

I noticed a (new?) rosbuild directive: rosbuild_add_swigpy_library<br><br>After some searches through the ros-users archive and <a href="http://ros.org" target="_blank">ros.org</a> wiki, I haven&#39;t seen any major examples of its use.  Has anyone tried to SWIG some of the more mature libraries / stacks?  At the moment, I&#39;m particularly interested in the costmap_2d and trajectory_planner libraries, but wanted to hear about others&#39; mileage before falling down a rabbit hole chasing after heavy class-based SWIG wrapping.<br>


<br>Question to the WG ROS core developers: are python / SWIG bindings to core libraries on the roadmap? <br clear="all"><font color="#888888"><br>~Travis Deyle<br>
PhD student @ Georgia Tech&#39;s Healthcare Robotics Lab<br>
Co-Founder <a href="http://www.Hizook.com" target="_blank">www.Hizook.com</a> -- Robotics News for Academics &amp; 
Professionals<br>
</font><br>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
<br></blockquote></div><br></div>