You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+18-3Lines changed: 18 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ An article was also posted on the [GopherAcademy Advent-2015](https://blog.gophe
70
70
Documentation is available on [godoc](https://godoc.org):
71
71
https://godoc.org/github.com/go-python/gopy
72
72
73
-
The `pkg` and `exe` commands are for end-users and create a full standalone python package that can be installed locally using `make install` based on the auto-generated `Makefile`. Theoretically these packages could be uploaded to https://pypi.org/ for wider distribution, but that would require a lot more work to handle all the different possible python versions and coordination with the Go source version, so it is much better to just do the local make install on your system. The `gen` and `build` commands are used for testing and just generate / build the raw binding files only.
73
+
The `pkg` and `exe` commands are for end-users and create a full standalone python package that can be installed locally using `make install` based on the auto-generated `Makefile`. Theoretically these packages could be uploaded to https://pypi.org/ for wider distribution, but that would require a lot more work to handle all the different possible python versions and coordination with the Go source version, so it is easier to just do the local make install on your system. The `gen` and `build` commands are used for testing and just generate / build the raw binding files only.
74
74
75
75
IMPORTANT: many errors will be avoided by specifying the `-vm` option to gopy, with a full path if needed, or typically just `-vm=python3` to use python3 instead of version 2, which is often the default for the plain `python` command.
76
76
@@ -116,6 +116,7 @@ Options:
116
116
-version="0.1.0": semantic version number -- can use e.g., git to get this from tag and pass as argument
117
117
-vm="python": path to python interpreter
118
118
-dynamic-link=false: whether to link output shared library dynamically to Python
119
+
-build-tags="": build tags to be passed to `go build`
119
120
120
121
121
122
$ gopy help exe
@@ -142,6 +143,8 @@ Options:
142
143
-user="": username on https://www.pypa.io/en/latest/ for package name suffix
143
144
-version="0.1.0": semantic version number -- can use e.g., git to get this from tag and pass as argument
144
145
-vm="python": path to python interpreter
146
+
-dynamic-link=false: whether to link output shared library dynamically to Python
147
+
-build-tags="": build tags to be passed to `go build`
145
148
146
149
$ gopy help gen
147
150
Usage: gopy gen <go-package-name> [other-go-package...]
@@ -153,9 +156,15 @@ ex:
153
156
$ gopy gen github.com/go-python/gopy/_examples/hi
154
157
155
158
Options:
156
-
-main="": code string to run in the Go main() functionin the cgo library
159
+
-build-tags="": build tags to be passed to `go build`
160
+
-dynamic-link=false: whether to link output shared library dynamically to Python
161
+
-main="": code string to run in the go main() functionin the cgo library
157
162
-name="": name of output package (otherwise name of first package is used)
163
+
-no-make=false: do not generate a Makefile, e.g., when called from Makefile
164
+
-no-warn=false: suppress warning messages, which may be expected
158
165
-output="": output directory for bindings
166
+
-package-prefix=".": custom package prefix used when generating import statements for generated package
167
+
-rename=false: rename Go symbols to python PEP snake_case
0 commit comments