-
Notifications
You must be signed in to change notification settings - Fork 184
MAINT: More adjustments for changes in sklearn1.8 LogisticRegression #2784
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
david-cortes-intel
merged 8 commits into
uxlfoundation:main
from
david-cortes-intel:logreg_deprecated_penalty
Nov 27, 2025
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
cbfbf02
more adjustments for sklearn1.8
david-cortes-intel 1ac0b03
try using fork to see if it passes tests
david-cortes-intel 268dec7
restore main branch after PR was merged
david-cortes-intel e545bc2
Merge branch 'main' into logreg_deprecated_penalty
david-cortes-intel caff55f
corrections
david-cortes-intel 27e4659
add missing patching condition
david-cortes-intel b4cbedd
document conditions
david-cortes-intel 931604d
Merge branch 'main' into logreg_deprecated_penalty
david-cortes-intel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Most other boolean values mentioned in these docs use single ticks - is double preferred? If so I guess we should update for all of these, otherwise let's stick with single
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.
Double backtick is guaranteed to render as code. Single backtick is up to configuration. I don't know why they had single ticks.