Disable pm api by default

[njgheorghita]

What was wrong?

Disable PMAPI by default, and mechanism to enable the unstable API.

Cute Animal Picture

[njgheorghita]

This was the quick and easy solution to avoiding the circular import this time around, but it seems to me like this won't be suitable long-term when we want to make the PM api available on the web3 object by default.

[carver]

I'm missing it: which circular import? Does web3.pm import from web3.main somehow?

I don't follow how this will be different from any other modules that are attached on Web3 by default.

[carver]

I'm missing it: which circular import? Does web3.pm import from web3.main somehow?

I don't follow how this will be different from any other modules that are attached on Web3 by default.

[njgheorghita]

@carver Sorry, it's not very clear but web3.pm imports from ethpm.package which imports Web3 from web3.main

[carver]

@carver Sorry, it's not very clear but web3.pm imports from ethpm.package which imports Web3 from web3.main

At some point, we may have to vendor ethpm like we did ens. For now, the internal import is okay. It may instead make sense to do the internal import inside web3.pm, but I don't have any suggestion on that yet