Miniconda3 environment.yml ERROR: "Found conflicts! Looking for incompatible packages."

By -

I downloaded Miniconda and was sent an environment.yml file. I first type in Conda deactivate to get out of the base environment and then do Conda env create and Conda activate name (the name of the environment.yml) but I keep getting the following error, which continues on for several lines until the last line shown below. Not sure what's wrong. I've tried changing the python version to 3.7.7 but that doesn't do anything.

(base) svaldez-29356s:~ svaldez$ conda info --envs
# conda environments:
#
base                  *  /Users/svaldez/miniconda3

(base) svaldez-29356s:~ svaldez$ conda deactivate
svaldez-29356s:~ svaldez$ conda env create
Collecting package metadata (repodata.json): done
Solving environment: \ 
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.

...

Package ipywidgets conflicts for:
ipywidgets==7.5.1=py_0
jupyter==1.0.0=py38_7 -> ipywidgets

Package gettext conflicts for:
glib==2.63.1=h70d4741_1 -> gettext
dbus==1.13.14=h517e14e_0 -> glib[version='>=2.63.1,<3.0a0'] -> gettext[version='>=0.19.8.1,<1.0a0|>=0.21.0,<1.0a0']
gettext==0.19.8.1=hb0f4f8b_2

Package matplotlib conflicts for:
seaborn==0.10.1=py_0 -> matplotlib[version='>=2.1.2']
matplotlib==3.1.3=py38_0

Package pyqt conflicts for:
pyqt==5.9.2=py38h655552a_2
jupyter==1.0.0=py38_7 -> qtconsole -> pyqt[version='>=5.9.2,<5.10.0a0']
qtconsole==4.7.4=py_0 -> pyqt


from Recent Questions - Stack Overflow https://ift.tt/2Tgk3iV
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more