[Python-ideas] PEP 3156/Tulip: Extensible EventLoop interface

[Richard Oudkerk]

On 06/02/2013 10:20pm, Paul Moore wrote:
> I just tried a build on Windows 7 64-bit with Python 3.3 (i.e., not a
> 3.4 checkout). I got a lot of these types of error as well. I also got
> a couple of genuine ones. One was a build problem - PY_ULONG_MAX
> doesn't exist. I changed it to ULONG_MAX which got the compile to work
> - but it may not be correct, I guess. The other was:
>
> ERROR: test_sock_accept (tulip.events_test.ProactorEventLoopTests)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>    File "C:\Work\Scratch\tulip\tulip\events_test.py", line 309, in
> test_sock_accept
>      conn, addr = self.event_loop.run_until_complete(f)
>    File "C:\Work\Scratch\tulip\tulip\base_events.py", line 104, in
> run_until_complete
>      return future.result()  # May raise future.exception().
>    File "C:\Work\Scratch\tulip\tulip\futures.py", line 148, in result
>      raise self._exception
>    File "C:\Work\Scratch\tulip\tulip\windows_events.py", line 132, in _poll
>      value = callback()
>    File "C:\Work\Scratch\tulip\tulip\windows_events.py", line 83, in
> finish_accept
>      listener.fileno())
> OSError: [WinError 10014] The system detected an invalid pointer
> address in attempting to use a pointer argument in a call
>
> Interestingly, I saw the same OSError occurring in some of the
> "ERROR:root:Accept failed" logging stuff.
>
> I don't know if that's of any use...

Thanks.

It should be fixed now, but I have not tested it on a 64 bit build.  (My 
64 bit setup seems to be all screwed up.)

-- 
Richard