Code: Select all
# Depending on how people use the
# client it might be prudent to revisit this decision and consider making these
# full fledged classes that are mutable.
What do you mean? namedtuple is part of core MicroPython. I started to code urequests (micro requests), but that was put on hold, as entire priority now on running ESP8266 KS campaign and coding for it.json, requests, collections/namedtuple. I don't think we have the last two in micropython-lib.
. But you know, we're realistic guys, and not talking about more stretch goals before current are met . (And indeed, there're many such services, and even deciding which one to support is a lot of time/effort (to review alternatives), and that conflicts with development).Didn't know that, apologies! And urequests sounds very exciting. Of course, the KS campaign will take off the majority of yours and Damiens time, as we all appreciate. Since there is a plethora of such platforms that provide cloud data collection and analysis, I don't think aiming to support one particular service is advantageous. Certainly our own platform would be amazing, but priorities are set right. Anyone else is free to write a library for any other cloud service that's out there, but with all the maintenance and transitions from upstream beta and any API changes should be taken into account.pfalcon wrote:What do you mean? namedtuple is part of core MicroPython.