ironpython - absolute_import about traitlets HOT 4 CLOSED

@swn1 can you tell us what module is being imported incorrectly, and what exactly the error is? It's a bit odd that IronPython would behave differently from CPython 2.7 in this regard.

from traitlets.

Without the absolute_import clause I get this:
`
C:\Program Files (x86)\IronPython 2.7>ipy64 -X:Frames
IronPython 2.7.5 (2.7.5.0) on .NET 4.0.30319.42000 (64-bit)
Type "help", "copyright", "credits" or "license" for more information.

import sys
sys.path.insert(0, r"c:\users\steve\jupyter_client")
sys.path.insert(0, r"c:\users\steve\jupyter_core")
sys.path.insert(0, r"c:\users\steve\ironzmq")

import jupyter_client as jc
Traceback (most recent call last):
File "", line 1, in
File "c:\users\steve\jupyter_client\jupyter_client__init__.py", line 4, in
File "c:\users\steve\jupyter_client\jupyter_client\connect.py", line 23, in
File "C:\Program Files (x86)\IronPython 2.7\lib\site-packages\traitlets\config
init.py", line 6, in
File "C:\Program Files (x86)\IronPython 2.7\lib\site-packages\traitlets\config
\application.py", line 18, in
File "C:\Program Files (x86)\IronPython 2.7\lib\site-packages\traitlets\config
\configurable.py", line 13, in
ImportError: No module named traitlets

`

My copy of jupyter_client is, so far, unmodified. ironmzq is a stiched-together mess, mostly copied from pymzq but with the whole backend structure ripped out and replaced by clrmzq4. I tried dropping the .NET zeromq bindings in under backend but it got very messy so I'm trying it this way, may go back.

The traitlets code I'm running is pip-installed, 4.2.1.

The call site in jupyter_client looks like this:
`from future import absolute_import

import glob
import json
import os
import socket
import tempfile
import warnings
from getpass import getpass

import zmq

from traitlets.config import LoggingConfigurable
from .localinterfaces import localhost
from ipython_genutils.path import filefind`

And works with the suggested change.

from traitlets.

I won't oppose the change in #213, but that seems like a bug in ironpython, because there is no traitlets.py in traitlets/config. That means absolute_import should have no effect in traitlets/config/configurable.py according to Python's defined behavior.

from traitlets.

I reached a similar conclusion, that there is something askew in the implementation of import, based on some other breadcrumbs I've found along the way. Behavior seems to depend on history in ways it shouldn't. In IronPython import also searches the loaded .NET namespaces so it's definitely different. But I'm just a beginner in this codebase, Thanks for the expert review.

from traitlets.