Issue1930

import traceback results in 
ImportError: no os specific module found
when embedded interpreter is run from java.

Looks like this is because when interpreter is run from inside java, sys.builtin_module_names  does not include 'posix' nor any of the OS names that os.py is looking for in that if else if statement at the beginning of os.py.

When interpreter is run from command line, 'posix' is included in sys.builtin_module_names.



================================
actual stack trace looks like:
================================
Traceback (most recent call last):
  File "<string>", line 2, in <module>
  File "/usr/local/jython2.5.2/Lib/traceback.py", line 3, in <module>
    import linecache
  File "/usr/local/jython2.5.2/Lib/linecache.py", line 9, in <module>
    import os
  File "/usr/local/jython2.5.2/Lib/os.py", line 118, in <module>
    raise ImportError, 'no os specific module found'
================================

it should be possible to specify explicitly that 'nt' or 'posix' module should be within builtin. Any ideas how to do that?

If you look at the bottom of the registry file, you will see an option called "python.modules.builtin", which should allow you to specify the relevant os module for your platform.

"""
# Use this registry entry to control the list of builtin modules; you
# can add, remove, or override builtin modules.  The value for this
# registry key is a comma separated list of module entries, each entry 
# of which has the following allowable forms:
#
# name
#     The module name is `name' and the class name is
#     org.python.modules.name
#
# name:class
#     The module name is `name' and the class name is `class' where
#     class must be a fully qualified Java class name
#
# name:null
#     The module `name' is removed from the list of builtin modules
#
# A good example would be to use a jni version of os for more
# functionality by having an entry such as os:com.foo.jni.os
#python.modules.builtin = whatever

"""

Functionality is available, any reason not to close this out?

3 years is long enough for that question to be left hanging :) This does not occur on 2.7.2a1, so I declare it fixed. (Won't fix in 2.5.)