Closed datalogics-kam closed 6 years ago
This is a very good point, and a perfect report, many thanks for it. Sounds like it could be removed, lets try it.
@datalogics-kam fixed in release 1.8.4, please upgrade and report.
@datalogics-kam fixed in release 1.8.4, please upgrade and report.
Yes! Thank you very much, and for the rapid response, too. It works great!
To help us debug your issue please explain:
[x] I've read the CONTRIBUTING guide.
[x] I've specified the Conan version, operating system version and any tool that can be relevant.
[x] I've explained the steps to reproduce the error or the motivation/use case of the question/suggestion.
macOS High Sierra 10.13.6
Conan 1.8.3
Python 3.6.5
Pipenv 2018.10.13
I'm going around and around with Pipenv, because it won't install Conan without
--pre
or theallow_prereleases
setting. This is due to Conan depending on pyasn, which has never had a stable release, all betas.If I do use
allow_prereleases
, then I start grabbing up development versions of Conan itself, as well as Conan's dependencies, which is not ideal.For instance:
If I allow prereleases, I get a prerelease Conan, which I don't want.
pyasn
.pyasn
pipenv graph
doesn't show any of Conan's dependencies making reference topyasn
pyasn
out ofrequirements_osx.txt
, I can still install Conan.It makes me wonder if it really belongs at all. Is it necessary? Can it be taken out? It'd make working with Pipenv a whole lot easier.