Re: [Python-Dev] Tests failing in MacPython 2.2.2
barry@python.org (Barry A. Warsaw) writes:
"MH" == Michael Hudson
writes: >> "JJ" == Jack Jansen
writes: >> JJ> Aside from the usual suspects I have three tests failing in >> JJ> MacPython 2.2.2: test_atexit, test_email and test_httplib. >> Oops, looks like I'm also getting a segfault in test_re. MH> This is normal; run "ulimit -s 2048" before running the test MH> suite.
Thanks, that works. Would it make sense to add this to the test suite some how, either by adding a ulimit call to the makefile, or adding some resource.setrlimit() call to site.py or test_{,s}re.py?
There's a patch of sf to do this. It's probably a good idea (I forget to do this fairly often). Or maybe it could be in Modules/main.c:main()... Cheers, M. -- 39. Re graphics: A picture is worth 10K words - but only those to describe the picture. Hardly any sets of 10K words can be adequately described with pictures. -- Alan Perlis, http://www.cs.yale.edu/homes/perlis-alan/quotes.html
"MH" == Michael Hudson
writes:
MH> There's a patch of sf to do this. It's probably a good idea MH> (I forget to do this fairly often). Or maybe it could be in MH> Modules/main.c:main()... Do you mean #580869? It's not really much of a patch, e.g. I can't tell if Steve actually tried that or what file he put it in. I've assigned that PR to myself and will look into it for Python 2.3. Skip or Jack can feel free to steal it from me if they want to raise the urgency on it. -Barry
BAW> Do you mean #580869? I gave it a try, but was unable to raise my stack size. I attached a file to the patch containing my change to Lib/test/regrtest.py. Skip
On Thursday, October 10, 2002, at 12:09 PM, Skip Montanaro wrote:
BAW> Do you mean #580869?
I gave it a try, but was unable to raise my stack size. I attached a file to the patch containing my change to Lib/test/regrtest.py.
Skip
Skip -- I saw the sourceforge notice and replied there before I saw this thread. Yes, that fix still works for me and No, I'm not running it as root, but I am still running 10.1.5, so if it's not working for you, maybe it's a 10.1 vs 10.2 problem. -- Steve
"SM" == Steven Majewski
writes:
SM> Yes, that fix still works for me and No, I'm not running it as SM> root, but I am still running 10.1.5, so if it's not working SM> for you, maybe it's a 10.1 vs 10.2 problem. Note that SourceForge's compile farm has some vintage 10.1 OSX server available. I've got 10.2 at home. I'll try it on both. -Barry
Steve> Yes, that fix still works for me and No, I'm not running it as Steve> root, but I am still running 10.1.5, so if it's not working for Steve> you, maybe it's a 10.1 vs 10.2 problem. Alas, from what I've seen on the pythonmac-sig, this seems to be a common theme... Skip
On donderdag, oktober 10, 2002, at 09:27 , Skip Montanaro wrote:
Steve> Yes, that fix still works for me and No, I'm not running it as Steve> root, but I am still running 10.1.5, so if it's not working for Steve> you, maybe it's a 10.1 vs 10.2 problem.
Alas, from what I've seen on the pythonmac-sig, this seems to be a common theme...
Don't worry: the recent flurry of discussion is all about
MacPython, not about unix-Python. Forward compatibility from
10.1 to 10.2 for unix programs is pretty good, the only problem
I've seen (runtime-wise, that is) is with programs using curses.
What *is* bothersome, though, is that you cannot easily create a
program on 10.2 that is backwards compatible to 10.1. Now this
is probably true on most Unix platforms, but Apple has all this
wonderful versioning infrastructure for frameworks, and then
they don't use it themselves:-(
--
- Jack Jansen
participants (5)
-
barry@python.org
-
Jack Jansen
-
Michael Hudson
-
Skip Montanaro
-
Steven Majewski