search

coecms / conda-envs

3 stars 2 forks source link

issue with click in analysis3 #20

Open paolap opened 5 years ago

paolap commented 5 years ago

Hi , I'm getting this issue when try to run code that sues click with analysis3 [pxp581@raijin2 ERA5]$ python cli.py --help Traceback (most recent call last): File "cli.py", line 224, in era5() File "/g/data3/hh5/public/apps/miniconda3/envs/analysis3-18.10/lib/python3.6/site-packages/click/core.py", line 764, in call return self.main(*args, **kwargs) File "/g/data3/hh5/public/apps/miniconda3/envs/analysis3-18.10/lib/python3.6/site-packages/click/core.py", line 696, in main _verify_python3_env() File "/g/data3/hh5/public/apps/miniconda3/envs/analysis3-18.10/lib/python3.6/site-packages/click/_unicodefun.py", line 124, in _verify_python3_env ' mitigation steps.' + extra RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult https://click.palletsprojects.com/en/7.x/python3/ for mitigation steps.

This system lists a couple of UTF-8 supporting locales that you can pick from. The following suitable locales were discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, af_ZA.utf8, am_ET.utf8, an_ES.utf8, ar_AE.utf8, ...

I've cut down the locales list

This is not happening if I use clef-test environment which is also using python3

aidanheerdegen commented 5 years ago

What happens if you set an appropriate locale? Does it work?

paolap commented 5 years ago

I didn't try, didn't have time to do anything more on this today, especially given that using clef-test works and it used to work before. So it seems to me it doesn't depend on what i was trying to do. I can try tomorrow if persists

aidanheerdegen commented 5 years ago

So it isn't stopping you from working? I'm not a fan of click. Not sure it is worth the overhead TBH.

paolap commented 5 years ago

I'm not arguing if it has to stay in analysis3 or not, it's probably used more if you're doing tools then if you're analysing data, just pointing out it stopped working and that the reason might affect other packages. I'm perfectly happy if it is removed from analysis3

aidanheerdegen commented 5 years ago

If it is used by other tools it has to stay. If it becomes an issue we might have to isolate that tools in an environment which supports click correctly I guess. Or invoke the tool with a script that sets the locale to something that click is ok with?

paolap commented 5 years ago

It's used in clef definitely but that has its own environment for the moment.