Philip May

Here is a Colab with code that shows that the dataset can be loaded without setting `ŧrust_remote_code`: https://colab.research.google.com/drive/1BUORL2_VxORGdIko6SMPqJqZIMUmtR-3?usp=sharing

@clefourrier and @Pommel4711 I think the root issue is this and not the dataset itself: ``` File "C:\apps\entwicklungsumgebung\anaconda3\envs\lighteval\lib\site-packages\datasets\load.py", line 117, in resolve_trust_remote_code signal.signal(signal.SIGALRM, _raise_timeout_error) AttributeError: module 'signal' has no attribute...

> Hm, I'm going to ping @lhoestq on this then because it seems like a `datasets` issue. Good idea. Thanks.

@Pommel4711 now I also have the same issue. I am on linux. So this should not be the root cause of the problem.

@Pommel4711 I found a solution that works for me. See here: #278 It is by adding `export HF_DATASETS_TRUST_REMOTE_CODE=TRUE` But this should not be required. IMO this should be considered as...

> can you try uninstalling and reinstalling `datasets`? You mean a `pip install -U datasets` might not be enough? @lhoestq

> Ah it's `community_tasks/german_rag_evals.py` apparently ? Well maybe you should point to a dataset on HF with data e.g. in parquet files instead. (and remove this script from `lighteval` ?)...

> Add benchmarks for tool usage Are there any? What do you suggest?

Hi. I did not know about this pep before. So there were no plans. For me this pep reads like it might replace the functionality of lazy-imports one day.

> As for lazy-imports, do you find it worth the effort to support the development for the feature in topic? To be honest: I do not actively extend this tool...