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

Update benchmark numbers #135

Merged
merged 1 commit into from
Nov 28, 2022
Merged

Conversation

movermeyer
Copy link
Collaborator

@movermeyer movermeyer commented Nov 23, 2022

What are you trying to accomplish?

Now that #126 and #130 are merged, and ciso8601 is still on top, it's time to brag a bit by updating the benchmark numbers. 🎉

What approach did you choose and why?

  • Ran the benchmarking scripts to update the numbers in the README.
  • Fixed some other miscellaneous issues in the README
    • Typos
    • Lowercased words in sections
    • Fixed alignment issues

What should reviewers focus on?

🤷 You can see the rendered version here.

If #138 is merged first, I'll recreate this PR with that library included too.

The impact of these changes

Fixes #66

@movermeyer movermeyer force-pushed the movermeyer/update_benchmark_numbers branch 3 times, most recently from 96f455e to 3e25eac Compare November 26, 2022 17:17
Copy link
Collaborator

@AlecRosenbaum AlecRosenbaum left a comment

Choose a reason for hiding this comment

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

LGTM, though probably should regenerate after merging the datetime backport-related PR's

@movermeyer movermeyer force-pushed the movermeyer/update_benchmark_numbers branch from 3e25eac to 652378a Compare November 28, 2022 01:55
@movermeyer movermeyer merged commit e8b6dd9 into master Nov 28, 2022
@movermeyer movermeyer deleted the movermeyer/update_benchmark_numbers branch December 21, 2022 18:51
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.

Add datetime.fromisoformat to the benchmarks
2 participants