Esmvaltool: Prospector fails (sometimes)

[schlunma]

After building a new environment and installing the tool, I got these new error messages:

pylint 2.3.1 has requirement astroid<3,>=2.2.0, but you'll have astroid 2.0.4 which is incompatible.
prospector 1.1.6.2 has requirement pycodestyle<=2.4.0,>=2.0.0, but you'll have pycodestyle 2.5.0 which is incompatible.
prospector 1.1.6.2 has requirement pylint==2.1.1, but you'll have pylint 2.3.1 which is incompatible.

In addition, for several days now (after an update) my prospector fails sometimes with the error

Messages
========

.
  Line: None
    pylint: failure / Tool pylint failed to run (exception was raised)

prospector -X ... gives this error

AttributeError: 'MessagesStore' object has no attribute 'get_message_definition'

which was already reported here.

Is there anything we can do about this? Or is this rather an issue of prospector itself?

[bouweandela]

To fix it locally, run pip install pylint==2.1.1. I guess we could pin pylint, but I expect this issue will solve be solved by the people developing prospector soon.

[valeriupredoi]

also, the first bits are Debian (Ubuntu?) messages - I might be Dr Obvious here, but did you do a sudo apt-get update && sudo apt-get upgrade? :grin:

[schlunma]

No, but I can't because I run the tool on DKRZ's mistral :grimacing:

You mean those?

pylint 2.3.1 has requirement astroid<3,>=2.2.0, but you'll have astroid 2.0.4 which is incompatible.
prospector 1.1.6.2 has requirement pycodestyle<=2.4.0,>=2.0.0, but you'll have pycodestyle 2.5.0 which is incompatible.
prospector 1.1.6.2 has requirement pylint==2.1.1, but you'll have pylint 2.3.1 which is incompatible.

These are error messages of pip install -e ".[develop]".

[valeriupredoi]

yesh, those ones. Darn! Tell those mistral admins to stop watching cats on the internet and update their system :grin:

[mattiarighi]

I close this since it is not an ESMValTool issue.

[bouweandela]

It is actually an issue with our installation scripts, I think we may need to pin some dependencies.

[schlunma]

For the current environment, the fix mentioned above (pip install pylint==2.1.1) does not work for me anymore.

[mattiarighi]

Solved by #120 in Core.