>> So is having mutable bytes just a matter of calling them "byte >> displays" instead of "byte literals" or does that also require >> changing something in the back end? Martin> It's certainly also an issue of language semantics (i.e. changes Martin> to interpreter code). There are a number of options: Martin> 1. don't support creation of byte values through syntax. Instead, Martin> create bytes through a constructor function. I don't read the py3k mailing list. I presume the distinction between "display" and "literal" is old hat to those folks. I've never seen the term. Can someone explain it? Thx, Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4