Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Catching exceptions from iterator MoveNext(), additional testing (issue #475, original pull request #523) #693

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jun 26, 2018

Conversation

ArvidJB
Copy link
Contributor

@ArvidJB ArvidJB commented Jun 25, 2018

What does this implement/fix? Explain your changes.

This request contains the changes from #523 and adds some additional testing as requested in the comments on that request

Does this close any currently open issues?

Issue #475

Any other comments?

...

Checklist

Check all those that are applicable and complete.

  • Make sure to include one or more tests for your change
  • If an enhancement PR, please create docs and at best an example
  • Add yourself to AUTHORS
  • Updated the CHANGELOG

@codecov
Copy link

codecov bot commented Jun 25, 2018

Codecov Report

Merging #693 into master will increase coverage by 0.02%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #693      +/-   ##
==========================================
+ Coverage    76.9%   76.93%   +0.02%     
==========================================
  Files          63       63              
  Lines        5582     5589       +7     
  Branches      890      891       +1     
==========================================
+ Hits         4293     4300       +7     
  Misses        998      998              
  Partials      291      291
Flag Coverage Δ
#setup_linux 69.42% <ø> (ø) ⬆️
#setup_windows 76.11% <100%> (+0.02%) ⬆️
Impacted Files Coverage Δ
src/runtime/iterator.cs 88.88% <100%> (+7.07%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 545c549...2131292. Read the comment docs.

@filmor filmor merged commit 3eb7e58 into pythonnet:master Jun 26, 2018
@filmor
Copy link
Member

filmor commented Jun 26, 2018

@rickardraysearch @ArvidJB Thank you very much for your contribution and sorry (especially to @rickardraysearch) for the long time until it was finally merged.

Just to clarify, the question I had was a pure lack-of-understanding question, I'm fine if this behaviour (i.e. always traverse exactly one level into the exception chain) if it's consistent with the rest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants