[issue12082] Python/import.c still references fstat even with DONT_HAVE_FSTAT/!HAVE_FSTAT

[Petri Lehtinen]

Petri Lehtinen <petri at digip.org> added the comment:

I tried to compile Python 3.3 (from default branch) with DONT_HAVE_FSTAT and DONT_HAVE_STAT. It seems to depend even more heavily on stat() being available, in other files than Python/import.c.

With 2.7, it was quite easy to disable the .pyc/.pyo writing in the absence of fstat(), but the NullImporter needs to be able to check for a directory. In addition, the build process fails when trying to run "setup.py build", because distutils cannot be imported. And it cannot be imported because it's a package, and packages (directories) cannot be detected without having stat().

So... Unless we have another way to check for a directory, I'm not sure whether it will be possible to compile Python at all without stat().

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12082>
_______________________________________