[EMAIL PROTECTED] wrote:
I checked in the contents of my multiprocessing.tar file and opened issues
#1 and #2.
I added a setup.py, disabled recv_bytes_into for now and fixed lots of
naming issues. The multiprocessing code is using the new names of the
threading module (current_thread, is_alive
Maybe we should backport those handy pep8 threading names ... ... Ok maybe
not.
On Oct 22, 2008 9:02am, Christian Heimes <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
I checked in the contents of my multiprocessing.tar file and opened issues
#1 and #2.
I added a setup.py, disabled
Update:
I just implemented the recv_bytes_into function with the old buffer
protocol. All tests are passing on my Linux box (Ubuntu 8.04 with gcc
4.2, AMD64 processor).
svn check it out https://python-multiprocessing.googlecode.com/svn/trunk
Christian
___
Christian> I just implemented the recv_bytes_into function with the old
Christian> buffer protocol. All tests are passing on my Linux box
Christian> (Ubuntu 8.04 with gcc 4.2, AMD64 processor).
Using Python v < 2.6? So I don't need to horse around making
test_multiprocessing.py API c
[EMAIL PROTECTED] wrote:
Using Python v < 2.6? So I don't need to horse around making
test_multiprocessing.py API compatible with processing 0.52?
With Python 2.5.2 and 2.6.0 all tests are passing with any error. With
Python 2.4.5 seven tests are failing because 2.4 doesn't support mmap
with
[EMAIL PROTECTED] wrote:
Using Python v < 2.6? So I don't need to horse around making
test_multiprocessing.py API compatible with processing 0.52?
I've backported the Python 2.5 svn version of mmap to 2.4 and added it
as multiprocessing._mmap25. The port is just a proof of concept and most
l
The latest svn version is now working with Python 2.4.4, Python 2.5.2
and Python 2.6.0 on Linux (Ubuntu AMD64, Debian i386) and Windows XP. On
Windows the multiprocessing module requires ctypes and pywin32 under
Python 2.4.4.
Some of the examples aren't working correctly under 2.4 and 2.5. Jes
