3 ms·

I am reluctant to refer you to aws-cli V2 because it is way more involved to install. No idea why aws moved away from their original distribution method... Howe

I am reluctant to refer you to aws-cli V2 because it is way more involved to install. No idea why aws moved away from their original distribution method... However, the V2 is going to be the way to go moving forwards :/

garblegarble 3y ago
>No idea why aws moved away from their original distribution method Didn't they move away exactly because of issues like this? As I understand it, aws-cli v2 is still written in Python but ships everything it needs self-contained so it can avoid Python dependency hell[1] 1: https://www.youtube.com/watch?v=U5y7JI_mHk8#t=3m40 https://www.youtube.com/watch?v=U5y7JI_mHk8#t=3m40
- gchamonlive 3y ago
  Indeed!
- PartiallyTyped 3y ago
  Funnily enough, I didn’t have issues with Python’s dependency hell before working for AWS, not because we have more dependencies, but because… reasons.
  - RandomThrow321 3y ago
    Is it special files that begin with a capital letter, version sets, version filter instances, and massive symlink farms?
    - PartiallyTyped 3y ago
      If you already know that much then you don’t need a response ;)
takeda 3y ago
cat -n shell.nix { pkgs ? import <nixpkgs> {} }: pkgs.mkShell { name = "dev-env"; buildInputs = with pkgs; [ awscli2 ]; } And then you can have it available when entering shell with nix-shell.