PyYAML cannot uninstall warning with PIP

[tayabsoomro]

No description provided.

[syncrotron]

Associated Error Message:

ERROR: Cannot uninstall 'PyYAML'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.

[syncrotron]

Fixed error by ignoring PyYAML install, but now getting new dependency error:

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
spyder 4.1.4 requires pyqt5<5.13; python_version >= "3", which is not installed.
spyder 4.1.4 requires pyqtwebengine<5.13; python_version >= "3", which is not installed.
numba 0.50.1 requires numpy>=1.15, but you have numpy 1.14.5 which is incompatible.
gevent 20.6.2 requires greenlet>=0.4.16; platform_python_implementation == "CPython", but you have greenlet 0.4.13 which is incompatible.
astropy 4.0.1.post1 requires numpy>=1.16, but you have numpy 1.14.5 which is incompatible.
astroid 2.4.2 requires six~=1.12, but you have six 1.11.0 which is incompatible.

[tayabsoomro]

I think we need to completely revamp the entire dependency pool for python because there are a lot of dependencies that are deprecated now.

I suggest getting rid of the entire python env and incrementally figuring out what dependencies exist. Thoughts?

[syncrotron]

Sure, that sounds like a wise decision (and beats attempting to fix the dependency mixups by hand). I will use python 3.9 as a base.

[tayabsoomro]

And while we are at it, I think it will be best if we consider conda to be the default dependency manager. We are currently supporting virtualenv and conda, which I think will make things more complicated. See here: https://github.com/coadunate/MICAS/blob/master/install.sh#L42-L57

We can create a YAML file recipe for our conda environment.

Possibly related to #31

[syncrotron]

Have generated new tickets to address the conversion of all virtualenv to conda (issue #36) as well as a ticket to look into updating the projects requirements (issue #37). As of now though, the original issue for PyYAML has been resolved.