just to test: Don't upgrade pip, setuptools, wheels

[romanc]

Description
Include a summary of the change and which issue is fixed. Please also include
relevant motivation and context. List any dependencies that are required for
this change.

Fixes # (issue)
If this is a hotfix to a released version, please specify it.

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note
any relevant details for your test configuration (e.g. compiler, OS). Include
enough information so someone can reproduce your tests.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• New check tests, if applicable, are included

[FlorianDeconinck]

Wat #python

[romanc]

To be fair: pip is printing warnings for that ever since (and probably before) I joined the project. It's just never a good combination to have auto-upgrading in a production CI workflow

…

On Tue, Apr 29, 2025, 17:59 Florian Deconinck ***@***.***> wrote: *FlorianDeconinck* left a comment (NOAA-GFDL/pace#116) <#116 (comment)> Wat #python — Reply to this email directly, view it on GitHub <#116 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIQUSQBEYQWJV72RKJQVRL236OX5AVCNFSM6AAAAAB4DL4RICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMZZGQZTQMJZG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[FlorianDeconinck]

Yeah... We just going to have to redo a bunch of workflow and go to pyproject after all. Sigh.

[romanc]

Yeah we don't need to move immediately. For now we are anyway on python 3.11, which is still 'safe' with that regard. Once we lift that restriction, we have to take another look at dev installs / local setups. The other question here is why this workflow is configured to do an editable install of PyFV3. That seems not necessary to me. We should probably also look at using a virtual environment because pip is - even with this patch - complaining about dependency conflicts (with system installs) as far as I could see. There's much to clean up before we have to move to a pyproject (where we - as you said - eventually have to go to)....

…

On Tue, Apr 29, 2025, 18:43 Florian Deconinck ***@***.***> wrote: *FlorianDeconinck* left a comment (NOAA-GFDL/pace#116) <#116 (comment)> Yeah... We just going to have to redo a bunch of workflow and go to pyproject after all. Sigh. — Reply to this email directly, view it on GitHub <#116 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIQUSUV6VNAMTHB7OVAMIL236T4JAVCNFSM6AAAAAB4DL4RICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMZZGU2TSNZSGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[romanc]

closing in favor of PR #117