"Atsuo Ishimoto" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
| Yes. My question is "Which do you feel comfortable, printing collect
| glyphs or hex-escaped ASCII ?". I prefer printed glyphs for foreign
| characters, but I had feeling that western people prefer hex-escaped
| ASCII
On Fri, May 23, 2008 at 7:04 PM, Atsuo Ishimoto <[EMAIL PROTECTED]> wrote:
> On Sat, May 24, 2008 at 5:42 AM, Stephen J. Turnbull <[EMAIL PROTECTED]>
> wrote:
>> Atsuo Ishimoto writes:
>> > 2008/5/23 Guido van Rossum <[EMAIL PROTECTED]>:
>> > > Personally, I can live with it. I rarely generate J
On Sat, May 24, 2008 at 5:42 AM, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> Atsuo Ishimoto writes:
> > 2008/5/23 Guido van Rossum <[EMAIL PROTECTED]>:
> > > Personally, I can live with it. I rarely generate Japanese text so I
> > > doubt it'll be a problem. I can also change the console en
Atsuo Ishimoto writes:
> 2008/5/23 Guido van Rossum <[EMAIL PROTECTED]>:
> > Personally, I can live with it. I rarely generate Japanese text so I
> > doubt it'll be a problem. I can also change the console encoding and
> > error handler.
>
> While you rarely generate Japanese text, but I gue
2008/5/23 Guido van Rossum <[EMAIL PROTECTED]>:
> Personally, I can live with it. I rarely generate Japanese text so I
> doubt it'll be a problem. I can also change the console encoding and
> error handler.
While you rarely generate Japanese text, but I guess you often get
non-ASCII text data e.g.
On Fri, May 23, 2008 at 12:28 AM, Atsuo Ishimoto <[EMAIL PROTECTED]> wrote:
> On Fri, May 23, 2008 at 1:30 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
>>> One point still remains is default error handler for sys.stdout. I can
>>> live with 'strict' error handler, but I think raising exception
Hi,
while implementing Py_buffer support in Cython, I noticed (the hard way,
throught a segfault), that the buffer pointer passed into getbuffer() can be
NULL, e.g. when calling memoryview.tobytes(). According to PEP 3118 (first
paragraph below the getbuffer() signature), this implies setting a lo
paul bedaride wrote:
Hello,
I'm new on this list
The question you asked is more appropriate for comp.lang.python, not
python-dev/python-3000 (which are about the development *of* Python, not
development *with* Python).
Regards,
Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane,
On Fri, May 23, 2008 at 1:30 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>> One point still remains is default error handler for sys.stdout. I can
>> live with 'strict' error handler, but I think raising exceptions for
>> evenry un-supported characters by default is too exacting.
>
> I think t
Hello,
I'm new on this list and it's just for ask a question about class-style in
python 3000
because I don't understand for instance why in
class Example(object):
var1 = 'example'
var2 = property(fget=lambda self: 'example')
var1 seems to be linked to class and var2 to object.
In more i
Hello.
> The py3k branch has a major show stopper, It's leaking references to the
> max.
Is there any chance this leak also will be fixed?
http://bugs.python.org/issue
Thank you.
___
Python-3000 mailing list
Python-3000@python.org
http://mail.pytho
On Fri, 02 May 2008 00:03:24 - [EMAIL PROTECTED] wrote:
> On 11:45 pm, [EMAIL PROTECTED] wrote:
> >I like this, except one issue: I really don't like the .local
> >directory. I don't see any compelling reason why this needs to be
> >~/.local/lib/ -- IMO it should just be ~/lib/. There's no nee
12 matches
Mail list logo
