question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Following the installation instructions for macOS yields an error message

See original GitHub issue

Describe the bug

Following the installation instructions for macOS in the development version of the docs produces an error message, not a working MNE-Python installation

Steps to reproduce

Download the conda environment file from https://raw.githubusercontent.com/mne-tools/mne-python/master/environment.yml

Run

conda env create -f environment.yml -n mne-test

Expected results

A working environment should be created.

Actual results

Installation fails due to an unsatisfiable dependency:

Pip subprocess error:
ERROR: Could not find a version that satisfies the requirement vtk<8.2 (from -r /private/tmp/condaenv.fkd0fvyw.requirements.txt (line 4)) (from versions: 9.0.0, 9.0.1)
ERROR: No matching distribution found for vtk<8.2 (from -r /private/tmp/condaenv.fkd0fvyw.requirements.txt (line 4))


CondaEnvException: Pip failed

Additional information

This is due to the fact that python is pinned to >= 3.5 and vtk is pinned to < 8.2 on macOS. This will first install Python 3.8 (via conda) and bomb during pip install of vtk, because the only wheels available for Python 3.8 are for VTK 9.

VTK was pinned to version 8 on macOS because of some issues with version 9.

Since conda environment files do not support selectors, there are currently only 3 solutions to this problem:

  • fix the bugs that keep us from using VTK 9 on macOS
  • provide a separate environment file for macOS, which pins Python to < 3.8
  • suggest that users install the conda-forge package of MNE-Python, as the “clean” way to declare system-dependent requirements in conda land is by producing separate packages

cc @GuillaumeFavelier

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:22 (22 by maintainers)

github_iconTop GitHub Comments

2reactions
cbrnrcommented, Jun 29, 2020

I’ll see if 9.0.1 changed anything for the better though.

1reaction
cbrnrcommented, Jun 29, 2020

@GuillaumeFavelier I can help with macOS testing of course! Right, the notebook example still shows a black image with VTK 9.0.1.

Read more comments on GitHub >

github_iconTop Results From Across the Web

If an error occurred while updating or installing macOS
The message might say that an error occurred while downloading, preparing, or installing, or that the installer is damaged or could not be ......
Read more >
Fix: An Error Occurred While Preparing macOS Installation
If your MacBook says that an error occurred while preparing the installation, boot into Safe Mode and check your date and time settings....
Read more >
an error occurred installing macos
error Code =601 "An error occurred installing macOS. ... in macOS Recovery, select Reinstall macOS, then click Continue and follow the onscreen instructions....
Read more >
Fix OneDrive Files On-Demand issues on macOS 12.1 or later
This error is shown if your OneDrive folder is locked, or you don't have write permissions. Make sure the folder is unlocked and...
Read more >
Installing or updating the latest version of the AWS CLI
Install the AWS CLI on your system. ... For installation instructions, expand the section for your operating system.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found