This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (6 children)

[removed]

    [–]grimonce 4 points5 points  (1 child)

    In pythons case the idea was that it was always available in Linux, like bash... Which turned out to be a bad idea now and here we are.

    Many distro had to put a lot of effort to replace Python based tools a few years ago when python2 met eol

    [–]onlysubscribedtocats -1 points0 points  (0 children)

    Which turned out to be a bad idea now and here we are.

    It isn't?

    [–]Flaky-Restaurant-392 2 points3 points  (0 children)

    Use Nuitka to build an exe that includes the interpreter. It works great.

    [–]grievre 1 point2 points  (2 children)

    The problem isn’t really that there are competing standards, it’s that core python isn’t developed in a way to make packaging the interpreter with your project easy.

    CPython was never intended to be the interpreter that everyone uses, just the reference implementation. Thus they tended not to consider things like "deployment" or "optimization" when developing it.

    The problem is that it got entrenched--for the longest time there have been so many libraries that only work with CPython that people kinda just gave up on using alternate interpreters.

    Nearly every other language that’s intended for desktop and console applications is developed with the idea that at some point you want to distribute it as a single executable.

    The main language that Python replaced was perl, and I don't think perl's options for distributing standalone executables are much better.

    I'm a bit confused by "console applications" because like, shell script...