fatal error: Python.h: No such file or directory

[autopulated]

fatal error: Python.h: No such file or directory

[lielran]

Same as here. add this to your steps

 - run:
          name: "Install missing library on awscli"
          command: sudo apt-get install -y libpython-dev  

[autopulated]

👍 With the need for this extra step, it's just as simple to install the cli manually from pip 🙈

[mt-kelvintaywl]

I noticed the base image is in now based on Python indeed, and was able to use the orb @1.0.0 without requiring to install python myself.

I guess this issue can be closed :)

[BalmungSan]

Agree, having to install another package defeats the purpose of using the aws-cli orb...

Anyways, IMHO (as well as to others), having to install the cli on each job feels like a completely waste of time.

[felicianotech]

Python & pip need to be installed to use the install command of this orb.

If you want to have the aws cli pre-installed in an image, there's three options that come to mind.

1. Pre-install it in your own image.
2. Use the executor/image that comes along with this orb.
3. Use the cibuilds/aws image.

As for this specific issue, I'm not sure exactly how we'd want to solve it yet. If the logic ends up the same, better, upfront error handling might the solution here.

[BalmungSan]

"Pre-install it in your own image."

We really do not want to maintain our own images, we have a lot of projects and almost all of them need a different one. Until now your official images have worked like a charm, with the only inconvenient of having to install the aws cli on almost all of them.
But, having to maintain a lot of images just for the cli does not seems like a good idea, we would end with a CD for our CD lol.

"Use the executor/image that comes along with this orb."

For steps that only require the cli, this is what we do.
But, sometime we require the cli for intermediate steps. So installing the cli over other image, seems like a better idea than persist to workspace, switch image, do other things, persist again, return to main image. (or are we wrong?)

"Use the cibuilds/aws image."

Cool, but probably we will stick to option 2.

---

Being honest, we would love if your images would come with the cli pre-installed, or having another set of images which does (like circleci/node-aws:10-stretch or circleci/openjdk:8-jdk-stretch-aws).
But, we understand that would mean more work and things to worry about for you guys.

BTW, do not get me wrong, I personally love CircleCI and am very grateful to your excellent work, just wanted to share my thoughts about that topic. 👍

[mt-sergio]

When will we have @0.1.14 solving that?

[iynere]

doesn't seem too hard to do a quick check if python/pip are installed & if not, install them—feel free to submit a PR @mt-sergio @BalmungSan @lielran @autopulated

[iynere]

but really, we should provide a 1st-party circleci/python orb so it's easier & faster for anyone to install python/pip—that's my preferred solution