On Sun, Jul 10, 2016 at 12:20 AM, Nathaniel Smith wrote:
> Hi Ryan,
>
> I'll be and SciPy and I'd love to talk about this :-). Things are a
> bit hectic for me on Mon/Tue/Wed between the Python Compilers Workshop
> and my talk, but do you want to meet up Thursday maybe?
>
>
I'll be at scipy also
Sounds like an apt description of what this is intended to be.
Ryan
On Sun, Jul 10, 2016 at 10:12 PM, Nathan Goldbaum
wrote:
> Hi Ryan,
>
> As a maintainer of a unit-aware ndarray subclass, I'm also interested in
> sitting in.
>
> Maybe this can be an informal BOF session?
>
> Nathan
>
>
> On S
Hi Ryan,
As a maintainer of a unit-aware ndarray subclass, I'm also interested in
sitting in.
Maybe this can be an informal BOF session?
Nathan
On Sunday, July 10, 2016, Ryan May wrote:
> Hi Nathaniel,
>
> Thursday works for me; anyone else interested is welcome to join.
>
> Ryan
>
> On Sun,
Hi Nathaniel,
Thursday works for me; anyone else interested is welcome to join.
Ryan
On Sun, Jul 10, 2016 at 12:20 AM, Nathaniel Smith wrote:
> Hi Ryan,
>
> I'll be and SciPy and I'd love to talk about this :-). Things are a
> bit hectic for me on Mon/Tue/Wed between the Python Compilers Works
Andy
First compile "othermodule" with fortran (not f2py):
$ gfortran -shared -o libothermodule.so othermodule.f90
Then link to it when compiling "mainmodule" with f2py:
$ f2py -c -L[path to libothermodule.so] -lothermodule -m mainmodule
mainmodule.f90
You can also make othermodule a static
