How do node imports work?

[isConic]

I'm trying to do the following.

Within this project structure:

When I import them.. they don't show up in the Ryven nodes list.

When I've had this same issue of nodes not showing up when I import them, it usually meant that I wasn't structuring my nodes the "ryven way".

Like for example...
To make any of my nodes work in the past, all nodes are declared within the nodes.py files, which were located in a directory with the name you'd expect to show up next to your nodes.
So if I put my facial recognition node called face_recognition in a nodes.py file that exists in the facial directory, it would show up like this.

If i tried importing anything else that had nodes but was not called nodes.py in that some directory. It wouldn't import.

So now I'm thinking that breaking things into... little modules and exporting them through nodes.py is not the "ryven way".

What is Ryven doing exactly when I give it a nodes.py file to import?

[leon-thomm]

The README shows how node packages are defined. The package name is the folder's name, and the folder must contain a file nodes.py. Of course you can distribute your nodes into other files, you just need to make sure that you import them correctly in your nodes.py and call export_nodes() on them (you might want to be careful with relative imports in your example, but that's python stuff and doesn't have anything to do with how Ryven processes node packages).

Ryven simply imports the module nodes.py which causes export_nodes() to execute, which then registers all provided node classes as nodes in the session. That's basically it.

If the nodes don't show up, there's probably an error which you can see in the console hidden at the bottom of the window.

[leon-thomm]

ah btw. calling your node package nodes is usually probably rather undesirable :)

[isConic]

Thanks. I'll give this a try soon.