UNIX build missing socket.sendall() method
Port, board and/or hardware
UNIX
MicroPython version
$ micropython
MicroPython v1.24.1 on 2025-02-24; linux [GCC 14.2.1] version
Use Ctrl-D to exit, Ctrl-E for paste mode
>>> import socket
>>> s = socket.socket()
>>> dir(s)
['__class__', 'close', 'read', 'readinto', 'readline', 'send', 'write', 'accept', 'bind', 'connect', 'fileno', 'listen', 'makefile', 'recv', 'recvfrom', 'sendto', 'setblocking', 'setsockopt', 'settimeout']
>>>
Regarding to documentation, sendall is supported. On ESP32 build it is available
MicroPython v1.24.1 on 2024-11-29; Generic ESP32 module with ESP32
Type "help()" for more information.
>>>
>>> import socket
>>> s = socket.socket()
>>> dir (s)
['__class__', 'close', 'read', 'readinto', 'readline', 'send', 'write', '__del__', 'accept', 'bind', 'conn
ect', 'fileno', 'listen', 'makefile', 'recv', 'recvfrom', 'sendall', 'sendto', 'setblocking', 'setsockopt'
, 'settimeout']
Unix build was created by using AUR package https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=micropython
Reproduction
Build unix version of uPy
import socket
try to call sendall(packet)
Expected behaviour
Method will be there, so do not need rewrite libraries just for one port
Observed behaviour
what is this ?
Additional Information
No, I've provided everything above.
Code of Conduct
Yes, I agree
RP2350 fileno missing
Port, board and/or hardware
Raspberry Pi Pico 2 W with RP2350
MicroPython version
MicroPython v1.27.0 on 2025-12-09; Raspberry Pi Pico 2 W with RP2350
Reproduction
dir on socket in esp32:
['class', 'close', 'read', 'readinto', 'readline', 'send', 'write', 'del', 'accept', 'bind', 'connect', 'fileno', 'listen', 'makefile', 'recv', 'recvfrom', 'sendall', 'sendto', 'setblocking', 'setsockopt', 'settimeout']
dir on socket in RP2350:
['class', 'close', 'read', 'readinto', 'readline', 'send', 'write', 'del', 'accept', 'bind', 'connect', 'listen', 'makefile', 'recv', 'recvfrom', 'sendall', 'sendto', 'setblocking', 'setsockopt', 'settimeout']
--> fileno missing
Expected behaviour
providing IP address
Observed behaviour
Exception
Additional Information
No, I've provided everything above.
Code of Conduct
Yes, I agree