Python wheel: initial setup

[tmi]

No description provided.

[FussyDuck]

All committers have signed the CLA.

[github-actions]

Private downstream CI failed.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13176332396.

[github-actions]

Private downstream CI failed.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13177800021.

[github-actions]

Private downstream CI failed.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13178107800.

[iainrussell]

@wdeconinck, this is part of our effort to provide a large portion of our software stack as Python wheels. We have a new convention, where the binary libraries are stored on PyPi as lib, e.g. eccodeslib, mirlib, fdblib, up to multio. We would add atlaslib to this, so that mirlib can be built with atlas support. It's still a bit experimental, but we hope that earthkit-regrid can soon start benefiting from it. I'm happy to merge this in so that we can start using the GitHub actions to deploy it, if you give us the thumbs-up!

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13245038952.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13245038952.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13247690267.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13247690267.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13247690267.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13283002144.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13283002144.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13283002144.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13283430073.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13283430073.

[tmi]

There's one particular problem here: https://pypi.org/project/atlaslib/ is already taken by someone, so we need a different name here. No preference on my side, so something like "ecatlaslib"? Ftr atlas is also taken since Dec 2024 :/

This unfortunately means that findlibs invocation would have to be done via findlibs.find("atlas", <the new name>) instead of just findlibs.find("atlas")

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13368312983.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13368312983.

[wdeconinck]

Hi, the new name could be something similar to what we have used for readthedocs.
There it is "atlas-ecmwf.readthedocs.io"
So this could be "atlaslib-ecmwf" ?

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.86%. Comparing base (cea0222) to head (7fc05bb).
Report is 22 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #257      +/-   ##
===========================================
- Coverage    79.88%   79.86%   -0.02%     
===========================================
  Files          836      836              
  Lines        65698    65734      +36     
===========================================
+ Hits         52480    52501      +21     
- Misses       13218    13233      +15     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13389406108.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13389406108.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13550353798.

[wdeconinck]

Hi @tmi could you please move this directory into ".github/python_wrapper_wheel" or so?
It should not be confused with the existence of an atlas Python API at this point.

[tmi]

@wdeconinck the convention we've started in all other ecmwf projects is to have the wrapper in python_wrapper and the python API (as in, proper interfaces callable from python, with python objects) in python_interface directory. See eg https://github.com/ecmwf/metkit/pull/55/files. That can of course be changed, ideally consistently across all the repositories -- python_wrapper is now in about 10... However I'm not sure why you would put it to .github, it does not have anything to do with github, does it? Or is it more about just hidding the directory somehow?

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13586782012.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13586782012.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13592394913.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13592394913.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13592394913.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13592950577.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13592950577.

[tmi]

@wdeconinck what do you think now? The paths have been updated -- is it mergeable now?

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13634278064.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13634278064.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13634278064.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13635221288.

[github-actions]

Private downstream CI succeeded.
Workflow name: private-downstream-ci-hpc
View the logs at https://github.com/ecmwf-actions/private-downstream-ci/actions/runs/13635221288.