fix: remove global constants

[ianna]

It seems to me that creating global constants in the tests is unnecessary. PyCall checks if a Python package has been imported and reuses it.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (bed29bc) 71.32% compared to head (49e3b7b) 71.32%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #46   +/-   ##
=======================================
  Coverage   71.32%   71.32%           
=======================================
  Files           3        3           
  Lines        1618     1618           
=======================================
  Hits         1154     1154           
  Misses        464      464           

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

[Moelf]

Instead of installing test dependency on the fly, it's cleaner to have a test Project.toml, for example: https://github.com/JuliaHEP/UnROOT.jl/blob/main/test/Project.toml . They will be installed in addition to the package you're testing

[ianna]

Instead of installing test dependency on the fly, it's cleaner to have a test Project.toml, for example: https://github.com/JuliaHEP/UnROOT.jl/blob/main/test/Project.toml . They will be installed in addition to the package you're testing

I think, I'd like to have PyCall as an optional dependency of the AwkwardArray module and only for the AwkwardPyCall module.

[Moelf]

That's fine, you're doing the Pkg extension mechanism right? The test project.toml is the correct way to test that setup, basically that would simulate when user have AK.jk and PyCall.jl installed

[Moelf]

we can merge this and I can make a PR later to move to Pkg extension system