Skip to content

Refactor max_ver and min_ver to use builtin max and min #269

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

Closed

Conversation

tlaferriere
Copy link
Contributor

@tlaferriere tlaferriere commented Jun 13, 2020

This allows the use of an arbitrary number of args or an iterable for max_ver and min_ver.
All the args must of a homogeneous type (all the same). This fixes #160

tlaferriere and others added 8 commits June 12, 2020 20:20
Co-authored-by: Tom Schraitle <tomschr@users.noreply.github.com>
I am fairly confident this is correct and I think it should bedazzle any native English speaker with an appreciation of literature.
@tlaferriere tlaferriere deleted the 160-use-builtin-max-min branch June 13, 2020 13:49
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.

Deprecate min_ver/max_ver and use builtin max()/min() functions
1 participant