M.-A. Lemburg writes:
> I'd use "allowlonesurrogates" as name for the "surrogates" error
> handler and "lonesurrogatereplace" for the "utf8b" one.
+1
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
On Fri, May 8, 2009 at 9:36 AM, Tarek Ziadé wrote:
> Hello,
>
> I am trying to refactor distutils.log in order to use logging but I
> have been bugged by the fact that site.py uses
> distutils.util.get_platform() in "addbuilddir".
> The problem is the order of imports at initialization time : impo
Andrew Bennetts wrote:
> Antoine Pitrou wrote:
>> Robert Kern gmail.com> writes:
>>> Since one may have more than one filesystem side-by-side, this can't be just
>> be
>>> a system-wide boolean somewhere. One would have to query the target
>>> directory
>>> for this information. I am not aware
On Fri, May 08, 2009, Tarek Ziad? wrote:
>
> This module can be used by site.py, by distutils, and others, and will
> focus on this role.
This should get kicked around on python-ideas; I don't think it will
require a full-blown PEP unless there's disagreement about what it should
contain.
--
Aahz
On approximately 5/7/2009 3:27 PM, came the following characters from
the keyboard of MRAB:
Terry Reedy wrote:
Martin v. Löwis wrote:
So I'm happy to make it "surrogatepass" and "surrogateescape" as
These seem adequate. It is not what I would choose or suggest, but it
is adequate, and it
Antoine Pitrou wrote:
> Robert Kern gmail.com> writes:
> >
> > Since one may have more than one filesystem side-by-side, this can't be just
> be
> > a system-wide boolean somewhere. One would have to query the target
> > directory
> > for this information. I am not aware of the existence of co
Hello,
I am trying to refactor distutils.log in order to use logging but I
have been bugged by the fact that site.py uses
distutils.util.get_platform() in "addbuilddir".
The problem is the order of imports at initialization time : importing
"logging" into distutils will make the initialization/bui
Robert Kern gmail.com> writes:
>
> Since one may have more than one filesystem side-by-side, this can't be just
be
> a system-wide boolean somewhere. One would have to query the target directory
> for this information. I am not aware of the existence of code that does such
a
> query, though.
On 2009-05-07 18:29, Brett Cannon wrote:
[my python-dev sabbatical is still in effect, so make sure I am at least
cc'ed on any replies to this email]
I cannot be the only person who has a need to run tests conditionally
based on whether the file system is case-sensitive or not, so I feel
like I
[my python-dev sabbatical is still in effect, so make sure I am at least
cc'ed on any replies to this email]
I cannot be the only person who has a need to run tests conditionally based
on whether the file system is case-sensitive or not, so I feel like I am
re-inventing the wheel for issue 5442 to
Martin v. Löwis wrote:
>> The error handler for undoing this operation (ie. when converting
>> a Unicode string to some other encoding) should probably use the
>> same name based on symmetry and the fact that the escaping
>> scheme is meant to be used for enabling round-trip safety.
>
> Could you
Tarek Ziadé wrote:
I have fixed configure by runing autoconf, everything should be fine now
And indeed, it's working fine now, thanks.
Sorry for the inconvenience.
Not a problem. Anyone who volunteers for autoconf work gets a free pass
from me.
Eric.
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 mak
On Thu, May 7, 2009 at 11:51 PM, Eric Smith wrote:
> Tarek Ziadé wrote:
>>
>> On Thu, May 7, 2009 at 11:36 PM, Eric Smith wrote:
>>>
>>> With you ARFLAGS change, I now get the following error on a 32 bit Fedora
>>> 6
>>> box. I've done "make distclean" and "./configure":
>>
>> Sorry yes, I am on
Eric Smith wrote:
Eric Smith wrote:
Neal Becker wrote:
"format_spec ::= [[fill]align][sign][#][0][width][.precision][type]"
"The precision is ignored for integer values."
In [36]: '%3x' % 10
Out[36]: ' a'
In [37]: '%.3x' % 10
Out[37]: '00a'
Apparently, precision is _not_ ignored?
That s
Tarek Ziadé wrote:
On Thu, May 7, 2009 at 11:36 PM, Eric Smith wrote:
With you ARFLAGS change, I now get the following error on a 32 bit Fedora 6
box. I've done "make distclean" and "./configure":
Sorry yes, I am on it now, the produced Makefile is broken, until then
you can change it
...
N
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 make this pair the curr
On Thu, May 7, 2009 at 11:36 PM, Eric Smith wrote:
> Tarek:
>
> With you ARFLAGS change, I now get the following error on a 32 bit Fedora 6
> box. I've done "make distclean" and "./configure":
Sorry yes, I am on it now, the produced Makefile is broken, until then
you can change it
<<< line 71
a
Tarek:
With you ARFLAGS change, I now get the following error on a 32 bit
Fedora 6 box. I've done "make distclean" and "./configure":
$ make
...
gcc -pthread -fno-strict-aliasing -g -Wall -Wstrict-prototypes -I.
-IInclude -I./Include -DPy_BUILD_CORE -I./Modules/_io -c
./Modules/_io/texti
On Thu, May 7, 2009 at 12:39 PM, "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 fa
> 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 make this pair the current status
> quo
Neal Becker wrote:
"format_spec ::= [[fill]align][sign][#][0][width][.precision][type]"
"The precision is ignored for integer values."
In [36]: '%3x' % 10
Out[36]: ' a'
In [37]: '%.3x' % 10
Out[37]: '00a'
Apparently, precision is _not_ ignored?
Apparent typo reports should go to the track
Eric Smith wrote:
Neal Becker wrote:
"format_spec ::= [[fill]align][sign][#][0][width][.precision][type]"
"The precision is ignored for integer values."
In [36]: '%3x' % 10
Out[36]: ' a'
In [37]: '%.3x' % 10
Out[37]: '00a'
Apparently, precision is _not_ ignored?
That section is talking a
Neal Becker wrote:
"format_spec ::= [[fill]align][sign][#][0][width][.precision][type]"
"The precision is ignored for integer values."
In [36]: '%3x' % 10
Out[36]: ' a'
In [37]: '%.3x' % 10
Out[37]: '00a'
Apparently, precision is _not_ ignored?
That section is talking about this:
>>> for
Martin v. Löwis wrote:
So are you proposing that I should rename the PEP 383 handler
to "utf_8b_encoder_invalid_codepoints"?
No, he's saying that your algorithm for choosing the PEP 383 handler
should have come up with that name, rather than utf8b. But since PEP
383 applies to other codecs bes
"format_spec ::= [[fill]align][sign][#][0][width][.precision][type]"
"The precision is ignored for integer values."
In [36]: '%3x' % 10
Out[36]: ' a'
In [37]: '%.3x' % 10
Out[37]: '00a'
Apparently, precision is _not_ ignored?
___
Python-Dev mailin
Walter Dörwald writes:
> "surrogatepass" (for the "don't complain about lone half surrogates"
> handler) and "surrogatereplace" sound OK to me. However the other
> "...replace" handlers are destructive (i.e. when such a "...replace"
> handler is used for encoding, decoding will not produce the
> The error handler for undoing this operation (ie. when converting
> a Unicode string to some other encoding) should probably use the
> same name based on symmetry and the fact that the escaping
> scheme is meant to be used for enabling round-trip safety.
Could you please familiarize yourself wit
> I haven't come up with anything I like better than errors="lenient"
> for the old utf8 behavior handler; would errors="nonvalidating" be
> correct?
I think either is fairly unspecific.
> For the utf8b error handler, I could see any of errors="roundtrip",
> errors="roundtripreplace", errors="tos
>> 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
> something like errors=('surrogates', 're
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
some
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
> something
On Thu, May 7, 2009 at 01:16, "Martin v. Löwis" wrote:
> I'm still at a loss what name to give it, though. I understand that
> I have to rename both error handlers, but I'm uncertain what I should
> rename them to. So proposals that rename only one of them aren't
> that helpful. It would be helpfu
On Thu, May 7, 2009 at 00:43, "Martin v. Löwis" wrote:
> Michael Urman wrote:
>> On Wed, May 6, 2009 at 15:42, "Martin v. Löwis" wrote:
>>> Despite there being also an error handler called "surrogates".
>>
>> Not that I have to be, but I'm not sold on the previous UTF-8 codec
>> behavior becoming
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
M.-A. Lemburg wrote:
> Antoine Pitrou wrote:
>> Martin v. Löwis v.loewis.de> writes:
>>> py> b'\xed\xa0\x80'.decode("utf-8","surrogates")
>>> '\ud800'
>> The point is, "surrogates" does not mean anything intuitive for an /error
>> handler/. You seem to be the only one who finds this name explicit
On behalf of the Python development team, I'm thrilled to announce the first and
only beta release of Python 3.1.
Python 3.1 focuses on the stabilization and optimization of features and changes
Python 3.0 introduced. For example, the new I/O system has been rewritten in C
for speed. File system
On Thu, May 7, 2009 at 2:11 PM, David Cournapeau wrote:
> But I don't know if that's easy to set up such as both python and
> numpy are built from sources.
I don't know about the numpy part, but the PyBots project code could
be a source of inspiration for the Python part
http://code.google.com/p
On Thu, May 7, 2009 at 8:49 PM, Tarek Ziadé wrote:
>
> Notice that from the beginning, the unixcompiler class options are
> never used if the option has been customized
> in distutils.sysconfig and present in the Makefile, so we need to
> clean this behavior as well at some point, and document
>
On Thu, May 7, 2009 at 1:37 PM, David Cournapeau wrote:
> On Thu, May 7, 2009 at 7:07 PM, Tarek Ziadé wrote:
>> On Thu, May 7, 2009 at 11:50 AM, David Cournapeau wrote:
>>> Then, in the customize_compiler function, set archiver to $AR +
>>> $ARFLAGS. IOW, just copying the logic used for e.g. lds
On Thu, May 7, 2009 at 11:50 AM, David Cournapeau wrote:
> Then, in the customize_compiler function, set archiver to $AR +
> $ARFLAGS. IOW, just copying the logic used for e.g. ldshared,
>
> I can prepare a patch if you want,
I am ok on Distutils side, but I wouldn't mind some help on the
makefil
On Wed, May 6, 2009 at 6:01 PM, Tarek Ziadé wrote:
> Hello,
>
> I need some help on http://bugs.python.org/issue5941
>
> The bug is quite simple: the Distutils unixcompiler used to set the
> archiver command to "ar -rc".
>
> For quite a while now, this behavior has changed in order to be able
> to
Antoine Pitrou wrote:
> Martin v. Löwis v.loewis.de> writes:
>> py> b'\xed\xa0\x80'.decode("utf-8","surrogates")
>> '\ud800'
>
> The point is, "surrogates" does not mean anything intuitive for an /error
> handler/. You seem to be the only one who finds this name explicit enough,
> perhaps because
On approximately 5/6/2009 11:16 PM, came the following characters from
the keyboard of Martin v. Löwis:
So are you proposing that I should rename the PEP 383 handler
to "utf_8b_encoder_invalid_codepoints"?
No, he's saying that your algorithm for choosing the PEP 383 handler
should have come up
44 matches
Mail list logo
