Re: How could a standalone python binary executable be made from a python script, to be run on other computers that don't have python installed?

["Susmita/Rajib" <bkpsusmitaa@gmail.com>]

    From: David Wright <deblis@lionunicorn.co.uk>
    Date: Thu, 20 Jul 2023 10:06:43 -0500
    Message-id: <[🔎] [🔎] ZLlNgwpvlWJPg7Id@axis.corp>
    Reply-to: debian-user@lists.debian.org
    In-reply-to: <[🔎]
[🔎] CAEG4cZXe=BUQ5VE_z0rcLqHGGERdANnZ=VjiznjBK439Jifmbw@mail.gmail.com>
    References: <[🔎]
[🔎] CAEG4cZXe=BUQ5VE_z0rcLqHGGERdANnZ=VjiznjBK439Jifmbw@mail.gmail.com>

On Thu 20 Jul 2023 at 16:36:44 (+0530), Susmita/Rajib wrote:
[    ...    ]

You should probably read this as background:

  https://peps.python.org/pep-0668/

> [    ...    ]
> to, presently.

When you do, pipx awaits:

  https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#python3-pep-668
[    ...    ]


Dear Mr. Wright,

Thank you for writing back with the link leading to the Python
Discourse thread. I would have preferred a similar post assuring us
from the Debian Side. Can't accept a third party website info on face
value. A 3rd party software installer from within the native Debian
system for which there isn't an explicit assurance from Debian is
unsettling. I could have risked if a Debian system snapshot could be
saved and in case of any trouble, could be reverted back to.

Yes, a virtual environment (i.e., virtualisation) however is an idea
that could theoretically be looked into, but that would mean extra
system resources to be spent for it.

Then it appears that I will be compelled to wait until my next upgrade.

Thank you for writing back with the relevant information.

Best wishes,
RKB