The way it works today, if you have an application embedding Python, your
sys.argv[0] is (likely) your main executable and sys.executable is probably
None or the empty string (per the stdlib docs which say not to set
sys.executable if there isn't a path to a known `python` executable).
On Thu, Dec 10, 2020 at 5:47 AM Serhiy Storchaka
wrote:
> 09.12.20 22:39, Steven D'Aprano пише:
> > On Wed, Dec 09, 2020 at 01:56:01PM +0200, Serhiy Storchaka wrote:
> >
> >> Thank you for good explanation of the problem.
> >
> > I'm sorry Serhiy, I disagree that this has been a "good
On Tue, Dec 8, 2020 at 2:44 PM Steven D'Aprano wrote:
> On Tue, Dec 08, 2020 at 11:47:22AM -0800, Gregory Szorc wrote:
>
> > It was recently brought to my attention via
> > https://github.com/indygreg/PyOxidizer/issues/317 that "__init__" in
> module
> > nam
PyOxidizer's pure Rust implementation of a meta path importer (
https://pyoxidizer.readthedocs.io/en/stable/oxidized_importer_oxidized_finder.html)
has been surprisingly effective at finding corner cases and behavior quirks
in Python's importing mechanisms.
It was recently brought to my attention
