`pip install` vs `pipenv install` for package graphene>=2.0.dev

pip install graphene>=2.0.dev works fine, but pipenv install "graphene>=2.0.dev" returns:

Locking [packages] dependencies…
Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
Could not find a version that matches graphene>=2.0.dev
Tried: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.5.1, 0.1.5.2, 0.1.5.3, 0.1.6a1, 0.1.6.0, 0.1.6.1, 0.3.0, 0.4.0, 0.4.0.1, 0.4.1, 0.4.1.1, 0.4.2, 0.4.3, 0.5.0, 0.6.0, 0.6.1, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.8.0, 0.8.1, 0.9b1, 0.9, 0.9.1, 0.10.0, 0.10.1, 0.10.2, 1.0.dev20160815004752, 1.0.dev20160816073455, 1.0.dev20160822080320, 1.0.dev20160823061102, 1.0.dev20160909040318, 1.0.dev20160909055438, 1.0.dev20160911044410, 1.0.dev20160911051803, 1.0.dev20160917190505, 1.0.dev20160918041239, 1.0.dev20160920015515, 1.0.dev20160920070441, 1.0.dev20160921153356, 1.0.dev20160922020647, 1.0, 1.0.1, 1.0.2, 1.1, 1.1.1, 1.1.2, 1.1.3, 1.2, 1.3, 1.4, 1.4.1, 2.0.dev20170724064308, 2.0.dev20170725043308, 2.0.dev20170725061556, 2.0.dev20170727024417, 2.0.dev20170727061432, 2.0.dev20170801053013, 2.0.dev20170801053013, 2.0.dev20170802065539, 2.0.dev20170802065539

Ok – so I get that graphene>=2.0.dev isn’t specific enough to build a hash against. So, I’ve tried pipenv install "graphene==2.0.dev20170802065539", but get the same error. What should I be specifying here?

[kennethreitz]

which… we’re not doing 😃

[dfee]

Interesting approach. But is this not doing brain surgery with a bludgeon? Should pre-release flags not be “per-requirement”?

I’m sure that’d require a more technically sophisticated approach, but it seems much safer. What do you think?