CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=5.3.0 2017-09-06T03:40:51+00:00 2017-09-06T03:40:51+00:00 Damien George damien.p.george@gmail.com 2017-09-06T03:40:51+00:00 urn:sha1:01dd7804b87d60b2deab16712eccb3b97351a9b7 This is to keep the top-level directory clean, to make it clear what is core and what is a port, and to allow the repository to grow with new ports in a sustainable way. 2017-07-31T08:35:40+00:00 Alexander Steffen devel.20.webmeister@spamgourmet.com 2017-06-30T07:22:17+00:00 urn:sha1:55f33240f3d7051d4213629e92437a36f1fac50e There were several different spellings of MicroPython present in comments, when there should be only one. 2017-07-18T01:57:39+00:00 Alexander Steffen devel.20.webmeister@spamgourmet.com 2017-06-29T21:14:58+00:00 urn:sha1:299bc625864b9e624ed599c94a5f95870516139a The code conventions suggest using header guards, but do not define how those should look like and instead point to existing files. However, not all existing files follow the same scheme, sometimes omitting header guards altogether, sometimes using non-standard names, making it easy to accidentally pick a "wrong" example. This commit ensures that all header files of the MicroPython project (that were not simply copied from somewhere else) follow the same pattern, that was already present in the majority of files, especially in the py folder. The rules are as follows. Naming convention: * start with the words MICROPY_INCLUDED * contain the full path to the file * replace special characters with _ In addition, there are no empty lines before #ifndef, between #ifndef and one empty line before #endif. #endif is followed by a comment containing the name of the guard macro. py/grammar.h cannot use header guards by design, since it has to be included multiple times in a single C file. Several other files also do not need header guards as they are only used internally and guaranteed to be included only once: * MICROPY_MPHALPORT_H * mpconfigboard.h * mpconfigport.h * mpthreadport.h * pin_defs_*.h * qstrdefs*.h 2017-02-22T00:29:19+00:00 Damien George damien.p.george@gmail.com 2017-02-22T00:05:27+00:00 urn:sha1:85ab469c64420d4c11c946efd17ddaea57b19278 It saves about 400 bytes of code space because the functions can now be inlined. 2016-02-21T21:01:18+00:00 danicampora daniel@wipy.io 2016-02-21T20:28:19+00:00 urn:sha1:495e7cfebce63d0168852269f279c24373abdd3a 2015-09-26T23:50:52+00:00 Daniel Campora daniel@wipy.io 2015-09-26T20:55:24+00:00 urn:sha1:57fa14b5be08736b37f1629475e47c92556c0629 2015-09-26T23:48:20+00:00 Daniel Campora daniel@wipy.io 2015-09-22T21:20:29+00:00 urn:sha1:dbdcb58d6413a907e5f4aed25eee85073ff7e575 2015-08-09T17:22:12+00:00 Daniel Campora daniel@wipy.io 2015-08-05T11:36:29+00:00 urn:sha1:00c4d6562ec2dbb494e9c26dce86f99f95a82d70 Changes are based on this post: https://github.com/micropython/micropython/issues/876#issuecomment-115255551 The constructor can optionally take the same params of iwconfig in order to configure WiFi when creating the object. Params are keyworkd only. The WiPy accepts: - mode (int -> WLAN.AP or WLAN.STA) - ssdi (string) - security (int -> WLAN.OPEN, WLAN.WEP, WLAN.WPA, WLAN.WPA2) - key (string) - channel (int (1-11)) - antenna (int -> WLAN.INTERNAL, WLAN.EXTERNAL) 2015-07-29T22:43:16+00:00 Daniel Campora daniel@wipy.io 2015-07-28T21:50:22+00:00 urn:sha1:aa58c7ec74e00f9dd652a1b56e2a7f8ae4b615da 2015-07-10T09:37:48+00:00 Daniel Campora daniel@wipy.io 2015-07-10T08:15:11+00:00 urn:sha1:ecb7f9fe581b746338b351415cf7bc0e3803cab6