Compiler - set solc version based on first line of contract about brownie HOT 6 CLOSED

When a contract has a floating solidity version pragma, is it preferred to use the lowest available compatible compiler version or the highest?

from brownie.

I think the highest available version. If the pragma allows it and the user has installed it, to me it seems the logical choice.

from brownie.

I agree. Would it also be good to have it attempt to install whatever version is needed? I've been looking at the solcx code, and I have ideas about how to change that as well to make this change easier and keep the two conceptually different

from brownie.

If solcx has no compatible version at all, I think it's fine to install the most recent version that fits the pragma.

In a case where there is a compatible version installed locally, but a newer version is available remotely, I don't think it's right to upgrade the local version automatically. Some people (myself included) avoid using the latest version because... well, see solc 0.5.5 ahahaha.

It would be cool to have a notification appear when compiling, saying "there is a newer version of solc available, install via xxx".

from brownie.

re: updates to solcx - i've asked github to change the repo from a fork to a standalone one so that people can open issues. Until that's happened, it only allows conversations via pull requests so we can either discuss it here or you can open a PR there :)

from brownie.

Just merged #82, it includes a method in compiler.py that should make it easy to integrate the auto-versioning with brownie.

from brownie.