summaryrefslogtreecommitdiff
path: root/tests/basics/bytes.py
AgeCommit message (Collapse)Author
2018-02-19py/objstr: Protect against creating bytes(n) with n negative.Damien George
Prior to this patch uPy (on a 32-bit arch) would have severe issues when calling bytes(-1): such a call would call vstr_init_len(vstr, -1) which would then +1 on the len and call vstr_init(vstr, 0), which would then round this up and allocate a small amount of memory for the vstr. The bytes constructor would then attempt to zero out all this memory, thinking it had allocated 2^32-1 bytes.
2017-10-04py/objstr: Make empty bytes object have a null-terminating byte.Damien George
Because a lot of string processing functions assume there is a null terminating byte, so they can work in an efficient way. Fixes issue #3334.
2015-04-04tests: Add tests to exercise lexer; and some more complex number tests.Damien George
2015-03-14tests: Add some more tests for bytes, bignum, string and ujson.Damien George
2015-01-28tests: Add testcase for bytes() on values in range 128-255.Paul Sokolovsky
2014-09-23tests: Fix uctypes tests to run on 64bit arch; enable more native tests.Damien George
2014-08-11objstr: Make sure that bytes are indexed as bytes, not as unicode.Paul Sokolovsky
Fixes #795.
2014-03-22py: Make 'bytes' be a proper type, support standard constructor args.Paul Sokolovsky
2014-01-24Add basic implementation of bytes type, piggybacking on str.Paul Sokolovsky
This reuses as much str implementation as possible, from this we can make them more separate as needed.