Thank you for your feedback on this topic.
Based on your replies we have decided to let the "publish()" function print
a warning when being invoked without the keyword "queue_size".
The warning message itself will point to the wiki page about rospy
publishers for more information.
As any warning printed via Pythons warnings module it can be disabled with
an environment variable.
Since deprecation warnings are not printed by default we used a UserWarning
instead.
These changes will be done for "Indigo".
For future ROS distros we can revisit the decision if we should keep the
Indigo behavior or change the warning into an error or change the default
behavior.
Thank you,
- Dirk
On Sat, Mar 8, 2014 at 1:43 AM, Thibault Kruse <
kruset@in.tum.de> wrote:
> 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
>
_______________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
(text/plain)