wrapyfi icon indicating copy to clipboard operation
wrapyfi copied to clipboard

Python Wrapper for Message-Oriented and Robotics Middleware

Results 7 wrapyfi issues
Sort by recently updated
recently updated
newest added

When using the NativeObject publisher pattern in ZeroMQ, calling publish from multiple threads leads to message format corruption when another process is listening. Upon investigation, I found that ZeroMQ sockets...

enhancement
help wanted

The following is planned for Wrapyfi v0.5: **OS Support** - [ ] MacOS 10.14 Mojave **Plugins** - [ ] [MLX Tensor](https://ml-explore.github.io/mlx/build/html/index.html) (exclusive to MacOS) - [ ] [Gmpy 2 MPZ](https://gmpy2.readthedocs.io/en/latest/)...

planned

MQTT is a reliable PUB/SUB protocol that is commonly used in industrial IoT. A server/client (REQ/REP) communication pattern will **not be supported**. Will rely on paho-mqtt in Python for initial...

help wanted

Currently, ROS messages (std_msgs, geometry_msgs ..., + custom message types following the ROS topic/package mapping convention) can be published and received using ROS by setting the data structure to ROSMessage....

enhancement

Allow classes/structs to be passed across middleware. The serializer would need to be modified to do something similar to [jsonpickle](https://jsonpickle.github.io/), however, jsonpickle is unsafe since it executes scripts. Find a...

enhancement
help wanted

Wrapify restricts the decorator to methods defined within classes. There are no technical limitations as to why this isn't possible. However, Wrapify maintains the properties for each class independently, to...

help wanted

`should_wait` should wait for all messages, and when multiple returns are expected by the reemit message, the ZeroMQ (like all other middleware) should also wait for all the messages to...

bug