also catch OSError when detecting conda_exe for cross-platform builds

[bollwyvl]

Description

This PR handles some observations when --platform and --conda-exe are specified.

• before the utils.py patch:

OSError: [Errno 8] Exec format error: '~/build/standalone/linux-aarch64/standalone_conda/conda.exe'

• without the main.py tpach:

  File "~/build/lib/python3.12/site-packages/constructor/shar.py", line 74, in get_header
    variables['enable_shortcuts'] = str(info['_enable_shortcuts']).lower()
                                        ~~~~^^^^^^^^^^^^^^^^^^^^^
  File "~/build/lib/python3.12/site-packages/ruamel/yaml/comments.py", line 853, in __getitem__
    return ordereddict.__getitem__(self, key)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: '_enable_shortcuts'

Presently, building with constructor 3.11 on python 3.12.1 on linux-64:

Checklist - did you ...

• Add a file to the news directory (using the template) for the next release's release notes?
• Add / update necessary tests?

  • are there tests of cross-platform building?

• Add / update outdated documentation?

  • is there documentation about cross-platform building?

[conda-bot]

We require contributors to sign our Contributor License Agreement and we don't have one on file for @bollwyvl.

In order for us to review and merge your code, please e-sign the Contributor License Agreement PDF. We then need to manually verify your signature, merge the PR (conda/infrastructure#1084), and ping the bot to refresh the PR.

[jaimergp]

are there tests of cross-platform building?

I don't think so, but it would be trivial to write some. Take any of the examples and add --platform. In osx-arm64 we can even run the installer with Rosetta to have a proper integration test.

[jaimergp]

We'll need the news file but this looks very good to me, thanks.

[bollwyvl]

Hmm, ok, then we also need the other conda-standalone up on there...

…

On Fri, Dec 20, 2024, 08:53 jaimergp ***@***.***> wrote: We'll need the news file but this looks very good to me, thanks. — Reply to this email directly, view it on GitHub <#916 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAALCRBYNGCLATGUJIY4WTD2GQVO7AVCNFSM6AAAAABT7IU2JKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJXGE3DCMRUHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[bollwyvl]

On account of me not going to sign anything that puts me in any kind of legal relationship with Anaconda, Inc, let's consider this a "complex bug report" rather than "a material contribution", whereby I release this code to the public domain. I do hope someone take this contribution and generates a derived work without any obligation to credit me or this work.

[marcoesters]

On account of me not going to sign anything that puts me in any kind of legal relationship with Anaconda, Inc, let's consider this a "complex bug report" rather than "a material contribution", whereby I release this code to the public domain. I do hope someone take this contribution and generates a derived work without any obligation to credit me or this work.

I was about to say that the CLA is with Conda, not Anaconda, but the CLA surprisingly mentions Anaconda a lot.

@jaimergp, I think this needs to be looked at. Would conda/infastructure be the right place?

[marcoesters]

Looks like this is a work in progress already: conda/cla#1