go get github.com/alexedwards/scs/v2 fails about scs HOT 7 CLOSED

Are you using modules for the dependencies in your project, or the traditional GOPATH approach?

from scs.

I am using the traditional GOPATH approach.
(I am investigating using modules after you asked, in case that's what I should do going fwd)

from scs.

For running it under your GOPATH:

• Install without the v2 postfix: go get github.com/alexedwards/scs
• Import without the v2 postfix: import "github.com/alexedwards/scs"

Everything else should work as normal as documented after that.

But yes, I definitely recommend switching to using modules. There's a great introduction here.

from scs.

I'll update the installation instructions in the README to make this clearer.

from scs.

Thanks for the help.

from scs.

For posterity:
My underlying issue was that the scs api had simply changed in between me working on it.
I needed to update my code from the Manager.Load interface to using the simpler Session one.
Ironically this is something that the go modules approach would mitigate going forward, because you are more deliberate about versions when importing go code.
thanks again

from scs.

Thanks for the explanation and sorry for any trouble. It sounds like it was just unfortunate timing! The API should be stable now for a long time, and you're right, modules will address exact this problem in the future anyway.

from scs.