fix: failing tests after #2877

[ManasviGoyal]

Just noticed that a few changes in #2877 are making the cuda tests fail. So I have fixed them.

[codecov]

Codecov Report

Merging #2886 (27b2652) into main (e2510ca) will not change coverage.
Report is 1 commits behind head on main.
The diff coverage is 100.00%.

Additional details and impacted files

Files	Coverage Δ
src/awkward/_nplikes/cupy.py	37.77% <100.00%> (ø)
src/awkward/_nplikes/jax.py	82.60% <100.00%> (ø)
src/awkward/_nplikes/numpy.py	92.10% <100.00%> (ø)
src/awkward/_nplikes/typetracer.py	74.67% <100.00%> (ø)
src/awkward/_parameters.py	82.22% <100.00%> (ø)
src/awkward/_singleton.py	89.65% <100.00%> (ø)
src/awkward/_typing.py	92.85% <100.00%> (ø)
src/awkward/operations/ak_concatenate.py	85.14% <100.00%> (ø)
src/awkward/operations/ak_from_json.py	93.57% <100.00%> (ø)

[ianna]

@ManasviGoyal - could you, please, run the linter and fix the warnings? Thanks!

[ManasviGoyal]

@ManasviGoyal - could you, please, run the linter and fix the warnings? Thanks!

I think we need to update the py.version to 3.8 in pyproject.toml to support typing.final. Should I go ahead and go it?

[ianna]

@ManasviGoyal - could you, please, run the linter and fix the warnings? Thanks!

I think we need to update the py.version to 3.8 in pyproject.toml to support typing.final. Should I go ahead and go it?

why is suddenly failing? what was changed?

[agoose77]

@ManasviGoyal is right that we should bump the PyLint Python version. I'd missed that when we last updated our Python bounds. I'm not sure why PyLint suddenly started noticing, though. I think we can safely assume that it's a strictness update on their part being pulled in via CI. No need to dig into it, though - we clearly should correct this on our side.

[agoose77]

@ManasviGoyal don't worry about pylint here - I'll fix it in a new PR.

[ManasviGoyal]

@ManasviGoyal don't worry about pylint here - I'll fix it in a new PR.

Thanks!

[ManasviGoyal]

@ianna I think this can be squash and merged now, right?