Data

Tools

Indexes

Applications

Experiments

Awesome

An open API service indexing awesome lists of open source software.

https://github.com/sbinet/go-python

naive go bindings to the CPython2 C-API
https://github.com/sbinet/go-python

cgo go golang python2

Last synced: about 2 months ago
JSON representation

naive go bindings to the CPython2 C-API

Awesome Lists containing this project

README 

          
go-python

=========



**`sbinet/go-python` only supports CPython2. CPython2 isn't supported anymore by [python.org](https://python.org). Thus, `sbinet/go-python` is now archived.**

**A possible alternative may be to use and contribute to [go-python/cpy3](https://github.com/go-python/cpy3) instead.**



[![Build Status](https://travis-ci.org/sbinet/go-python.svg?branch=master)](https://travis-ci.org/sbinet/go-python)

[![Build status](https://ci.appveyor.com/api/projects/status/n0ujg8no487a89vo/branch/master?svg=true)](https://ci.appveyor.com/project/sbinet/go-python/branch/master)

[![GoDocs](https://godocs.io/github.com/sbinet/go-python?status.svg)](https://godocs.io/github.com/sbinet/go-python)



Naive `go` bindings towards the C-API of CPython-2.



this package provides a ``go`` package named "python" under which most of the ``PyXYZ`` functions and macros of the public C-API of CPython have been exposed.



theoretically, you should be able to just look at:



  http://docs.python.org/c-api/index.html



and know what to type in your ``go`` program.



this package also provides an executable "go-python" which just loads "python" and then call ``python.Py_Main(os.Args)``.

the rational being that under such an executable, ``go`` based extensions for C-Python would be easier to implement (as this usually means calling into ``go`` from ``C`` through some rather convoluted functions hops)



## Install



With `Go 1` and the ``go`` tool, ``cgo`` packages can't pass anymore

additional ``CGO_CFLAGS`` from external programs (except `pkg-config`)

to the "fake" ``#cgo`` preprocessor directive.



``go-python`` now uses ``pkg-config`` to get the correct location of

headers and libraries.

Unfortunately, the naming convention for the ``pkg-config`` package is

not standardised across distributions and OSes, so you may have to

edit the ``cgoflags.go`` file accordingly.



```sh

 $ go get github.com/sbinet/go-python

```



If ``go get`` + ``pkg-config`` failed:



```sh

 $ cd go-python

 $ edit cgoflags.go

 $ make VERBOSE=1

```



*Note*: you'll need the proper header and `python` development environment. On Debian, you'll need to install the ``python-all-dev`` package



Documentation

-------------



Is available on ``godocs``:



 https://godocs.io/github.com/sbinet/go-python



Example:

--------



```go

package main



import "fmt"

import "github.com/sbinet/go-python"



func init() {

   err := python.Initialize()

   if err != nil {

          panic(err.Error())

   } 

}



func main() {

 	 gostr := "foo" 

	 pystr := python.PyString_FromString(gostr)

	 str := python.PyString_AsString(pystr)

	 fmt.Println("hello [", str, "]")

}

```



```sh

$ go run ./main.go

hello [ foo ]

```



TODO:

-----



 - fix handling of integers (I did a poor job at making sure everything was ok)



 - add CPython unit-tests



 - do not expose ``C.FILE`` pointer and replace it with ``os.File`` in "go-python" API



 - provide an easy way to extend go-python with ``go`` based extensions



 - think about the need (or not) to translate CPython exceptions into go panic/recover mechanism



 - use SWIG to automatically wrap the whole CPython api ?