Remove special handling due to IPython lacking support for exception groups

[jakkdl]

Quick draft request I'll look over later in case it needs further fixes, but IPython now has a workaround for displaying exceptiongroups, and the comment said this section could be removed in that case. ipython/ipython#13753

EDIT: I guess it needs a release too, and we'd need to bump the IPython requirement to that as well - so this will have to languish for quite a while.

[codecov]

Codecov Report

Merging #2702 (51db601) into master (1c15500) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2702      +/-   ##
==========================================
- Coverage   98.94%   98.94%   -0.01%     
==========================================
  Files         113      113              
  Lines       16919    16883      -36     
  Branches     3050     3036      -14     
==========================================
- Hits        16741    16705      -36     
  Misses        123      123              
  Partials       55       55              

Files Changed	Coverage Δ
trio/_core/_multierror.py	100.00% <100.00%> (ø)
trio/_core/_tests/test_multierror.py	100.00% <100.00%> (ø)

[A5rocks]

I retargeted this PR to the PR that bumps dependencies and went ahead and marked this as reviewable: I think you will need to remove a test (or at least update it) but I believe this fixes the CI for that other PR.

[A5rocks]

Sorry, I just realize I was mistaken. Your fix hasn't gone out, I just jumped the gun when I saw multierrors were formatting differently!

Additionally, it seems I can't force-push my merge above out:

@A5rocks ➜ /workspaces/trio (ipython_exceptiongroup_support) $ git push --force
remote: Permission to jakkdl/trio.git denied to A5rocks.
fatal: unable to access 'https://github.com/jakkdl/trio/': The requested URL returned error: 403

:(

[jakkdl]

Sorry, I just realize I was mistaken. Your fix hasn't gone out, I just jumped the gun when I saw multierrors were formatting differently!

Ah sorry, maybe could've been a bit clearer in my edit :)

Additionally, it seems I can't force-push my merge above out:

@A5rocks ➜ /workspaces/trio (ipython_exceptiongroup_support) $ git push --force
remote: Permission to jakkdl/trio.git denied to A5rocks.
fatal: unable to access 'https://github.com/jakkdl/trio/': The requested URL returned error: 403

:(

Added you as a collaborator to the fork, think that might help? I could maybe start pushing branches to the trio/ repository otherwise, but I suspect force-pushing from other people isn't gonna come up too many more times.

[A5rocks]

Yeah I don't think that'll happen again: I'll try not to jump to conclusions next time!

EDIT: I don't need to join your repo FWIW, you can force push yourself xd (since you're here, I just wanted to decrease the work I caused!)

[jakkdl]

Yeah I don't think that'll happen again: I'll try not to jump to conclusions next time!

EDIT: I don't need to join your repo FWIW, you can force push yourself xd (since you're here, I just wanted to decrease the work I caused!)

Ah, you can just push reversion commit[s] then. git revert is very handy

[Zac-HD]

IPython 8.15 has been released with native ExceptionGroup support, so let's rebase this PR and get it in before Trio 0.23 🚀

[Zac-HD]

Looks like we just need to delete trio/_core/_tests/test_multierror.py::test_ipython_exc_handler and test_ipython_custom_exc_handler, and add a changelog, then we'll be ready to merge!

(and maybe also enable skip-covered in .coveragerc so it's easier to find out what failed next time)

[jakkdl]

@TeamSpen210 mind adding a changelog entry as well?

[Zac-HD]

+5 / -198 🤩