Bengt Richter wrote:
on tracking the encodings of literal generated astrings
The big problem you'll hit is figuring out how to use these strings.
Which string ops preserve the encoding? Even the following is
problematic:
#-*- coding: utf-8 -*-
name = 'Martin Löwis'
brokenpart =
Bengt Richter wrote:
Others reject it because of semantic difficulties: how would such
strings behave under concatenation, if the encodings are different?
I mentioned that in parts you snipped (2nd half here):
This could also support s1+s2 to mean generate a concatenated string
that has the
Bengt Richter wrote:
Well, what will be assumed about name after the lines
#-*- coding: latin1 -*-
name = 'Martin Löwis'
?
Are you asking what is assumed about the identifier 'name', or the value
bound to that identifier? Currently, the identifier must be encoded in
latin1 in this
On Tue, 18 Oct 2005 01:34:09 +0200, =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=
[EMAIL PROTECTED] wrote:
Bengt Richter wrote:
Well, what will be assumed about name after the lines
#-*- coding: latin1 -*-
name = 'Martin Löwis'
?
Are you asking what is assumed about the identifier 'name',
Bengt Richter wrote:
Perhaps string equivalence in keys will be treated like numeric equivalence?
I.e., a key/name representation is established by the initial key/name
binding, but
values can be retrieved by equivalent key/names with different
representations
like unicode vs ascii or
On Sun, 16 Oct 2005 12:16:58 +0200, =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=
[EMAIL PROTECTED] wrote:
Bengt Richter wrote:
Perhaps string equivalence in keys will be treated like numeric equivalence?
I.e., a key/name representation is established by the initial key/name
binding, but
On Wed, 12 Oct 2005 10:56:44 +0200, =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=
[EMAIL PROTECTED] wrote:
Mike Meyer wrote:
Out of random curiosity, is there a PEP/thread/? that explains why
Python symbols are restricted to 7-bit ascii?
No PEP yet; I meant to write one for several years now.
Mike Meyer wrote:
Out of random curiosity, is there a PEP/thread/? that explains why
Python symbols are restricted to 7-bit ascii?
No PEP yet; I meant to write one for several years now.
The principles would be
- sources must use encoding declarations
- valid identifiers would follow the
Out of random curiosity, is there a PEP/thread/? that explains why
Python symbols are restricted to 7-bit ascii?
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
--
I'm not aware of any PEPs on the subject, but google groups turns up some past
threads. Here's one from February 2004:
http://groups.google.com/group/comp.lang.python/browse_frm/thread/d5fcc1c8825a60dc/96856af647ce71d5
I didn't immediately find this message of Guido's that everyone's
Mike Meyer wrote:
Out of random curiosity, is there a PEP/thread/? that explains why
Python symbols are restricted to 7-bit ascii?
And of equally random curiosity :-), what alternative(s) can you suggest
would have been appropriate? (I note that Unicode, for example, dates
from around the
Hi !
I agree with you; I will adore capacity to call functions named in Unicode.
@-salutations
Michel Claveau
--
http://mail.python.org/mailman/listinfo/python-list
12 matches
Mail list logo
