CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=4.0.x 2018-08-09T20:29:30+00:00 2018-08-09T20:29:30+00:00 Scott Shawcroft scott@tannewt.org 2018-08-09T01:24:49+00:00 urn:sha1:96ebf5bc3fb455162286b9bc31e763f3c4f1c457 * Fix finding translations with escaped characters. * Add back \r to translations since its needed by screen. 2018-07-11T20:45:30+00:00 Dan Halbert halbert@halwitz.org 2018-07-11T20:45:30+00:00 urn:sha1:7c219600a246d8956d0b23ea3f5d125a820e6b6a 2018-04-04T15:11:26+00:00 Damien George damien.p.george@gmail.com 2018-04-04T15:11:26+00:00 urn:sha1:f1df86a0177c77769d73bc477570580b4f705acf The LHS passed to mp_obj_int_binary_op() will always be an integer, either a small int or a big int, so the test for this type doesn't need to include an "other, unsupported type" case. 2018-03-29T11:42:10+00:00 Jeff Epler jepler@unpythonic.net 2018-03-25T21:01:06+00:00 urn:sha1:a55988a547011c04978a1661325062397ef74110 .. turning this from an assertion failure into an exception: pow(1,1,0) 2017-11-24T03:48:23+00:00 Damien George damien.p.george@gmail.com 2017-11-24T02:04:24+00:00 urn:sha1:5e34a113eaaf736fb4f703a3ee0892e1705d0a63 Before this patch MP_BINARY_OP_IN had two meanings: coming from bytecode it meant that the args needed to be swapped, but coming from within the runtime meant that the args were already in the correct order. This lead to some confusion in the code and comments stating how args were reversed. It also lead to 2 bugs: 1) containment for a subclass of a native type didn't work; 2) the expression "{True} in True" would illegally succeed and return True. In both of these cases it was because the args to MP_BINARY_OP_IN ended up being reversed twice. To fix these things this patch introduces MP_BINARY_OP_CONTAINS which corresponds exactly to the __contains__ special method, and this is the operator that built-in types should implement. MP_BINARY_OP_IN is now only emitted by the compiler and is converted to MP_BINARY_OP_CONTAINS by swapping the arguments. 2017-10-04T01:37:50+00:00 Damien George damien.p.george@gmail.com 2017-10-04T01:37:50+00:00 urn:sha1:a3dc1b1957d2c96d7c60c2c629c95077b03488a1 Header files that are considered internal to the py core and should not normally be included directly are: py/nlr.h - internal nlr configuration and declarations py/bc0.h - contains bytecode macro definitions py/runtime0.h - contains basic runtime enums Instead, the top-level header files to include are one of: py/obj.h - includes runtime0.h and defines everything to use the mp_obj_t type py/runtime.h - includes mpstate.h and hence nlr.h, obj.h, runtime0.h, and defines everything to use the general runtime support functions Additional, specific headers (eg py/objlist.h) can be included if needed. 2017-09-17T21:06:43+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2017-09-17T21:06:43+00:00 urn:sha1:9dce823cfd0a9991350184f08a1373f3887134f4 This allows user classes to implement __abs__ special method, and saves code size (104 bytes for x86_64), even though during refactor, an issue was fixed and few optimizations were made: * abs() of minimum (negative) small int value is calculated properly. * objint_longlong and objint_mpz avoid allocating new object is the argument is already non-negative. 2017-09-07T21:10:10+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2017-09-07T21:10:10+00:00 urn:sha1:b8ee7ab5b988f424e34e778fe3a679710d675efa This is to allow to place reverse ops immediately after normal ops, so they can be tested as one range (which is optimization for reverse ops introduction in the next patch). 2017-09-07T07:55:43+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2017-09-07T07:55:43+00:00 urn:sha1:d4d1c45a553c6361a72053383f0fe242f05cad3d This is to allow to encode arithmetic operations more efficiently, in preparation to introduction of __rOP__ method support. 2017-08-29T03:16:30+00:00 Damien George damien.p.george@gmail.com 2017-08-29T03:04:01+00:00 urn:sha1:58321dd9854d71a96e5db2d361e0efc05d9de8cf The unary-op/binary-op enums are already defined, and there are no arithmetic tricks used with these types, so it makes sense to use the correct enum type for arguments that take these values. It also reduces code size quite a bit for nan-boxing builds.