Hi Steve,
Since responding to Robert above, I've successfully installed Enthought's Canopy with Python 2.7 and made it default in the command-line. I can safely check that Canopy's distribution is running, and I've quite a few of sfepy's runtime dependencies (haven't had the chance to check them all).
Also, I believe my error is the same or close to what happened in this thread: http://stackoverflow.com/questions/16176128/enthought-canopy-1-0-missing-pyt...
In any case, still get an error even when trying to compile with "build_ext" and "--inplace"... maybe there are CLI flags I can use to include the directory where Python.h can be found?
Finally, I'd like to get more involved with SfePy in general, but I can't seem to find IRC channels to chat with the community. I'm thinking of how I could implement structural elements: beams, plates, and whatnot.
Cheers, Fred
Em terça-feira, 17 de junho de 2014 09h33min58s UTC-3, steve escreveu:
Hi Fred,
How have you installed python?
You might want to consider enthought:
or anaconda:
As they take care of managing lots of packages/dependencies etc.
-steve
On Jun 17, 2014, at 7:14 AM, Robert Cimrman <cim...@ntc.zcu.cz <javascript:>> wrote:
On 06/17/2014 12:49 PM, Fred Furst wrote:
Hello Robert, and thanks for the response. I take it the command in question would be:
sfepy$ python setup.py build_ext --inplace
Hadn't tried it, but did, and it gives me an error when including:
#include <Python.h>
fatal error: file not found
It seems that you do not have python development package installed. No idea how it is called on Mac, on linux it is usually something like python-dev(el). You might need other dev packages as well.
r.
Em segunda-feira, 16 de junho de 2014 02h45min16s UTC-3, Robert Cimrman escreveu:
On 06/16/2014 12:19 AM, Fred Furst wrote:
Well...
I'm a new user too. Having trouble making all dependencies work under Canopy. Also, I'm able to fully access SfePy functionality on a
Ubuntu
machine, but my MacBook Air (late 2011) keeps giving me an error for extmods.crcm.
This module is the first C extension module that gets imported. So the error means that the extension modules were not built correctly. Did you try building and running in-place?
r.
Thus far my attempts have proved unsuccessful.
Em segunda-feira, 12 de maio de 2014 16h45min29s UTC-3, Robert Cimrman escreveu:
Hi,
any Mac users here able to help with [1]?
r.
-- You received this message because you are subscribed to the Google Groups "sfepy-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sfepy-d...@googlegroups.com <javascript:>. To post to this group, send email to sfep...@googlegroups.com <javascript:>. Visit this group at http://groups.google.com/group/sfepy-devel.