[yt-dev] Forthon issues

[Matthew Turk]

Hi Stephen,

On Tue, Aug 7, 2012 at 4:03 PM, Stephen Skory <s at skory.us> wrote:
> Hi all,
>
> Some problems Sam was having with the fortan kdtree has alerted me to
> some necessary changes due to changes in Forthon. Two of them are
> simple. One is to remove a --with-numpy flag in the Makefile. The
> second is that the most recent version of Forthon (0.8.9) builds the
> fKDpy.so object in it's own build/lib.arch.../ directory, not in the
> same directory as the Makefile. This is easily fixed by a change to
> the setup.py file in yt/utilities. I will issue a PR for this
> depending on the discussion of the following issue.

While I initially thought this would work, I'm now seeing issues with
how this interacts with using yt in develop mode, which is by far the
most common.  I don't believe it is importable anymore from a
"develop" environment.  One option I could see is adding a new target
to the Makefile, or change the Makefile to use --builddir=. .  What do
you think?

-Matt

-Matt

>
> The not-simple change is that the newest Forthon setup.py is
> hard-coded to install the Forthon package for the system Python,
> regardless of which actual Python stack you're using, which is not
> convenient for our custom-curated yt stack. The fix is to simply
> remove the hard-coding. But I want to ask y'all what the best course
> forward from here is: A) ask the author to change it, B) make the
> change in the Forthon linked to in the install_script, or C) stick to
> the old version for now?
>
> Thanks!
>
> --
> Stephen Skory
> s at skory.us
> http://stephenskory.com/
> 510.621.3687 (google voice)
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org