On 12/20/07, Ross Cohen <[EMAIL PROTECTED]> wrote:
>
> On Thu, Dec 20, 2007 at 06:08:47PM +0100, Christian Heimes wrote:
>
> > I've written wrappers for both mechanisms. Both wrappers are inspired
> > from Twisted and select.poll()'s API. The interface is more Pythonic
> > than the available wrappe
I am unable to reproduce this in windows with:
Python 3.0a2 (py3k:59584M, Dec 20 2007, 16:24:12) [MSC v.1500 32 bit
(Intel)] on win32
Running the test via rt and in isolation does not appear to fail. In
isolation produces 16 OKs.
Joe
On Dec 20, 2007 3:58 PM, Guido van Rossum <[EMAIL PROTECTED]
When I build from scratch and run most tests (regrtest.py -uall) I get
some strange failures with test_sys.py:
test test_sys failed -- Traceback (most recent call last):
File "/usr/local/google/home/guido/python/py3kd/Lib/test/test_sys.py",
line 302, in test_43581
self.assertEqual(sys.__stdo
On Thu, Dec 20, 2007 at 06:08:47PM +0100, Christian Heimes wrote:
> I've written wrappers for both mechanisms. Both wrappers are inspired
> from Twisted and select.poll()'s API. The interface is more Pythonic
> than the available wrappers and it reduced the burden on the user. The
> users don't ha
Linux Kernel 2.6+ and BSD (including Mac OS X) have two I/O event
notification systems similar but superior to select() and poll(). From
the manuals:
kqueue, kevent -- kernel event notification mechanism
The kqueue() system call provides a generic method of notifying the user
when an event happen
Quentin Gallet-Gilles wrote:
> Has someone already encountered this ?
Without any version numbers, it's hard to say. More recent versions of
Python don't assume LC_NUMERIC is set to the C locale, but older
versions did.
Cheers,
Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Au
While testing the tkFileDialog, I encountered a strange error :
~/dev/trunk$ ./python Lib/lib-tk/tkFileDialog.py
Traceback (most recent call last):
File "Lib/lib-tk/tkFileDialog.py", line 202, in
openfilename=askopenfilename(filetypes=[("all files", "*")])
File "Lib/lib-tk/tkFileDialog.py
Raymond Hettinger wrote:
> The bots are kicking-off so many false alarms that it is becoming
> difficult to tell whether a check-in genuinely broke a build.
It would also be nice if the checkins list only got spammed for actual
compile or test failures. I'm not all that interested in getting an
