This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pelson
Recipients pelson, repcsike, skrah
Date 2014-10-29.17:37:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414604264.76.0.567685866999.issue21917@psf.upfronthosting.co.za>
In-reply-to
Content
I just wanted to say that I am seeing the same issue with similar build flags for the xlc compiler.

Finding the correct compile flags may well be the problem here.

For the record, since I think this is related to the flags which are being passed to os.open, I've been looking at the following:

http://bugs.python.org/issue19749
https://github.com/pypa/pip/issues/849

I actually have access to a python2.7 which does work on this OS (which I didn't compile), which allowed me to identify the following difference:


$> ./python
Python 2.7.8 [C] on aix7
>>> import os; print os..O_NOFOLLOW
137438953472


$> /usr/bin/python
Python 2.7.6 [C] on aix7
>>> import os; print os.O_NOFOLLOW
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'O_NOFOLLOW'



My workaround therefore is to put the following in sitecustomize:

import os; os.__dict__.pop('O_NOFOLLOW', None)

And as a result "make test" no longer fails.

Any idea what it is we're missing in the configure step which is erroneously putting O_NOFOLLOW in os?
History
Date User Action Args
2014-10-29 17:37:44pelsonsetrecipients: + pelson, skrah, repcsike
2014-10-29 17:37:44pelsonsetmessageid: <1414604264.76.0.567685866999.issue21917@psf.upfronthosting.co.za>
2014-10-29 17:37:44pelsonlinkissue21917 messages
2014-10-29 17:37:44pelsoncreate