On 19/12/2010 00:31, Martin v. Löwis wrote:
Am 18.12.2010 19:26, schrieb MRAB:
On 18/12/2010 09:26, Martin v. Löwis wrote:
Comments?
How do you implement that? In particular, how do you retrieve
information for different locales in a single program?
The locale module would be able
I had a thought about locale-specific formatting.
Currently, when we want to do locale-specific formatting we use the
locale module like this:
locale.format(%d, 12345, grouping=False)
'12345'
locale.format(%d, 12345, grouping=True)
'12,345'
This makes it harder to use more than one locale at
On 09/12/2010 05:57, Alexander Belopolsky wrote:
On Thu, Dec 9, 2010 at 12:47 AM, Martin v. Löwismar...@v.loewis.de wrote:
..
However, in Python 3.2b1 the library python32.lib contains only
_PyUnicode_IsWhitespace, therefore breaking the build.
Is this change intentional? If so, why does
On 09/12/2010 23:35, Daniel Stutzbach wrote:
On Wed, Dec 8, 2010 at 6:56 PM, MRAB pyt...@mrabarnett.plus.com
mailto:pyt...@mrabarnett.plus.com wrote:
Is this change intentional? If so, why does unicodeobject.h still do
the mapping?
In 3.2b1, unicodeobject.h doesn't map
The regex module calls _PyUnicode_IsWhitespace, which is mapped by
unicodeobject.h to either _PyUnicodeUCS2_IsWhitespace or
_PyUnicodeUCS4_IsWhitespace.
From Python 2.5 to Python 3.1 the library pythonXX.lib contains either
_PyUnicodeUCS2_IsWhitespace or _PyUnicodeUCS4_IsWhitespace.
However, in
I can't get http://pypi.python.org and I've double-checked using
http://downforeveryoneorjustme.com/.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
It looks like the bug tracker is down.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
anatoly techtonik wrote:
On Thu, Jul 8, 2010 at 10:52 PM, MRAB pyt...@mrabarnett.plus.com wrote:
Hi all,
I re-implemented the re module, adding new features and speed
improvements. It's available at:
http://pypi.python.org/pypi/regex
under the name regex so that it can be tried alongside
Collin Winter wrote:
On Fri, Jul 9, 2010 at 10:28 AM, MRAB pyt...@mrabarnett.plus.com wrote:
anatoly techtonik wrote:
On Thu, Jul 8, 2010 at 10:52 PM, MRAB pyt...@mrabarnett.plus.com wrote:
Hi all,
I re-implemented the re module, adding new features and speed
improvements. It's available
Hi all,
I re-implemented the re module, adding new features and speed
improvements. It's available at:
http://pypi.python.org/pypi/regex
under the name regex so that it can be tried alongside re.
I'd be interested in any comments or feedback. How does it compare with
re in terms of speed
Nick Coghlan wrote:
On Fri, Jul 9, 2010 at 5:52 AM, MRAB pyt...@mrabarnett.plus.com wrote:
Hi all,
I re-implemented the re module, adding new features and speed
improvements. It's available at:
http://pypi.python.org/pypi/regex
under the name regex so that it can be tried alongside re
Nick Coghlan wrote:
On Fri, Jul 9, 2010 at 7:54 AM, MRAB pyt...@mrabarnett.plus.com wrote:
You should be able to replace:
import re
with:
import regex as re
and still have everything work the same, ie it's backwards compatible
with re.
That's not what I'm asking. I'm asking what
Amaury Forgeot d'Arc wrote:
2010/4/4 MRAB pyt...@mrabarnett.plus.com:
I've just downloaded the daily snapshot at
http://svn.python.org/snapshots/python.tar.bz2
In the header file /python/Modules/unicodedata_db.h, there are the
following lines in the change_records_3_2_0 struct:
{ 255
I've just downloaded the daily snapshot at
http://svn.python.org/snapshots/python.tar.bz2
In the header file /python/Modules/unicodedata_db.h, there are the
following lines in the change_records_3_2_0 struct:
{ 255, 255, 255, 255, 1.0 },
{ 255, 255, 255, 255, 2.0 },
{
I've thought of a possible additional feature for my regex module and
I'm looking for opinions.
Occasionally there's a question about matching multiple regexes and
someone might suggest combining them into one regex using |.
The feature would be to allow regex.compile, etc, to accept a list or
Vlastimil Brom wrote:
Vlastimil Brom vlastimil.b...@gmail.com added the comment:
I just tested the fix for unicode tracebacks and found some possibly weird
results (not sure how/whether it should be fixed, as these inputs are indeed
rather artificial...).
(win XPp SP3 Czech, Python 2.6.4)
Vitor Bosshard wrote:
2010/1/31 Georg Brandl g.bra...@gmx.net:
foo.py
foo.pyr/
cpython-25.pyc
cpython-25U.pyc
cpython-27.pyc
cpython-27U.pyc
cpython-32.pyc
unladen-011.pyc
wpython-11.pyc
+1. It should be quite easy to assign a new name every time the magic
number is updated.
Reid Kleckner wrote:
On Sun, Jan 31, 2010 at 8:34 AM, Nick Coghlan ncogh...@gmail.com wrote:
That still leaves the question of what to do with __file__ (for which
even the solution in the PEP isn't particularly clean). Perhaps the
thing to do there is to have __file__ always point to the source
Silke von Bargen wrote:
That still leaves the question of what to do with __file__ (for which
even the solution in the PEP isn't particularly clean). Perhaps the
thing to do there is to have __file__ always point to the source file
and introduce a __file_cached__ that points to the
Ben Finney wrote:
Vitor Bosshard algor...@gmail.com writes:
foo.py
foo.pyc # 2.7 or 3.2
foo.27.pyc
foo.32.pyc
etc.
This is simpler and more logical than the current subfolder proposal,
as it is clear which version each file corresponds to. Python can use
all the magic values it wants, but
Martin v. Löwis wrote:
The only supported default encodings in Python are:
Python 2.x: ASCII
Python 3.x: UTF-8
Is this true?
For 3.x: yes. However, the default encoding is much less relevant in
3.x, since Python will never implicitly use the default encoding, except
when some C
Hi all,
I'm back on the regex module after doing other things and I'd like your
opinion on a number of matters:
Firstly, the current re module has a bug whereby it doesn't split on
zero-width matches. The BDFL has said that this behaviour should be
retained by default in case any existing
Terry Reedy wrote:
On 1/12/2010 5:10 PM, MRAB wrote:
Hi all,
I'm back on the regex module after doing other things and I'd like your
opinion on a number of matters:
Firstly, the current re module has a bug whereby it doesn't split on
zero-width matches. The BDFL has said that this behaviour
MRAB wrote:
Hi all,
I'm back on the regex module after doing other things and I'd like your
opinion on a number of matters:
Firstly, the current re module has a bug whereby it doesn't split on
zero-width matches. The BDFL has said that this behaviour should be
retained by default in case any
Lennart Regebro wrote:
On Mon, Jan 11, 2010 at 11:37, Walter Dörwald wal...@livinglogic.de wrote:
UTF-8 might be a good choice
No, fallback if there is no BOM should be the local settings, just as
fallback is today if you don't specify a codec.
I mean, what if you want to look for a BOM but
Lennart Regebro wrote:
On Mon, Jan 11, 2010 at 10:06, Martin v. Löwis mar...@v.loewis.de
wrote:
I know you are just looking for a compromise, but this shouldn't be
it: the PSF has deliberately stayed out of the actual Python
engineering, so the release that Benjamin makes is not done by the
PSF
Victor Stinner wrote:
Le vendredi 08 janvier 2010 05:21:04, Guido van Rossum a écrit :
(...)
(And yes, I know this happens. Doesn't mean we need to auto-guess by
default; there are lots of issues e.g. what should happen after
seeking to offset 0?)
I wrote a new version of my patch (version
Glenn Linderman wrote:
On approximately 1/8/2010 3:59 PM, came the following characters from
the keyboard of Victor Stinner:
Hi,
Thanks for all the answers! I will try to sum up all ideas here.
One concern I have with this implementation encoding=BOM is that if
there is no BOM it assumes
Guido van Rossum wrote:
I'm a little hesitant about this. First of all, UTF-8 + BOM is crazy
talk. And for the other two, perhaps it would make more sense to have
a separate encoding-guessing function that takes a binary stream and
returns a text stream wrapping it with the proper encoding?
Hi,
I've been wondering whether it's possible to release the GIL in the
regex engine during matching.
I know that it needs to have the GIL during memory-management calls, but
does it for calls like Py_UNICODE_TOLOWER or PyErr_SetString? Is there
an easy way to find out? Or is it just a case of
David Lyon wrote:
On Mon, Dec 28, 2009 at 1:15 AM, Tarek Ziade wrote:
This new operator removes the ambiguity the original proposal had,
without making it more
complex for common use cases. So if you dislike it, you will need to
propose something
else that also fixes the ambiguity we had.
Antoine Pitrou wrote:
David Lyon david.lyon at preisshare.net writes:
Requires a particular python version.
Requires-Python: 2.5:2.7
Why not drop ranges as well as operators and simply use commas?
The above would be rewritten as:
Requires-Python: 2.5, 2.6, 2.7
This would prevent the
Tarek Ziadé wrote:
On Mon, Dec 28, 2009 at 1:41 AM, Sridhar Ratnakumar
sridh...@activestate.com wrote:
[..]
Tarek,
I am a bit confused at the current proposal combined with the newly
introduced range operator.
Would Requires-Python: =2.5 include 2.5.4 or not?
=2.5 means any version that is
Ben Finney wrote:
Tarek Ziadé ziade.ta...@gmail.com writes:
On Mon, Dec 28, 2009 at 1:41 AM, Sridhar Ratnakumar
sridh...@activestate.com wrote:
Also, Requires-Python: 3 would include all 3.X versions, correct?
Correct, because, Requires-Python: 3 is equivalent to
Requires-Python: ~= 3 which
Martin v. Löwis wrote:
No application developer will quickly figure out what a tilde means. Maybe
it means 'roughly', but it requires too much thought and is ambiguous. 2.5
is not roughly 2.5.2. It is the same exactly.
Before we had : Requires-Python: 2.5, 2.6
That made much more sense. It was
Arfrever Frehtes Taifersar Arahesis wrote:
2009-12-28 02:17:22 Ben Finney napisał(a):
Tarek Ziadé ziade.ta...@gmail.com writes:
On Mon, Dec 28, 2009 at 1:41 AM, Sridhar Ratnakumar
sridh...@activestate.com wrote:
Also, Requires-Python: 3 would include all 3.X versions, correct?
Correct,
John Arbash Meinel wrote:
Roy Hyunjin Han wrote:
While debugging a network algorithm in Python 2.6.2, I encountered
some strange behavior and was wondering whether it has to do with some
sort of code optimization that Python does behind the scenes.
After initialization:
Terry Reedy wrote:
Tarek Ziadé wrote:
Hello,
On behalf of the Distutils-SIG, I would like to propose PEP 386 for
inclusion in the sdtlib, and have a final discussion here on
Python-dev.
http://www.python.org/dev/peps/pep-0386
Some English copy editor comments:
and it will optionally allow
Benjamin Peterson wrote:
2009/11/15 Michael Foord fuzzy...@voidspace.org.uk:
Well, personally I think it would be a good thing if this raised an
exception during bytecode compilation - but it would fall under the
moratorium and have to wait a few years.
It could probably be considered a bug,
Matthew Woodcraft wrote:
Steven D'Aprano st...@pearwood.info wrote:
Why do you think it is okay to combine the Disallow vote, without also
combining the Allow vote? Less than a third of the total votes are in
favour of disallowing comments, with two-thirds in favour of allowing
them.
I
Guido van Rossum wrote:
On Tue, Nov 3, 2009 at 9:35 AM, Guido van Rossum gu...@python.org wrote:
I've checked draft (!) PEP 3003, Python Language Moratorium, into
SVN. As authors I've listed Jesse, Brett and myself.
I haven't seen substantial opposition against the PEP -- in fact I
can't
David Bolen wrote:
[snip]
I think the other issue most likely to cause a perceived downtime
with the Windows build slave that I've had a handful of cases over the
past two years where the build slave appears to be operating properly,
but the master seems to just queue up jobs as if it were down.
Masklinn wrote:
On 11 Oct 2009, at 13:36 , Tarek Ziadé wrote:
On Sun, Oct 11, 2009 at 1:26 PM, Ben Finney
ben+pyt...@benfinney.id.au wrote:
Stephen J. Turnbull step...@xemacs.org writes:
Trimming can be a PITA if you're using a crummy MUA
How so? It merely requires the ability to navigate
Eric Smith wrote:
Vinay Sajip wrote:
BTW I sent Eric a private mail re. the 0o versus 0 issue, to see
if it was
worth raising an enhancement request on the bug tracker using O to
generate
compatible rendering for octals.
I didn't get your message, could you resend?.
I was thinking the same
Vinay Sajip wrote:
Thanks to
http://bugs.python.org/issue7077
I've noticed that the socket-based logging handlers - SocketHandler,
DatagramHandler and SysLogHandler - aren't Unicode-aware and can break in the
presence of Unicode messages. I'd like to fix this by giving these handlers an
Vinay Sajip wrote:
Raymond Hettinger python at rcn.com writes:
We should get one written. ISTM, every %-formatting
string is directly translatable to an equivalent {}-formatting string.
I'm not sure you can always get equivalent output from the formatting, though.
For example:
%0#8x %
Steven Bethard wrote:
I thought it might be useful for those who don't have time to read a
million posts to have a summary of what's happened in the formatting
discussion.
The basic problem is that many APIs in the standard library and
elsewhere support only %-formatting and not {}-formatting,
Mark Dickinson wrote:
On Sat, Oct 3, 2009 at 4:41 PM, Steven Bethard steven.beth...@gmail.com wrote:
I thought it might be useful for those who don't have time to read a
million posts to have a summary of what's happened in the formatting
discussion.
Definitely useful. Thanks for the
Antoine Pitrou wrote:
MRAB python at mrabarnett.plus.com writes:
Another possibility:
A StringFormat class with subclasses PercentStringFormat,
BraceStringFormat, and perhaps DollarStringFormat.
Or:
A StringFormat class with methods parse_percent_format,
parse_brace_format
Vinay Sajip wrote:
Brett Cannon brett at python.org writes:
Why don't we start something in the sandbox and see how far we can
get. If no one beats me to it I will add the directory some time today
and we can start hashing out the solution there.
I've done a first cut of a converter from
Terry Reedy wrote:
Steven Bethard wrote:
I thought it might be useful for those who don't have time to read a
million posts to have a summary of what's happened in the formatting
discussion.
definitely
The basic problem is that many APIs in the standard library and
elsewhere support only
Pascal Chambon wrote:
Hello
Below is a corrected version of the PEP update, adding the start/end
indexes proposition and fixing functions signatures. Does anyone
disagree with these specifications ? Or can we consider it as a target
for the next versions of the io module ?
I would have no
Pascal Chambon wrote:
Found in current io PEP :
Q: Do we want to mandate in the specification that switching between
reading and writing on a read-write object implies a .flush()? Or is
that an implementation convenience that users should not rely on?
- it seems that the only important
waqas ahmad wrote:
Hi,
I dont know it is the right place to post this question. I need help to
change one search code line . can you help me please.
here is my search method code:
search=re.compile(^#acl InternationalGroup.*\n, re.M).search(pagetext)
if search:
Janzert wrote:
Steven D'Aprano wrote:
On Thu, 24 Sep 2009 06:47:41 am Dino Viehland wrote:
So I am +1 on unified the message and +1 on using the does not
support indexing one.
I'd be +1 on the unified message as well - but it seems what that
message should be may be contentious (and quite a
Ben Finney wrote:
Steven D'Aprano st...@pearwood.info writes:
As far as I can see, in practice, people talk about obj[i] as the item
at index i, not the item at subscript i -- the term subscript in
this context seems to be rare to non-existent except for the error
message.
Presumably, the
Dino Viehland wrote:
Is there a reason or a rule by which CPython reports different error
message for different failures to subscript?
For example:
set()[2]
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: 'set' object does not support indexing
Pascal Chambon wrote:
Daniel Stutzbach a écrit :
On Sun, Sep 20, 2009 at 4:48 AM, Pascal Chambon
chambon.pas...@gmail.com mailto:chambon.pas...@gmail.com wrote:
*RawIOBase*.readinto(b: bytes) - int
bytes are immutable. The signature is:
*RawIOBase*.readinto(b: bytearray) - int
Your
[Oops! Hit Send to soon]
Pascal Chambon wrote:
Hello everyone
I'm currently working on a reimplementation of io.FileIO, which would
allow cross-platform file range locking and all kinds of other safety
features ; however I'm slightly stuck due to some specification
fuzziness in the IO docs.
James Y Knight wrote:
On Sep 18, 2009, at 3:55 PM, MRAB wrote:
I think that this should be an invariant:
0 = file pointer = file size
so the file pointer might sometimes have to be moved.
As for the question of whether 'truncate' should be able to lengthen a
file, the method name
James Y Knight wrote:
On Sep 2, 2009, at 6:15 AM, Rob Cliffe wrote:
So - the syntax restriction seems not only inconsistent, but
pointless; it doesn't forbid anything, but merely means we have to do
it in a slightly convoluted (unPythonesque) way. So please, Guido,
will you reconsider?
Jeff McAninch wrote:
Should be legal, right?, since syntax would be
expression except expression if exception
Dino Viehland wrote:
On option 1 is this legal then?
x = float(string) except float('nan') if some_check() else
float('inf') if ValueError
Thinking more about the syntax
Nick Coghlan wrote:
P.J. Eby wrote:
At 05:59 PM 8/5/2009 -0700, Raymond Hettinger wrote:
[Jeffrey E. McAninch, PhD]
I very often want something like a try-except conditional expression
similar
to the if-else conditional.
An example of the proposed syntax might be:
x = float(string) except
Dino Viehland wrote:
MRAB wrote:
Dino Viehland wrote:
On option 1 is this legal then?
x = float(string) except float('nan') if some_check() else float('inf') if
ValueError
Well, is this is legal?
try:
x = float(string)
except some_check():
x = float('nan
Nick Coghlan wrote:
Mark Hammond wrote:
On 5/08/2009 7:09 PM, Dirkjan Ochtman wrote:
I'm not sure how win32text will provide anything other than
performance degradation for non-Windows developers, but if there's
functionality to be had, I'm happy to mandate its use on every
platform.
I see
John Machin wrote:
Hi Matthew,
Your post in c.l.py about your re rewrite didn't mention where to report
bugs etc so I dug this address out of Google Groups ...
Environment: Python 2.6.2, Windows XP SP3, your latest (29 July) regex
from the Python bugtracker.
Problem is repeated calls of
Paul Moore wrote:
2009/7/27 Eric Pruitt eric.pru...@gmail.com:
Hello,
Since there was a bit of confusion last time, I'll start by saying I am
working on the subprocess.Popen module for Google Summer of Code. One of the
features I am implementing is a class so that a running process can stand
Steven D'Aprano wrote:
On Tue, 28 Jul 2009 03:21:30 am MRAB wrote:
What about stderr? You could add e if you want to read from it.
Read from stderr is just a read. Write to stderr is just a write.
The difference between reading stdout and stderr is not that you have
different modes
Sean Reifschneider wrote:
I'm mailing this to python-dev because I'd like feedback on the idea of
adding an re attribute to strings. I'm not sure if it's a good idea or
not yet, but I figure it's worth discussion. The module mentioned here
includes a class called restr() which allows you to
Terry Reedy wrote:
Dirkjan Ochtman wrote:
It needs to be decided where the hg repositories will live. I'd like
to propose to keep the hgwebdir instance at hg.python.org. This is an
accepted standard for many organizations, and an easy parallel to
svn.python.org. The 2.7 (trunk) repo might live
Stefan Behnel wrote:
s...@pobox.com wrote:
Aahz On Wed, Jul 01, 2009, Brett Cannon wrote:
Anything happen while I was gone that I should be aware of that is
not covered in a PEP?
Aahz Yes.
In particular, Brett, you probably didn't hear that the King of Pop died
last week.
Cameron Simpson wrote:
On 16Jun2009 02:18, MRAB pyt...@mrabarnett.plus.com wrote:
My itch is that peek() _feels_ like it should be look into the buffer
but actually can block and/or change the buffer.
Can block, but not if you don't want it too. You might just want to see
what, if anything
Cameron Simpson wrote:
On 16Jun2009 11:21, Greg Ewing greg.ew...@canterbury.ac.nz wrote:
Cameron Simpson wrote:
It seems like whenever I want to do some kind of opportunistic but
non-blocking stuff with a remote service
Do you actually do this with buffered streams?
Sure, in C, python and
Seo Sanghyeon wrote:
Exception for setting attributes of built-in type differs between
CPython and IronPython. This is not purely theoretical, as
zope.interface tries to set Implements declaration as __implemented__
attribute of built-in type object, and excepts TypeError.
Python 2.6.1
I've just noticed an oddity of the re module while looking at the
sources. I'll illustrate it below:
import re
p = re.compile(foo)
help(p.match)
Help on built-in function match:
match(...)
match(string[, pos[, endpos]]) -- match object or None.
Matches zero or more characters at the
Tarek Ziadé wrote:
On Sat, May 16, 2009 at 6:55 PM, P.J. Eby p...@telecommunity.com wrote:
1. Why ';' separation, instead of tabs as in PEP 262? Aren't semicolons a
valid character in filenames?
I am changing this into a tab. for now.
What about Antoine's idea about doing a quote() on the
Alexander Shigin wrote:
В Сбт, 16/05/2009 в 23:15 +0100, MRAB пишет:
FYI, on RISC OS '/' is a valid filename character and '.' is used as
the directory separator.
I'd probably say that TAB is s reasonable character to use, even
though it's OK in POSIX; after all, should anyone really be using
Glenn Linderman wrote:
On approximately 5/16/2009 11:58 AM, came the following characters from
the keyboard of P.J. Eby:
At 11:17 AM 5/16/2009 -0700, Glenn Linderman wrote:
On approximately 5/16/2009 9:55 AM, came the following characters
from the keyboard of P.J. Eby:
At 06:06 PM 5/16/2009
Antoine Pitrou wrote:
Hello,
Just food for thought here, but seeing how 3.1 is going to be a real featureful
schedule despite being released shortly after 3.0, wouldn't it make sense to
tighten future release planning a little? I was thinking something like doing a
major release every 12 months
Robert Brewer wrote:
There's a major change in functionality in the cgi module between Python
2 and Python 3 which I've just run across: the behavior of
FieldStorage.read_multi, specifically when an HTTP app accepts a file
upload within a multipart/form-data payload.
In Python 2, each part
Michael Foord wrote:
Nick Coghlan wrote:
Benjamin Peterson wrote:
A while ago, Guido declared that all special method lookups on
new-style classes bypass __getattr__ and __getattribute__. This almost
completely consistent now, and I've been working on patching up a few
incorrect cases. I've
Brett Cannon wrote:
On Thu, May 7, 2009 at 18:56, John Arbash Meinel
john.arbash.mei...@gmail.com mailto:john.arbash.mei...@gmail.com wrote:
Andrew Bennetts wrote:
Antoine Pitrou wrote:
Robert Kern robert.kern at gmail.com http://gmail.com writes:
Since one may have
Martin v. Löwis wrote:
Wouldn't renaming the existing surrogates handler be an incompatible
change, and thus inappropriate?
No - it's new in Python 3.1.
So what do you think about Antoine's proposal?
+1
Although it looks like it would be without the '-' for consistency with
existing error
Walter Dörwald wrote:
Michael Urman wrote:
[...]
Well, there is a way to stack error handlers, although it's not pretty:
[...]
codecs.register_error(surrogates_then_replace,
surrogates_then_replace)
That mitigates my arguments significantly, although I'd rather see
Terry Reedy wrote:
Martin v. Löwis wrote:
Given your explanation of what the new 'surrogates' handler does (pass
rather than reject erroneous surrogates), I think 'surrogates_pass' is
fine. Thus, I considoer that and 'surrogates_excape' the best proposal
the best so far and suggest that you
M.-A. Lemburg wrote:
Martin v. Löwis wrote:
The name utf8b suggested in the PEP is not in line with the codec
design
Where is that design documented, and how exactly violates the name
the design (chapter and verse, please).
Martin, I designed the whole Python codec machinery, so even if
this
Antoine Pitrou wrote:
Martin v. Löwis martin at v.loewis.de writes:
Despite there being also an error handler called surrogates.
People, perhaps we could end all the bikeshedding and call one of those handlers
surrogates-pass and the other surrogates-escape, which sounds quite faithful
to
Stephen J. Turnbull wrote:
Martin v. Löwis writes:
I've updated the PEP accordingly.
I have three substantive comments. First, although consequences for
Python 3 byte interfaces (ie, none) are explicitly stated, as far as
I can see this PEP could apply to Python 2 as well. I don't think
Stephen J. Turnbull wrote:
MRAB writes:
I don't think people shouldn't be using non-ASCII-compatible
encodings for locale encodings is a sufficient rationale for a hard
error here. I mean, of course they *should* be using UTF-8. Maybe
Python 3.1 should just go ahead and error
Alexander Belopolsky wrote:
..
leaving just 'Rejected' and 'Replaced' to be disambiguated.
'X' or 'Z' for Rejected? Looks like a perfect start for a bikeshed
discussion. :-)
Are there Unicode codepoints for smilies? I'm thinking of :-) for
'Accepted' and :-( for 'Rejected'. :-)
I've just noticed an oddity in the key in PEP 0. Most letters are used
more than once. Wouldn't it be clearer if different letters were used
for Accepted and Active instead of them both being 'A', for example?
- A - Accepted proposal
- R - Rejected proposal
W - Withdrawn proposal
- D -
Zooko O'Whielacronx wrote:
Following-up to my own post to correct a major error:
On Thu, Apr 30, 2009 at 11:44 PM, Zooko O'Whielacronx zoo...@gmail.com wrote:
Folks:
My use case (Tahoe-LAFS [1]) requires that I am *able* to read arbitrary
binary names from the filesystem and store them so
Benjamin Peterson wrote:
2009/5/1 MRAB goo...@mrabarnett.plus.com:
I've just noticed an oddity in the key in PEP 0. Most letters are used
more than once. Wouldn't it be clearer if different letters were used
for Accepted and Active instead of them both being 'A', for example?
- A - Accepted
Michael Foord wrote:
MRAB wrote:
Benjamin Peterson wrote:
2009/5/1 MRAB goo...@mrabarnett.plus.com:
I've just noticed an oddity in the key in PEP 0. Most letters are used
more than once. Wouldn't it be clearer if different letters were used
for Accepted and Active instead of them both being
Martin v. Löwis wrote:
OK, so why not adopt the Mono solution in CPython? It seems to produce
valid unicode strings, removing at least one issue with PEP 383. It
also means that IronPython and CPython actually would be compatible.
See my other message. The Mono solution may not be what you
One further question: should the encoder accept a string like
u'\xDCC2\xDC80'? That would encode to b'\xC2\x80', which, when decoded,
would give u'\x80'. Does the PEP only guarantee that strings decoded
from the filesystem are reversible, but not check what might be de novo
strings?
Larry Hastings wrote:
Counting the votes for http://bugs.python.org/issue5799 :
+1 from Mark Hammond (via private mail)
+1 from Paul Moore (via the tracker)
+1 from Tim Golden (in Python-ideas, though what he literally said
was I'm up for it)
+1 from Michael Foord
+1 from
Barry Scott wrote:
On 30 Apr 2009, at 05:52, Martin v. Löwis wrote:
How do get a printable unicode version of these path strings if they
contain none unicode data?
Define printable. One way would be to use a regular expression,
replacing all codes in a certain range with a question mark.
James Y Knight wrote:
On Apr 28, 2009, at 2:50 AM, Martin v. Löwis wrote:
James Y Knight wrote:
Hopefully it can be assumed that your locale encoding really is a
non-overlapping superset of ASCII, as is required by POSIX...
Can you please point to the part of the POSIX spec that says that
Martin v. Löwis wrote:
Furthermore, I don't believe that PEP 383 works consistently on Windows,
What makes you say that? PEP 383 will have no effect on Windows,
compared to the status quo, whatsoever.
You could argue that if Windows is actually returning UTF-16 with half
surrogates that they
401 - 500 of 506 matches
Mail list logo
