On Tue, Aug 7, 2012 at 11:11 PM, Stephen Skory firstname.lastname@example.org wrote:
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?
The --builddir= option doesn't seem to put the fKDpy.so where --builddir specifies.
How about a line in the Makefile that moves the .so file back where we have always had it after compilation, and return setup.py to how it was before my PR? I've just tried this and it appears to work.
Sounds great to me. I think the ideal solution would be integrating Forthon into setup.py, but sicne that's probably tricky and difficult, I think this is a good way for now.
-- Stephen Skory email@example.com http://stephenskory.com/ 510.621.3687 (google voice) _______________________________________________ yt-dev mailing list firstname.lastname@example.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org