On 06.03.2014 09:32, Daniel Stonier wrote:
>
> So back to my earlier question - is setting a queue size expensive in
> the python implementation? If there isn't a technical weakness there,
> then I'm all for a) warnings and a migration point sometime in the
> future - it wouldn't be very costly to mechanically search and destroy
> all rospy.Publisher instances in a ros workspace.
>
I agree. I would say a warning here should include a deprecation
warning. Even if actual removal of the old API cannot yet be scheduled
for j-turtle or k-turtle, deprecation seems to be the way to go.
_______________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
(text/plain)