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 petri.lehtinen
Recipients brett.cannon, joshtriplett, ncoghlan, petri.lehtinen, vstinner
Date 2011-05-31.11:52:23
SpamBayes Score 4.06619e-13
Marked as misclassified No
Message-id <1306842744.62.0.663789574306.issue12082@psf.upfronthosting.co.za>
In-reply-to
Content
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().
History
Date User Action Args
2011-05-31 11:52:24petri.lehtinensetrecipients: + petri.lehtinen, brett.cannon, ncoghlan, vstinner, joshtriplett
2011-05-31 11:52:24petri.lehtinensetmessageid: <1306842744.62.0.663789574306.issue12082@psf.upfronthosting.co.za>
2011-05-31 11:52:24petri.lehtinenlinkissue12082 messages
2011-05-31 11:52:23petri.lehtinencreate