QUERY · ISSUE

network: status codes/constants not unified across ports

openby msetinaopened 2023-04-24updated 2023-11-10

bug

Working with latest builds (20230422-unstable-v1.19.1-1019) of micropython I found some discrepancies:
ESP32 generic does not have STAT_CONNECT_FAIL in network module.
I noticed that status code value for connecting is 1 in rp2w and 1001 in ESP32.
If we should use constants from documentation then they should be implemented in all ports (please).

Some examples use codes (which is bad) that means they do not work correctly over ports

CANDIDATE · ISSUE

Pyboard D network module station interface: please implement STAT_CONNECTING

openby peterhinchopened 2019-04-08updated 2019-04-12

port-stm32

When calling the station interface connect method there is a need to verify whether the connection succeeded. On ESP8266 and ESP32 this can be done with

while s.status() == network.STAT_CONNECTING:  # Break out on fail or success.
    await asyncio.sleep(1)
if s.isconnected():
    #

Currently the only way seems to be to poll s.isconnected() with an arbitrary timeout.

Assessment

S Sonnet · high

Both issues concern missing or inconsistent network status constants across MicroPython ports, sharing the same root problem (network module constants not unified cross-port). However, they target different ports and different constants: #4682 requests STAT_CONNECTING on STM32/Pyboard D, while #11325 covers ESP32 missing STAT_CONNECT_FAIL and numeric value divergence between ESP32 and RP2W. Neither issue resolves the other — fixing STM32 does not address ESP32/RP2W inconsistencies, and vice versa.

Suggested action

Cross-reference these issues as part of the same broader network constants unification effort. Consider linking them in a tracking issue or milestone for network module cross-port consistency. Neither should be closed as a result of the other.

network: status codes/constants not unified across ports

Pyboard D network module station interface: please implement STAT_CONNECTING

Keyboard