[Python-Dev] How to test for stuff like fsync? (original) (raw)

Martin v. Löwis martin at v.loewis.de
Sat Sep 27 03:02:00 EDT 2003

Anthony Baxter <anthony at interlink.com.au> writes:

A thought that occurred to me a short time ago: write a script that outputs the contents of each builtin module (the names in the module) to a file.

Run that under previous version of python. Run it under release candidate. Compare differences.

In this specific case, it would have triggered a false alarm on some systems. I rewrote the test for fsync to overcome a build problem on some system, where fsync was present in the library, but not present in the header files. Since we are taking fsync's address, this causes a compile-time problem. So it is intentional that fsync is now gone for systems on which it was previously (2.2) present. (More specifically, fsync might disappear on systems that cannot stand _XOPEN_SOURCE being defined)

Regards, Martin

More information about the Python-Dev mailing list