-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
bpo-10381, bpo-32403: What's new entries for changes to datetime #5814
Conversation
@ned-deily - I am not sure what the procedure is for adding What's New in 3.7 entries. Please advise. The text LGTM. |
@abalkin After merging to the master branch, you should only need to backport to 3.7 like any other change and that should happen automatically. |
Should I try to do some sort of benchmarking before this is merged to give an estimate of the order of magnitude of the speedup? |
@pganssle As far as I'm concerned, "significant" is sufficient. Thanks for doing this. |
…hongh-5814) * Add What's New entry for addition of datetime.timezone to the C API Closes bpo-10381 * Add what's new entry for date and datetime optimizations Closes bpo-32403 (cherry picked from commit 5bd04f9) Co-authored-by: Paul Ganssle <pganssle@users.noreply.github.com>
GH-5929 is a backport of this pull request to the 3.7 branch. |
This adds "What's New" entries for two datetime-related improvements I made in #4993 (bpo-32403) and #5032 (bpo-10381).
For the "optimizations" one, I was not sure how best to measure the improvement in speed but I just put "significant". My initial benchmarks suggest that some of the constructors have as much as 100% speed improvement, but none of that was done against an optimized build.
https://bugs.python.org/issue10381