Invalid result on a simple program about pyre-check

[dkgi]

@llimllib: thanks for trying out Pyre :)

The error you're getting means that Pyre does not know about boto3. Pyre has various ways of knowing about third-party libraries. A lot of them are defined in typeshed, which is shipped with Pyre itself. Apart from that you can tell Pyre where to look for them, e.g. by adding

"search_path": ["where/to/find/additional/python/files/or/stubs"],

to your .pyre_configuration. You can also pass this with --search-path or tell python to use your current $PYTHONPATH during the lookup (with --preserve-pythonpath).

Unfortunately, all of those options are currently not very well documented, see also #10

[dkgi]

Anyway, here's a vote for making --preserve-pythonpath the default, who would not want that on?

We usually have lots of developers working on the same codebase. Getting them all to have a consistent environment setup on their machines is very difficult so we usually rely on storing a consistent set of options in a configuration file that is shared by everybody.

[JelleZijlstra]

Would it make more sense to have unimported modules default to evaluating to Any? That's the behavior I usually choose with mypy (--follow-imports=silent is the relevant option I believe), and I think that's generally the sensible behavior if you're using libraries that don't have stubs available.

[llimllib]

Ah! thanks for the quick response, I guess I'm surprised that a type checker is concerned about whether boto3 actually exists or not.

Anyway, here's a vote for making --preserve-pythonpath the default, who would not want that on?

[llimllib]

Maybe the default if there is no config file? Anyway, I found the error very confusing so I suspect others new to the project will too.

Thanks for your hard work on the tool, I’m using it because im excited for it.