How to install scikit-automl in a Kaggle notebook

I wanted to give scikit-automl a try, but I don’t like to install many packages on my machine. Conda solves the problem of creating a mess, although it does not deal with the issue of running unknown code on my computer. Hence, I decided to try it on Kaggle.

Table of Contents

1. What can go wrong?

I followed the installation instructions and did not expect any issues. After all, the instruction consists of only two steps:

!curl https://raw.githubusercontent.com/automl/auto-sklearn/master/requirements.txt | xargs -n 1 -L 1 pip install
!pip install auto-sklearn

Get $80/Year of AI Expertise. For Free.

"I've learned a lot already from your blog."
— A Substack reader who has pledged $80 per year for this content.

I help SaaS startups with customer-facing LLMs stop AI hallucinations before they spark compliance nightmares or customer churn.

Why join?

• Straight-to-the-point articles on measuring and fixing hallucinations.
• Playbooks for advanced RAG tuning, guardrails, and evaluation you can copy-paste.
• Case studies from real deployments, not "Hello World" demos.

What to expect:

• 3-4 actionable emails per month.
• Proven expertise: 500+ articles & 1k+ engineers trained.
• Zero fluff, zero spam — just tactics that make your LLM stack safer.

Subscribe

What can go wrong?

Swig. Swig can go wrong. I was installing the packages, and at some point, I saw this error message. Pip was installing the pyrfr package but failed because of a problem with swig.

building 'pyrfr._regression' extension
    swigging pyrfr/regression.i to pyrfr/regression_wrap.cpp
    swig -python -c++ -modern -features nondynamic -I./include -o pyrfr/regression_wrap.cpp pyrfr/regression.i
    unable to execute 'swig': No such file or directory
    error: command 'swig' failed with exit status 1

It turns out that Kaggle has some old swig version installed on their machines, but we can quickly fix it:

!apt-get remove swig
!apt-get install swig3.0
!ln -s /usr/bin/swig3.0 /usr/bin/swig

After that change, I ran the installation script, and everything worked fine.