Update _custom_ops.py to accomodate renaming of impl_abstract

[vmoens]

Fixes a deprecation warning raised because of #123937 and not fixed in #123938

cc @zou3519

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/124410

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (3 Unrelated Failures)

As of commit 332b776 with merge base 7a6edb0 ():

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / linux-focal-py3.12-clang10 / test (dynamo, 3, 3, linux.2xlarge) (gh)
  profiler/test_profiler.py::TestExecutionTrace::test_execution_trace_nested_tensor

BROKEN TRUNK - The following jobs failed but was present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / linux-focal-py3.11-clang10 / test (dynamo, 2, 3, linux.2xlarge) (gh)
  profiler/test_profiler.py::TestExecutionTrace::test_execution_trace_nested_tensor
• pull / linux-focal-py3.8-clang10 / test (dynamo, 3, 3, linux.2xlarge) (gh)
  profiler/test_profiler.py::TestExecutionTrace::test_execution_trace_nested_tensor

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[zou3519]

The deprecation is intentional: we shouldn't be using anything in torch._custom_ops anymore.

[zou3519]

@vmoens how did you run into this?

[vmoens]

A test in torchrl during vmap execution using nightlies.

We capture the warnings as errors and this one wasn't expected.

There's another one too that appeared recently if you're interested
https://github.com/pytorch/rl/actions/runs/8741799575/job/23988645897?pr=2088#step:11:103566

Both errors come from the fact that vmap imports internally a bunch at execution time. We had a similar error a couple of weeks ago and @jbschlosser helped solving it

I hope the patch makes sense!

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.