IronPython 1.0.2365 (Beta) on .NET 2.0.50727.42
Copyright (c) Microsoft Corporation. All rights reserved.
>>> 1/2
0
>>> from __future__ import division
Traceback (most recent call last):
File , line 0, in ##3
File , line 0, in __import__##7
ImportError: No module named __future_
This ended up being weirder and more subtle than I realized... And
possibly not an IP bug
I discovered that within the problematic scope, one module was using a
variable with the same name as an imported module -- and within that
narrow scope at least, was over-writing the namespace for the module
This is actually a correct behavior (*).
The “from __future__ import division” is detected at compile-time,
which is what will affect the division IronPython uses in the given module.
However, the module will still try to import the module called “__future__”
at runtime. Since IronPython di
I don't understand this error and was wondering if someone could open
my eyes to the exact problem.
I am working with IronPython beta8 and importing this array.py file:
http://codespeak.net/svn/user/nik/array_py/trunk/src/array.py
here is the execption details:
===
Traceback (most recent
What is the correct way to import an embedded module file(s) into a
PythonEngine?
In VS I have some embedded .py files which I have access to but I
can't seem to get the PythonEngine to import the modules. I don't
know if I am using the correct methods or not.
[embedded file: CNUDB.py in namespa
2006/7/3, JoeSox <[EMAIL PROTECTED]>:
> What is the correct way to import an embedded module file(s) into a
> PythonEngine? (snip)
This is an interesting use case that could be done with PEP 302 import
hooks. In CPython it was introduced to allow importing modules from
.zip files, but in .NET sett
