[Pythonmac-SIG] Need M1 Mac to Test

[Brian Herman]

I lived through that era. My dad would let me play with a Mac SE.
I would play with LC II at school and Apple II.
I have an Apple IIe.

On Wed, Jan 12, 2022 at 6:37 PM <jack.jansen at cwi.nl> wrote:

> No worries, you can do Python development during the Intel->Arm
> transition. And then in umpteen years during the Arm->RiscV transition, and
> after that: who knows….
>
> (And you probably weren’t born for the 68000->PowerPC transition)
>
> :-)
>
> --
>
> Jack Jansen, <Jack.Jansen at cwi.nl>, http://www.cwi.nl/~jack
>
> If I can't dance I don't want to be part of your revolution -- Emma Goldman
>
>
>
> On 12 Jan 2022, at 23:56, Brian Herman <bherman.live at gmail.com> wrote:
>
> I wish i was doing python development during the PowerPC->Intel transition.
> I was in high school and into macs but not python at the time.
>
>
> On Wed, Jan 12, 2022 at 4:48 PM <jack.jansen at cwi.nl> wrote:
>
>>
>> On 12 Jan 2022, at 22:54, Ned Deily <nad at python.org> wrote:
>>
>>  In theory it is possible to select which architecture a multi-arch
>> executable is to run under when there is more than one option by using the
>> "arch" command, like here to force running in Intel emulation mode under
>> Rosetta2 on an M1 Mac:
>>
>> arch -x86_64 /path/to/python3{x}
>>
>> But there is a big gotcha with that: if anything running under that
>> non-default arch Python spins off another Python in a subprocess by using
>> the value of sys.executable to find the running interpreter binary, the
>> "arch -x86_64" is effectively lost and the interpreter in the subprocess
>> will run in the default architecture. This happens, for instance, when
>> running Python's own test suite: the top-level Python process running
>> regrtest will be running in Intel emulation but tests running in
>> subprocesses will still be running in the default arm64 arch, possibly
>> giving errors or silently producing misleading results. Running the tests
>> using python3{}-intel64 avoids that problem.
>>
>>
>> Yeah, that’s why I’m staying away from universal builds for now. Often I
>> have a situation where I run cmake which runs make which runs python to
>> create a venv and then somebody higher up will use that venv to create
>> something using “python" that something else will then use to build
>> something against. The chances of this working with “arch -x86_64” are
>> slim, if that:-)
>>
>> Looking at the timeline of the PowerPC->Intel transition I think most of
>> the problem will be solved in another year, because pretty much everything
>> will be available for arm natively.
>>
>> --
>> Jack Jansen, <Jack.Jansen at cwi.nl>, http://www.cwi.nl/~jack
>> If I can't dance I don't want to be part of your revolution -- Emma
>> Goldman
>>
>>
>>
>> _______________________________________________
>> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
>> https://mail.python.org/mailman/listinfo/pythonmac-sig
>> unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
>>
> _______________________________________________
> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
> https://mail.python.org/mailman/listinfo/pythonmac-sig
> unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pythonmac-sig/attachments/20220112/0de19f47/attachment-0001.html>