Pearu,
Ohh Pearu I'm not complaining about deficiencies in f2py ... its a
great piece of work that makes what I'm doing possible at all. Just
like most open source software (including my own ;-) there may be
ways to tweak it to do things that are undocumented.
>> Why is that problem? I can
On Thu, February 14, 2008 8:24 am, Garry Willgoose wrote:
> Thanks for that. The docs suggest library dl is Unix only. Does that
> mean this solution will not work on Windows? Windows is on my
> implementation roadmap but I'm not quite there yet to test it.
I have no idea whether it will work on W
Thanks for that. The docs suggest library dl is Unix only. Does that
mean this solution will not work on Windows? Windows is on my
implementation roadmap but I'm not quite there yet to test it.
I guess I am now thinking maybe I can assemble (using f2py) an
(aggregated) shared library on the
On 2/12/08, Pearu Peterson <[EMAIL PROTECTED]> wrote:
> according to which makes your goal unachivable because of how
> Python loads shared libraries *by default*, see below.
> Try to use sys.setdlopenflags(...) before importing f2py generated
> extension modules and then reset the state using sys
On Tue, February 12, 2008 7:52 am, Garry Willgoose wrote:
> I have a suite of fortran modules that I want to wrap with f2py
> independently (so they appear to python as seperate imports) but
> where each module has access to another fortran module (which
> contains global data that is shared betwee
I have a suite of fortran modules that I want to wrap with f2py
independently (so they appear to python as seperate imports) but
where each module has access to another fortran module (which
contains global data that is shared between the suite of fortran
modules). I currently compile all t
