Message6675

What's wierd is that os.getpid() is not implemented on Solaris or it has to do with Java 1.6.0-18 or Java 1.6.0 in general on Solaris or OpenJDK VM vs HotSpot VM?  Being that I have standard Java HotSpot VM from the source(Oracle), regardless, whether or not this function is available is not reliable in Jython and the logging module is using os.getpid().  And in these cases where for some mystic reason the os.getpid() function is not implemented, on specific platforms and/or Java versions, phase of the moon and/or tides ;), the way it is handled in the logging module really needs to be more robust. But I digress. 

This is obviously a bug in the Python logging module but due the lack of os.getpid() in some Jython implementation(s), other than linux and windows, is exposing this issue. This is something that may need to be addressed in some way, even if that be by documentation or figuring out how to implement os.getpid() on all Jython platforms or at a minimum an os.getpid() function that returns -1 would at least would fill this hole(this would be a last resort).

This problem seems specific to Jython because of the possibility of os.getpid() being missing. Otherwise, the logging module would have been fixed in Python a long time ago.