Skip to content

Conversation

@ariostas
Copy link
Collaborator

No description provided.

@ikrommyd
Copy link
Collaborator

Thanks @ariostas! I was gonna do that today since we dropped py3.9 in coffea main yesterday

@ariostas ariostas changed the title chore: move to Python 3.10 as the minimum version chore: move to Python 3.10 as the minimum version and add timeouts Nov 18, 2025
@ariostas ariostas changed the title chore: move to Python 3.10 as the minimum version and add timeouts chore: drop Python 3.9, add timeouts, fix test passing logic Nov 18, 2025
@ariostas
Copy link
Collaborator Author

@pfackeldey since you have more experience with uv, what's the right way to install awkward-cpp from the main branch into the uv environment?

@ikrommyd
Copy link
Collaborator

ikrommyd commented Nov 18, 2025

I am aware of this syntax

uv pip install git+https://github.com/scikit-hep/awkward.git#subdirectory=awkward-cpp

but this still runs into the problem

      CMake Error at CMakeLists.txt:29 (message):
        awkward-cpp relies upon generated and copied artefacts such as the
        header-only libraries and generated kernel headers.  These could not be
        found, which indicates that



            nox -s prepare



        was skipped or failed.  Please check
        https://github.com/scikit-hep/awkward#installation-for-developers to learn
        more about this process.



      *** CMake configuration failed

      hint: This usually indicates a problem with the package or the build environment.

Probably just cloning in ci, run nox -s prepare for awkward and install with uv pip install -v ./awkward-cpp as if you were installing for local development is just best. You can also just install awkward too in the same step since you would be cloning anyways.

@ikrommyd
Copy link
Collaborator

ikrommyd commented Nov 18, 2025

@henryiii is there a way to get awkward-cpp from main without cloning? Should there be a way if that's not the case? Can this nox -s prepare requirement be ditched?

@henryiii
Copy link
Member

I think we could trigger that via cmake instead of via nox, then it would be possible.

@ariostas
Copy link
Collaborator Author

ariostas commented Nov 18, 2025

Probably just cloning in ci, run nox -s prepare for awkward and install with uv pip install -v ./awkward-cpp as if you were installing for local development is just best. You can also just install awkward too in the same step since you would be cloning anyways.

This is what I tried doing here, but I'm not sure why it's not working.

- name: Build awkward-cpp and awkward
run: |
cd repo-awkward
pipx run nox -s prepare -- --headers --signatures --tests
uv pip install --project .. -vv '.[test]' ./awkward-cpp -r requirements-test-full.txt

@ikrommyd
Copy link
Collaborator

ikrommyd commented Nov 18, 2025

Probably just cloning in ci, run nox -s prepare for awkward and install with uv pip install -v ./awkward-cpp as if you were installing for local development is just best. You can also just install awkward too in the same step since you would be cloning anyways.

This is what I tried doing here, but I'm not sure why it's not working.

- name: Build awkward-cpp and awkward
run: |
cd repo-awkward
pipx run nox -s prepare -- --headers --signatures --tests
uv pip install --project .. -vv '.[test]' ./awkward-cpp -r requirements-test-full.txt

ci right now shows failures in the "Save results to file" step, not installation. You can also use uvx instead of pipx btw. Also, If I remember correctly, awkward does not provide any extras so [test] is not doing anything.

@ikrommyd
Copy link
Collaborator

Uhmmm @ariostas in the last ci run, the windows py3.13 tests failed but I do not see a single actual test failure in the logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants