[Stackless] Stackless 2.5 branch updated for Python 2.5.1c1

[Richard Tew]

Hi,

As I noticed in passing on the daily Python URL web site a reference
to a Python 2.5.1 release candidate 1, I decided to get the process of
getting Stackless ready for 2.5.1 on the way.  To this end, I have
merged the changes to the mainline Python 2.5 branch into the
Stackless 2.5 branch.

Here is the nice marked up view of the repository:
  http://svn.python.org/view/stackless/branches/release25-maint/

And the address you can use SVN to obtain the source code from:
  http://svn.python.org/projects/stackless/branches/release25-maint/

The merge was without problems, as far as I can tell having used the
build environment I have to test the resulting code.  I have not
tested the unix build environment or the MacOS one, so if people could
do that, it would be appreciated.  These related uncertainties need to
be resolved:

 - Is 'configure.in' still valid or has the merge broken it?
 - Is 'configure' still valid or has the merge broken it?
 - Do you get Stackless unit test failures on your platform?
 - Do you get Python regression test failures on your platform?

My platform is Windows using Visual C++ Express (VS8).  However I
compiled using PCbuild rather than PCbuild8, so that may explain the
one test failure I have.  A test failure I should note I had before
the merge.  I also did not compile any extensions which have any
dependencies the user is expected to install or provide.

I would appreciate confirmation that these platforms still compile
this newly updated Stackless branch ok and that no tests fail
(comments on the uncertainties above not being problems as well):

 - MacOS
 - Unix / Linux / Posix / Whatever
 - Windows with VS7.

For those who do not know, after compilation, you can run the tests in
this manner (mocked up to suit *nix manner here):

$ cd release25-main
$ ./python Lib/test/regrtest.py
... test output ... (please send failures to this list)
$ cd Stackless/unittests
$ ../../python runAll.py
... test output ... (send failures to the list)

Or on Windows:

> cd release25-maint
> PCbuild\python.exe Lib\test\regrtest.py
... test output ... (please send failures to this list)
> cd Stackless\unittests
> ..\..\PCbuild\python runAll.py
... test output ... (send failures to the list)

As an FYI, here are the test failures I am experiencing.  I am not too
concerned about them given that I never experienced them when I was
using VS7 some months ago with the same code:

======================================================================
ERROR: test_universal_newlines (test.test_subprocess.ProcessTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Richard\VC-SVN\_python\stackless-release25-maint\lib\test\test_subprocess.py",
line 366, in test_universal_newlines
    universal_newlines=1)
  File "C:\Richard\VC-SVN\_python\stackless-release25-maint\lib\subprocess.py",line
615, in __init__
    self.stdout = os.fdopen(c2pread, 'rU', bufsize)
OSError: [Errno 22] Invalid argument

======================================================================
ERROR: test_universal_newlines_communicate
(test.test_subprocess.ProcessTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Richard\VC-SVN\_python\stackless-release25-maint\lib\test\test_subprocess.py",
line 393, in test_universal_newlines_communicate
    universal_newlines=1)
  File "C:\Richard\VC-SVN\_python\stackless-release25-maint\lib\subprocess.py",line
615, in __init__
    self.stdout = os.fdopen(c2pread, 'rU', bufsize)
OSError: [Errno 22] Invalid argument

Cheers,
Richard.

_______________________________________________
Stackless mailing list
Stackless at stackless.com
http://www.stackless.com/mailman/listinfo/stackless