-
Notifications
You must be signed in to change notification settings - Fork 89
OSSEVALML-80 Python 3.10 audit #3609
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
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3609 +/- ##
=======================================
- Coverage 99.7% 99.7% -0.0%
=======================================
Files 335 335
Lines 33840 33845 +5
=======================================
+ Hits 33712 33715 +3
- Misses 128 130 +2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cp2boston thank you for putting this up and investigating 3.10! A couple things:
- do you believe EvalML fully supports 3.10 at this point? If so we can also update the install page to reflect that! To do so you just need to update
docs/source/install.md
- coverage tests will not pass for
in_container_arm64
as it is not being run as part of our CI. @chukarsten will need to merge this PR in for you.
Lmk what you think!
The env var is set in the Dockerfile.arm for the purposes of local | ||
testing in a container on a mac M1, otherwise it's a noop. | ||
""" | ||
if os.getenv("DOCKER_ARM", None): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to # pragma: no cover
this?
@cp2boston or @chukarsten Can we fix the lint error and release notes conflict here? |
- Dockerfile.arm reference for M1
260d0cb
to
cac97b6
Compare
Pull Request Description
This ticket provides minor updates to allow successful testing under python 3.10. Specifically:
After creating the pull request: in order to pass the release_notes_updated check you will need to update the "Future Release" section of
docs/source/release_notes.rst
to include this pull request by adding :pr:123
.