There already exists a python3 branch in the atomspace repo unfortunately I never got it to work. This also contains a lot of changes I did trying to get it to work but didn't help that might have to be reversed. And the branch is over 2 years old not sure how much the python interface has changed since then but might still be worth looking at it.
On Tuesday, December 19, 2017 at 9:49:53 PM UTC+1, Eyob wrote: > > (1) > > So we have an intern at icog labs who is interested in making python3 > bindings for opencog/atomspace. > > If anybody wants to give him guidance on how to go about it, please write > him here or here https://github.com/opencog/atomspace/issues/501 > > His github username/profile is https://github.com/Yididya/ > > Hope he would be asking for pull requests soon :D > > (2) > > I was wondering does every part of opencog/atomspace need to be built > using python3 or we can proceed part by part. E.g. > > It seems i really like this import statement to work right now > > from opencog.scheme_wrapper import scheme_eval > > in python3 but the error reads " ImportError: No module named 'opencog' " > when executed. > > Its like at the moment we need python3 bindings only for a small number of > import statements, for a project we are doing now currently. > > Thanks! > > -- You received this message because you are subscribed to the Google Groups "opencog" group. To unsubscribe from this group and stop receiving emails from it, send an email to opencog+unsubscr...@googlegroups.com. To post to this group, send email to opencog@googlegroups.com. Visit this group at https://groups.google.com/group/opencog. To view this discussion on the web visit https://groups.google.com/d/msgid/opencog/82208a05-9809-47e3-a2fa-84c69ff156bd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
