@M-Quadra are you confident that this won’t be a breaking change for existing users? Are there edge cases in which it could be a breaking change (i.e. does it still work with dep , GOMODULE111=off go get, etc)?

Release policy of Go only supports two major version. There are 1.18 and 1.17 today. Dep is deprecated since 1.11.

And the last release tag of go-python/cpy3 is 0.1.1. In v0 version of the semantic versioning model, a developer with code consuming functions in a v0 module is responsible for adapting to incompatible changes until v1 is released. (ref: version-numbers)

I don' t think any module need to support dep when 1.18.

I don' t think any module need to support dep

Agreed to break support for dep.

I was more worried about GO111MODULE=off situations. However, after reading through 1 and 2 I think it should be OK to use your change (add go.mod) and add a v0.2.0 tag. (Note: tags need to have a v prefix from now on to work with modules).

Let me verify a few things tonight and if there are no surprises I’ll merge this.