Do not require explicit RNG in verify_grad

[t3chw]

Ensures that verify_grad can handle cases where an RNG is not explicitly provided

Description

Ensures that verify_grad can handle cases where an RNG is not explicitly provided, improving the function's usability and robustness. Added a new test case, test_verify_grad_no_rng, to verify that the verify_grad function works correctly without requiring an explicit RNG (random number generator) argument.

Related Issue

• Closes Do not require rng in verify_grad #1089
• Related to #

Checklist

• Checked that the pre-commit linting/style checks pass
• Included tests that prove the fix is effective or that the new feature works
• Added necessary documentation (docstrings and/or example notebooks)
• If you are a pro: each commit corresponds to a relevant logical change

Type of change

• New feature / enhancement
• Bug fix
• Documentation
• Maintenance
• Other (please specify):

[ricardoV94]

No need for the test, the changes in the code are okay by themselves

[t3chw]

I’ve removed the test as suggested. Let me know if there’s anything else to address!

[ricardoV94]

Thanks

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 82.12%. Comparing base (33a4d48) to head (00c99f3).
Report is 92 commits behind head on main.

Files with missing lines	Patch %	Lines
pytensor/gradient.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1093      +/-   ##
==========================================
+ Coverage   82.11%   82.12%   +0.01%     
==========================================
  Files         183      183              
  Lines       47959    47978      +19     
  Branches     8635     8642       +7     
==========================================
+ Hits        39381    39403      +22     
+ Misses       6411     6408       -3     
  Partials     2167     2167              

Files with missing lines	Coverage Δ
pytensor/gradient.py	77.57% <0.00%> (ø)

... and 3 files with indirect coverage changes

[t3chw]

The pull request is ready for merge:

• Approved by the reviewer.
• No conflicts with the main branch.
• The only failing check is codecov/patch due to 0% coverage on the diff, which is expected after removing the suggested test.

Let me know if there’s anything else I should address!

[ricardoV94]

The pull request is ready for merge:

• Approved by the reviewer.
• No conflicts with the main branch.
• The only failing check is codecov/patch due to 0% coverage on the diff, which is expected after removing the suggested test.

Let me know if there’s anything else I should address!

Thanks again. Hope you don't mind me asking, is this a robot message?

[t3chw]

Haha, no not a robot, just filtered my thought with chat-gpt. This is my first PR in pymc-dev, will try to contribute more and continuously learning about pymc.