Garrett Cooper added the comment:
.
--
Added file: http://bugs.python.org/file17414/config.log
___
Python tracker
<http://bugs.python.org/issue8746>
___
___
Pytho
New submission from Garrett Cooper :
As seen in the nose bug [1], I stumbled upon an OS quirk with FreeBSD, where
apparently (as superuser) due to the wording of the POSIX spec for access(2),
it's considered free game to return 0 for the system call (True) for
os.[RWX]_OK.
Only pytho
Garrett Cooper added the comment:
Well, bash screws up in this dept:
$ ls -l typescript
-rw-r--r-- 1 gcooper gcooper 37875 Jul 12 22:19 typescript
$ sudo sh -c 'test -x typescript; echo $?'
1
$ sudo bash -c 'test -x typescript; echo $?'
0
$ csh
%if (-x typescript) then
Garrett Cooper added the comment:
My initial analysis was incorrect after talking with the bash(1) folks. test(1)
is doing things wrong too:
case FILEX:
/* XXX work around eaccess(2) false positives for superuser */
if (eaccess(nm, X_OK) != 0
Garrett Cooper added the comment:
My initial analysis was incorrect after talking with the bash(1) folks. test(1)
is doing things wrong too:
case FILEX:
/* XXX work around eaccess(2) false positives for superuser */
if (eaccess(nm, X_OK) != 0
Garrett Cooper added the comment:
The issue is still present.
The overall problem I suppose is with consistency and presentation of features
in the python language.
Many features cannot be presented in a 100% portable manner, and the problem is
that such features that aren't
Garrett Cooper added the comment:
Yes, it's a duplicate. That being said, documentation alone it should be
unsigned long for Darwin (OS/X), FreeBSD, OpenBSD. Looking at the definition
for ioctl(2), the below example would cause a failure.
I need to hunt around for a practical example
Garrett Cooper added the comment:
Another note: mixed endianness might have been a factor as previous versions of
the product that were shipped used bi-arch x86 (32-bit userland on 64-bit
kernel.
--
___
Python tracker
<http://bugs.python.
101 - 108 of 108 matches
Mail list logo
