http://psf.upfronthosting.co.za/roundup/meta/issue274
___
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
Raymond Hettinger wrote:
> The problem is that a basic python pattern is now broken
> in a way that may not readily surface during testing.
>
> I'm wondering if there is something we can do to mitigate
> the issue in a general way. It bites that the venerable technique
> of tuple sorting has lost
MRAB wrote:
> Are there Unicode codepoints for smilies? I'm thinking of :-) for
> 'Accepted' and :-( for 'Rejected'. :-)
Yes there are, but we'd need to set the font size to 'humongous' to
see the smilies: ☹ ☺.
In py3k: print(chr(0x2639), chr(0x263a))
In trunk: print(unichr(0x2639), unichr(0x263a
Hi Henning,
henning.vonbargen wrote:
> How to build Python 2.6.2 on HP-UX Itanium with thread support?
[snip bit about python-list]
I can't give you directions, but if you can describe your issues I
might be able to help.
I'll respond in python-list, as I think this is OT for python-dev.
> Is H
Dino Viehland wrote:
> What about instead defining __argspec__ for built-in functions/method
> objects and allowing all the implementations to implement it? We could
> all agree to return:
>
> [
> (return_type, (arg_types,...)),
> (return_type, (arg_types,...)),
> ]
>
> Then inspect
anatoly techtonik wrote:
>
> It is impossible to edit roundup keywords and this takes away the
> flexibility in selecting bugs related to a module/function/test or
> some other aspect of development. For example, I need to gather all
> subprocess bugs in one query and things that won't be fixed in
Hi David,
wrote:
>
> It appears that one possibility of investigation into the development of a
> safety-critical variant of the python language
There is some interesting work related to a safety-critical variant of Python.
> would be to conduct run time
> error analysis of the source code that
Hi Martin,
"Martin v. Löwis" wrote:
> In this thread, I'd like to collect things that ought to be done
> but where Dirkjan has indicated that he would prefer if somebody else
> did it.
>
> So far, I have only one item: build identification. If you want to work
> on this, please either provide a pa
