Command not found

[kaggle]

Command not found

[solesensei]

Reinstall works for me:

$ kaggle
"kaggle": command not found
$ python3 -m pip uninstall kaggle

and then

$ python3 -m pip install kaggle
$ kaggle
usage: kaggle [-h] [-v] {competitions,c,datasets,d,kernels,k,config} ...

[nikhiljay]

I just installed kaggle using python 3 and it works: pip3 install kaggle

[mhnamaki]

I've just restarted my ubuntu machine and it worked.

[Maria-UET]

Reinstall works for me:

$ kaggle
"kaggle": command not found
$ python3 -m pip uninstall kaggle

and then

$ python3 -m pip install kaggle
$ kaggle
usage: kaggle [-h] [-v] {competitions,c,datasets,d,kernels,k,config} ...

This worked for me. Thank a lot.

This worked for me as well. I installed using this command and then added updated PATH as:

export PATH=/home/maria/.local/bin${PATH:+:${PATH}}

Then copied the Kaggle.json file to the required location as:

cp kaggle.json /home/maria/.kaggle

[josephthweatt]

@rysteboe I did check the binaries but was not entirely sure if that was the issue. I looked at @nikhiljay's comment and found that python3 was not installed on my computer. I downloaded python3 and installed kaggle with python3 -m pip install kaggle (pip3 was not a recognized command).
In any case, kaggle is working now. If you are planning on improving the installation instructions, it might help to specify installation with python3.

[RaccoonDML]

Reinstall works for me:

$ kaggle
"kaggle": command not found
$ python3 -m pip uninstall kaggle
and then

$ python3 -m pip install kaggle
$ kaggle
usage: kaggle [-h] [-v] {competitions,c,datasets,d,kernels,k,config} ...
This worked for me. Thank a lot.

[vaibhawc]

Somehow pip install --user kaggle worked.
I don't know how.
And so pip show kaggle worked too.

May be it could be included in the 'readme'!
-_-

[patilabhay679]

try : sudo pip install kaggle

You need for python's binary directory to be on your path. For a pip install kaggle --user on Linux, this is ~/.local/bin. On Windows, it's something like {python-root}/bin. You can find the exact path by doing pip uninstall kaggle and looking for the executable in the list of files that it says it would remove.

Which version was installed? You may need to restart your terminal session.

[vaibhawc]

I did it yesterday. That must be latest. I restarted the everything. Still doesn't.

I suspect that the binary is not on your path. Can you please echo $PATH and paste the results?

[vaibhawc]

My echo $PATH :
/home/mangal/bin:/home/mangal/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

On ls ~/.local/bin :

easy_install      f2py          markdown_py  pip3    saved_model_cli  toco              wheel
easy_install-3.5  freeze_graph  pip          pip3.5  tensorboard      toco_from_protos

So it does seem like that the binary is still not there!

But when I did pip uninstall kaggle , strange enough :

Skipping kaggle as it is not installed.

This creates suspicion but when I do pip install kaggle, it doesn't appear as if anything went wrong.
Could it something wrong with pip?

¯_(ツ)_/¯

Hmm, that's really weird. Do a whereis kaggle just to confirm that it's not being installed elsewhere - I don't remember where python drops system binaries. If that turns up nothing, try pip install --user kaggle. That will only install it for your user. I'm skeptical about that working, though. You can also try pip show kaggle, but if it's not detecting it for removal, then that probably won't work either.

I would also check /etc/pip.conf, $HOME/$XDG_CONFIG_HOME/pip/pip.conf (defaults to ~/.config/pip/pip.conf), and $HOME/.pip/pip.conf to see if there's anything weird there.

Yeah, I have a to do item to improve the installation instructions, since you're not the first one to have that problem.

[josephthweatt]

@rysteboe I also used pip install --user kaggle and was able to get pip show kaggle to work. However, the terminal still tells me kaggle: command not found. Also whereis kaggle returns nothing, which is kinda weird.

Do you have any idea why this might be? I'm fairly new to pip, but I think that if it is installed I should have the command available.

Did you do the following?

You need for python's binary directory to be on your path. For a pip install kaggle --user on Linux, this is ~/.local/bin. On Windows, it's something like {python-root}/bin. You can find the exact path by doing pip uninstall kaggle and looking for the executable in the list of files that it says it would remove.

It's not, strictly speaking, a python2 problem. python2 is all I have installed on my laptop and it works. Honestly, the API has been tested much less with 3 than with 2. I still strongly suspect that the problem was with your path, but I'm glad that the problem was resolved either way.

[ravigurnatham]

downloading kaggle API second time and keeping at ~/.kaggle/ worked for me

[thebeancounter]

Still getting the same error, after installing with pip3

[gopinath-balu]

Reinstall works for me:

$ kaggle
"kaggle": command not found
$ python3 -m pip uninstall kaggle

and then

$ python3 -m pip install kaggle
$ kaggle
usage: kaggle [-h] [-v] {competitions,c,datasets,d,kernels,k,config} ...

This worked for me. Thank a lot.

[SeriousHyena]

I just installed kaggle using python 3 and it works: pip3 install kaggle

After trying many other solutions this is the one that worked for me as well. I am running Windows 10 version 1909 and using jupyter notebooks and Python 3.7. also I installed directly into my anaconda environment.

[LeoTungAnh]

The following solution works for me:

1. sudo pip install kaggle
2. I go to download kaggle account on website of Kaggle to get API in format of "kaggle.json"
3. I move "kaggle.json" to /home/"user_name"/.kaggle

[valentin-fngr]

pip install --user kaggle

Yep that works.

Of course you need to do :

export PATH=/home/your_user/.local/bin

[diakt]

Reinstall works for me:

$ kaggle
"kaggle": command not found
$ python3 -m pip uninstall kaggle

and then

$ python3 -m pip install kaggle
$ kaggle
usage: kaggle [-h] [-v] {competitions,c,datasets,d,kernels,k,config} ...

Worked for me on powershell. Spent 90+ mins on this and didn't realize it's specifically */scripts/ that needs to be on path. Great success.