A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2007-May/073013.html below:

[Python-Dev] Changing string constants to byte arrays in Py3k

[Python-Dev] Changing string constants to byte arrays in Py3k [Python-Dev] Changing string constants to byte arrays in Py3kskip at pobox.com skip at pobox.com
Sun May 6 14:09:31 CEST 2007
    >> 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
More information about the Python-Dev mailing list

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