Skip to content
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

Fix a typo in the docstring for OrderedLogistic #6611

Merged

Conversation

NathanielF
Copy link
Contributor

Fixing a Docstring Example

Just a tiny change to fix a docstring for the orderedlogit class, the current docstring fails to run. This resolves it.
Related to discussion here

Checklist

Major / Breaking Changes

  • NA

New features

  • NA

Bugfixes

  • NA

Documentation

  • Changed docstring

Maintenance

  • NA

@codecov
Copy link

codecov bot commented Mar 18, 2023

Codecov Report

Merging #6611 (7110bd3) into main (c7279b5) will decrease coverage by 30.89%.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##             main    #6611       +/-   ##
===========================================
- Coverage   87.09%   56.21%   -30.89%     
===========================================
  Files          93       93               
  Lines       15737    15737               
===========================================
- Hits        13706     8846     -4860     
- Misses       2031     6891     +4860     
Impacted Files Coverage Δ
pymc/distributions/discrete.py 50.63% <ø> (-48.09%) ⬇️

... and 72 files with indirect coverage changes

@ricardoV94 ricardoV94 changed the title [Issue #6610] fixing a typo in the docstring for the orderedlogistic … Fix a typo in the docstring for OrderedLogistic Mar 18, 2023
@ricardoV94 ricardoV94 merged commit 67925df into pymc-devs:main Mar 18, 2023
@ricardoV94
Copy link
Member

Thanks @NathanielF

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

Successfully merging this pull request may close these issues.

None yet

2 participants