[Python-bugs-list] [ python-Bugs-763708 ] Failures in test_macostools
SourceForge.net
noreply@sourceforge.net
Sat, 19 Jul 2003 17:30:52 -0700
Bugs item #763708, was opened at 2003-07-01 08:54
Message generated for change (Comment added) made by jackjansen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=763708&group_id=5470
Category: Macintosh
Group: Python 2.3
>Status: Pending
>Resolution: Fixed
Priority: 5
Submitted By: Brett Cannon (bcannon)
Assigned to: Jack Jansen (jackjansen)
Summary: Failures in test_macostools
Initial Comment:
Here are the test results:
test_copy (__main__.TestMacostools) ... ok
test_mkalias (__main__.TestMacostools) ... ERROR
test_mkalias_relative (__main__.TestMacostools) ... ERROR
test_touched (__main__.TestMacostools) ... ok
=====================================
=================================
ERROR: test_mkalias (__main__.TestMacostools)
--------------------------------------------------------------------
--
Traceback (most recent call last):
File "Lib/test/test_macostools.py", line 69, in test_mkalias
macostools.mkalias(test_support.TESTFN, TESTFN2)
File "/Users/drifty/cvs_code/lib/python2.3/plat-mac/
macostools.py", line 46, in mkalias
File.FSGetResourceForkName())
Error: (-1402, 'Fork name parameter is bad')
=====================================
=================================
ERROR: test_mkalias_relative (__main__.TestMacostools)
--------------------------------------------------------------------
--
Traceback (most recent call last):
File "Lib/test/test_macostools.py", line 78, in
test_mkalias_relative
macostools.mkalias(test_support.TESTFN, TESTFN2,
sys.prefix)
File "/Users/drifty/cvs_code/lib/python2.3/plat-mac/
macostools.py", line 46, in mkalias
File.FSGetResourceForkName())
Error: (-1402, 'Fork name parameter is bad')
----------------------------------------------------------------------
>Comment By: Jack Jansen (jackjansen)
Date: 2003-07-20 02:30
Message:
Logged In: YES
user_id=45365
This seems to be fixed in 2.3c1. Could you please test?
----------------------------------------------------------------------
Comment By: Brett Cannon (bcannon)
Date: 2003-07-09 20:03
Message:
Logged In: YES
user_id=357491
OK, so the problem seems to be coming from Mac/Modules/file/
_Filemodule.c and the File_FSGetResourceForkName function
(printing the result just prints "ERROR"). The online docs for
FSGetResourceForkName (which is pretty much all that is called in
that function) can be found at http://developer.apple.com/
documentation/Carbon/Reference/File_Manager/file_manager/
function_group_20.html#//apple_ref/c/func/
FSGetResourceForkName .
Now it looks like the error is an OS X error and has nothing to do
with Python. The error (-1402) means that the fork name is
syntactically invalid. I don't see how this can mean anything,
though, since FSGetResourceForkName's only argument is a
pointer to store the result of the call into.
The only thing I can think of that might be causing this error from
Python's side is that a resource fork does not exist when the call is
made. But this is just a guess so I could be wrong.
Jack, I am going to be gone from July 13 until July 21, so if you
need any debugging info from me before 2.3 final goes out I am
afraid it will have to happen soon.
----------------------------------------------------------------------
Comment By: Brett Cannon (bcannon)
Date: 2003-07-01 22:42
Message:
Logged In: YES
user_id=357491
OK, Jack, here is your info:
- 10.2.6
- Python 2.3b2+ straight from CVS (only way to code =)
- HFS+ I believe (Finder says my HD is Mac OS Extended)
Ran the test from my CVS tree with my installed version of Python
2.3b2+ (I can't do anything the standard way). I just ran it with
the installed copy from the installed test directory and got the
errors. I also just ran it with the compiled copy but not installed
Python executable in my CVS tree and once again got the error.
I noticed this came up, for me at least, when I was checking a
patch for posixpath.py (which was applied to CVS). I checked the
code, though, and didn't find a problem where anything changed to
posixpath.py would affect it.
----------------------------------------------------------------------
Comment By: Jack Jansen (jackjansen)
Date: 2003-07-01 13:47
Message:
Logged In: YES
user_id=45365
Brett, I've seen this bug once in a while, but whenever I try to
hunt it it disappears. Could you give me the following info:
- OSX exact version
- Python exact version, plus where you got it from (binary install,
source tarball install, CVS)
- Type of filesystem (HFS+, UFS, NFS, something else)
Also, if you're building from source, did you run the tests from the
build tree or from the installed tree? Could you try the other one
too?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=763708&group_id=5470