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
$ go get github.com/algolia/algoliasearch-client-go/v3@v3.16.0
The package is just an example. Any package with @version will fail with the same errors.
What did you expect to see?
No errors
What did you see instead?
go get output
$ go get github.com/algolia/algoliasearch-client-go/v3@v3.16.0
go: cannot use path@version syntax in GOPATH mode
$ echo $GOPATH
$ echo $GO111MODULE
This of course is easily fixed by
$ export GO111MODULE=on
It's 2021. Shouldn't we be assuming that $GO111MODULE=on by default now? I'm aware of #37755 and I do think there might be some benefits for keeping GOPATH mode (which is very useful for working on interdependent packages with independent modules), but by default Go should always assume $GO111MODULE=on even when the environment variable is not set.
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
The package is just an example. Any package with
@version
will fail with the same errors.What did you expect to see?
No errors
What did you see instead?
go get output
This of course is easily fixed by
It's 2021. Shouldn't we be assuming that
$GO111MODULE=on
by default now? I'm aware of #37755 and I do think there might be some benefits for keeping GOPATH mode (which is very useful for working on interdependent packages with independent modules), but by default Go should always assume$GO111MODULE=on
even when the environment variable is not set.The text was updated successfully, but these errors were encountered: