cannot find package "foo" about go-pry HOT 8 CLOSED

When you say cannot find package "foo", is the package name literally foo? Or is that just a placeholder?

That looks like an issue with how go-pry looks for pry.Pry() statements. It doesn't follow dependencies, just parses all go files recursively. With lots of vendor packages, that runs into issues if there's invalid go code.

from go-pry.

from go-pry.

You import docker which gets added to the vendor folder and docker is importing foo. It's probably from test code that would normally never run. I think the fix is to add a check to go-pry to not explore the vendor folder.

from go-pry.

merging #45 was probably a good move.

However, it now means that you cant use go-pry in a project where you are depending on dependencies that are in your vendor directory.

so I guess it is a tradeoff

from go-pry.

Like, you can't insert pry.Pry() statements in the vendored dependencies? Yeah, hmm... That's kind of the same issue as #19.

from go-pry.

no, I meant you cant insert pry.Pry() statements in your main package if that package main depends on dependencies in your vendor directory

from go-pry.

I just tested it and it seems to work just fine. That change just makes it so it doesn't look for pry.Pry() statements in the vendor folder. You can still import vendored dependencies.

from go-pry.

ok, cool. my bad

from go-pry.