pinned python lower than 3.8

[valeriupredoi]

Bunch of packages from our environment are not yet able to deal with python=3.8 that gets picked up automatically by an env update or update all (eg numba and possible a bunch more). Can we get this in asap, please 🍺

[bouweandela]

Can you also pin in meta.yaml?

[bouweandela]

@jvegasbsc This is one of those cases where it would have been nice not to have numba as a dependency.

[valeriupredoi]

fairly sure it's not just Numba that's been caught sleeping, man

[valeriupredoi]

Can you also pin in meta.yaml?

done, bro

[bjoernbroetz]

Do we need to address this in the https://github.com/ESMValGroup/ESMValTool repository as well?

[zklaus]

fairly sure it's not just Numba that's been caught sleeping, man

Could you please post the list? This way we will know when we can move back to normal.

[valeriupredoi]

Do we need to address this in the https://github.com/ESMValGroup/ESMValTool repository as well?

no, the environment is restrictive enough not to allow conda to update Python (I just tested)

[valeriupredoi]

fairly sure it's not just Numba that's been caught sleeping, man

Could you please post the list? This way we will know when we can move back to normal.

I would have done that if I had a list. Unfortunately it was stopping at Numba compilation. We could turn it off (remove Numba from deps) and try again to see where next it may stop but I think it may be overkill for now

[zklaus]

Well, numba is really special in that it is affected by the changes to the internal byte-code format in python 3.8, so if there is no extra reason to belief otherwise it seems reasonable to assume that no other package has problems.

[bouweandela]

I think the only other package affected was fiona, you can look this up in the installation log file, which is recorded as an artifact by circle ci.

…

On Mon, 18 Nov 2019, 15:21 Klaus Zimmermann, ***@***.***> wrote: Well, numba is really special in that it is affected by the changes to the internal byte-code format in python 3.8, so if there is no extra reason to belief otherwise it seems reasonable to assume that no other package has problems. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#376?email_source=notifications&email_token=ABJN5GK6MCA7JD5BS4IB2RTQUKQFHA5CNFSM4JN2NBJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEKSWLY#issuecomment-555035439>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJN5GMXJSMLWZV3EVNSF7TQUKQFHANCNFSM4JN2NBJQ> .

[bouweandela]

And I believe we're actually using some deprecated functions that have been removed in Python 3.8 to check that there are no invalid preprocessor arguments in the recipe, so we might need to update esmvalcore/preprocessor/__init__.py too before it works.