StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14967690
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
7
CommunityOwnedDate
CreationDate
2013-02-19T21:22:07.227
FavoriteCount
0
LastActivityDate
2013-02-19T22:34:24.267
LastEditDate
2013-02-19T22:34:24.267
LastEditorUserId
908494
OwnerUserId
908494
ParentId
14967435
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
There's not enough information here to give you the complete answer, but the basic problem is almost certainly that <code>helloClass.py</code> does not end up anywhere on the module search path, so <code>PyImport_Import</code> can't find it. For example, maybe you're building your <code>main</code> executable into a location like <code>~/Library/Developer/Xcode/DerivedData/Hello/Build/Products/Release/hello</code>, but not copying <code>helloClass.py</code> there. Or, maybe you are copying it there, but the equivalent of <code>dirname $0</code> isn't on your module path. Or… well, there are a million possibilities, but the answer is the same in every case: <ol> <li>Figure out where the executable and the Python file are getting installed to.</li> <li>Build an appropriate (probably relative) path out of that knowledge.</li> <li>Make sure that path gets added to the module path.</li> </ol> The exact details on how Python searches for modules is different between different versions, but the basic idea is explained in <a href="http://docs.python.org/2/reference/simple_stmts.html#import" rel="nofollow">The <code>import</code>statement</a> (or <a href="http://docs.python.org/3/reference/simple_stmts.html#import" rel="nofollow">the 3.3 version</a>, which defers to <a href="http://docs.python.org/3/reference/import.html#importsystem" rel="nofollow">The import system</a>), and often, it's just a matter of adding something to <a href="http://docs.python.org/2/library/sys.html#sys.path" rel="nofollow"><code>sys.path</code></a>. (Note that if you're building .app bundles instead of just Unix command-line executables, there is a standard answer to this—you stick the .py files in a standard place, use Cocoa or CoreFoundation APIs to get the path, and then use that. But that doesn't seem to be relevant here.) <hr> Looking at the project you uploaded at <a href="https://github.com/Eduardof0nt/help.git" rel="nofollow">https://github.com/Eduardof0nt/help.git</a>: You're not copying <code>helloClass.py</code> anywhere. You have to decide where you want to copy it, and that depends entirely on how you want to deploy things. But for debugging purposes, just to get something testable, you can just put it alongside the <code>Hello Python!</code> executable (in <code>build/Debug</code> or <code>build/Release</code>). To do that: <ul> <li>Select the project in the Project Navigator.</li> <li>Select the target in the left sidebar of the project view that appears.</li> <li>Select the Build Phases tab.</li> <li>Click the Add Build Phase button.</li> <li>Add a Copy Files phase.</li> <li>Set its Destination to Products Directory.</li> <li>Drag <code>helloClass.py</code> from the Project Navigator into the build phase.</li> </ul> Now, when you build, if you look at the output (turn on "All" and "All Messages"), you'll see "Copy build/Debug/helloClass.py" right after the "Link build/Debug/Hello Python!". And, if you look inside that directory, you'll see the two files side by side. But that doesn't solve your whole problem. Because <code>/wherever/you/started/build/Debug</code> is not going to be on the <code>sys.path</code> that Python uses. The quickest way around this is to call <code>Py_SetProgramName(argv[0])</code> right before the <code>Py_Initialize()</code>, and <code>PySys_SetArgvEx(argc, argv, 1)</code> right after. That may well not be the right thing to do for your use case, but you're going to have the read the documentation and understand what all of this does, because I can't possibly explain all the details of embedding Python in an SO answer. While you're trying to learn this stuff, you probably want to do some debugging. For example, you can <code>printf(path=%s\n", Py_GetPath())</code> to see what the <code>sys.path</code> equivalent is, and <code>PyObject_Print(mod, stdout, 0)</code> to see what's in <code>mod</code>, and so on. But really, you're going to want to use the Xcode debugger—add a breakpoint and try doing this stuff at runtime. Much of this is explained in <a href="http://docs.python.org/2/extending/index.html#extending-index" rel="nofollow">Extending and Emnbedding the Python Interpreter</a>, and you really do need to read that; there's no substitute. (You don't need to read the whole <a href="http://docs.python.org/2/c-api/index.html" rel="nofollow">Python/C API Reference Manual</a>, but you will end up reading a lot of it, and getting good at searching it, before you're done.) However, because embedding Python is much less common than extending it, the docs really don't include everything you need, so… if whatever tutorial you're using doesn't cover things like <code>PySys_*</code> and <code>Py_GetPath</code>, you may need to find a better tutorial first.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to import Python functions to C in Xcode?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USabarnert
UserOwnerUserId
1. USabarnert
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.