Sending with padding can lead to integrity problems about pyudt HOT 2 OPEN

For the regular send() function, padding should be removed. As you mentioned it is not quite a good idea to manage the zero's myself since I must while loop on the original data. I would leave it for the sendmsg() function where the intent is to insure datagram packets are of a fixed size, however it might not even be all the particularly useful there.

If it's all the same to you, I might just remove it from everywhere and make sure buffer objects work as expected.

from pyudt.

Well it's up to you, if you really need padding on sendmsg() on the c++ end go for it. But why do you need fixed size ? With sendmsg() the message has boundaries and will always be as a whole either delivered or not so there is no need to loop over a fixed size to receive the message, it will be received as a whole by recvmsg(). And if the user ever wants to send fixed message sizes he can do a python loop to divide them into fixed sizes. But as I said, if for a particular reason you need it, keep it ;)

from pyudt.