▲ 608 ▼ python < shell (for scripts) (programming.dev) submitted 3 years ago by alexcoder04@programming.dev to c/programmer_humor@programming.dev 73 comments fedilink hide all child comments
[+] kogasa@programming.dev -6 points 3 years ago (1 child) Why not? permalink fedilink source parent hideshow 2 child comments replies: [–] Chunk@lemmy.world 6 points 3 years ago (1 child) Because you could be on another machine that doesn't have Python 3.X it only has 3.X-1. or you could write code for Python 3.12 and then four years later no one has 3.12 anymore. Sometimes you need to download packages from pip but pip might not be available or you may be hitting your company's internal pip mirror. permalink fedilink source parent hideshow 2 child comments replies: [–] kogasa@programming.dev -2 points 3 years ago (1 child) How often are you writing scripts that accidentally require a specific minor version of Python 3 to run? If you have dependencies, 1) you're no longer scripting, and 2) you need to manage your runtime environment anyway. permalink fedilink source parent hideshow 2 child comments replies: [–] RubberDucky@programming.dev 3 points 3 years ago (1 child) Runtime environments can change often, if you need to install your application on a ton of PC's you don't want to install python version 3.X on all of those instead you could just compile it into a native binary, pip is the most unsafe hell permalink fedilink source parent hideshow 2 child comments replies: [–] kogasa@programming.dev 0 points 3 years ago If you're compiling a native binary you DEFINITELY aren't in scripting territory anymore. permalink fedilink source parent
[–] Chunk@lemmy.world 6 points 3 years ago (1 child) Because you could be on another machine that doesn't have Python 3.X it only has 3.X-1. or you could write code for Python 3.12 and then four years later no one has 3.12 anymore. Sometimes you need to download packages from pip but pip might not be available or you may be hitting your company's internal pip mirror. permalink fedilink source parent hideshow 2 child comments replies: [–] kogasa@programming.dev -2 points 3 years ago (1 child) How often are you writing scripts that accidentally require a specific minor version of Python 3 to run? If you have dependencies, 1) you're no longer scripting, and 2) you need to manage your runtime environment anyway. permalink fedilink source parent hideshow 2 child comments replies: [–] RubberDucky@programming.dev 3 points 3 years ago (1 child) Runtime environments can change often, if you need to install your application on a ton of PC's you don't want to install python version 3.X on all of those instead you could just compile it into a native binary, pip is the most unsafe hell permalink fedilink source parent hideshow 2 child comments replies: [–] kogasa@programming.dev 0 points 3 years ago If you're compiling a native binary you DEFINITELY aren't in scripting territory anymore. permalink fedilink source parent
[–] kogasa@programming.dev -2 points 3 years ago (1 child) How often are you writing scripts that accidentally require a specific minor version of Python 3 to run? If you have dependencies, 1) you're no longer scripting, and 2) you need to manage your runtime environment anyway. permalink fedilink source parent hideshow 2 child comments replies: [–] RubberDucky@programming.dev 3 points 3 years ago (1 child) Runtime environments can change often, if you need to install your application on a ton of PC's you don't want to install python version 3.X on all of those instead you could just compile it into a native binary, pip is the most unsafe hell permalink fedilink source parent hideshow 2 child comments replies: [–] kogasa@programming.dev 0 points 3 years ago If you're compiling a native binary you DEFINITELY aren't in scripting territory anymore. permalink fedilink source parent
[–] RubberDucky@programming.dev 3 points 3 years ago (1 child) Runtime environments can change often, if you need to install your application on a ton of PC's you don't want to install python version 3.X on all of those instead you could just compile it into a native binary, pip is the most unsafe hell permalink fedilink source parent hideshow 2 child comments replies: [–] kogasa@programming.dev 0 points 3 years ago If you're compiling a native binary you DEFINITELY aren't in scripting territory anymore. permalink fedilink source parent
[–] kogasa@programming.dev 0 points 3 years ago If you're compiling a native binary you DEFINITELY aren't in scripting territory anymore. permalink fedilink source parent
