Skip to content

fix compiler warning #1226

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 8 commits into from
Sep 21, 2020
Merged

fix compiler warning #1226

merged 8 commits into from
Sep 21, 2020

Conversation

koubaa
Copy link
Contributor

@koubaa koubaa commented Sep 16, 2020

No description provided.

@codecov-commenter
Copy link

codecov-commenter commented Sep 16, 2020

Codecov Report

Merging #1226 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1226   +/-   ##
=======================================
  Coverage   86.25%   86.25%           
=======================================
  Files           1        1           
  Lines         291      291           
=======================================
  Hits          251      251           
  Misses         40       40           
Flag Coverage Δ
#setup_linux 64.94% <ø> (ø)
#setup_windows 72.50% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


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 ef2e6b4...d5de641. Read the comment docs.

@koubaa
Copy link
Contributor Author

koubaa commented Sep 17, 2020

@lostmsu please review

Copy link
Member

@filmor filmor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, can we make PyObject.obj readonly now?

@lostmsu
Copy link
Member

lostmsu commented Sep 17, 2020

@koubaa sorry, reviewed, but forgot to submit :-)

@koubaa
Copy link
Contributor Author

koubaa commented Sep 18, 2020

Looks good to me, can we make PyObject.obj readonly now?

It's a good thought! I tried it, but PyObject.Dispose sets it to IntPtr.Zero and that is a compiler error.

@lostmsu lostmsu merged commit 451fae6 into pythonnet:master Sep 21, 2020
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.

4 participants