> Unfortunately there doesn't seem to be any way to change the extension of
> a class library from .dll (other than a post-build step), so you should go bug
> the VS team about that :)
The property controls this in the C# build system, so you can put
something like ".ipyd" in the .csproj file.
On Tue, May 18, 2010 at 5:31 PM, Dino Viehland wrote:
> What if we required the extension to be named "_foo.ipyd" or "_foo.ipe"
> or something along those lines which would be similar to CPython's
> .pyd extension? That way we wouldn't be querying random DLLs that
> might or might not load and mi
Jeff wrote:
> When CPython is searching for modules to import, it will check all the
> folders in sys.path for .py, .pyc/.pyo, and .pyd/.dll files that match
> the requested import. For IronPython, .py is obviously supported,
> .pyc/.pyo are obviously(?) not, and neither are .pyd/.dll. Is there
> a
When CPython is searching for modules to import, it will check all the
folders in sys.path for .py, .pyc/.pyo, and .pyd/.dll files that match
the requested import. For IronPython, .py is obviously supported,
.pyc/.pyo are obviously(?) not, and neither are .pyd/.dll. Is there
any particular reason t
