New release

[paulkorir]

Hi, Any chance of getting an release that includes all new changes in master? P

[mcfletch]

I've pushed a new release, hope that helps.

[hernot]

Hi @mcfletch it doesn't as it just adds Python 10 support and does not change the fact that simpleparse is less usable and has less value to Python3 than it had for Python2 which is a pitty. Especially as there are plenty of pull-requests (#15) pending which reflect the fact that Python3 distinguishes between strings (uft8 only) and binary strings. Currently simple parse throws an Exceptoin when trying to parse a binary string even though underlying mtexttools would allow to parse them. The reason is that the grammar for simpleparse grammar parser is in str (utf8) and thus the grammar parser refuses to parse bytes type grammar strings which would be required to safely parse bytes type data strings. And decoding bytes to str is not in all cases possible. Especially when strings represent data files. Not all of them have a strict separation between Header and Data section. There are plenty out where both is intermixed causing either UTF8DecdingError exception or corrupt data.

So the question here is. Do you see any chance that in the last weeks of this year will have some to review all the open pullrequests close those which are meanwhile obsolete and provide advise how to proceed for the other (eg. #15). I would in extension to that have also suggestions on how to extend binary parsing capabilities of simple parse to any type of byte/memory (memorymaps, bytearrays, etc. ) contiguous binary data production and bytes type strings