GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||
GeezerVison is showing github.com — bpo-29534: _decimal difference with _pydecimal by andrewnester · Pull Request #65 · python/cpython Conversation
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Member
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Contributor
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
mdickinson
reviewed
|
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Style nit: please add a space after the >=.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This change seems unrelated to the PR; please could you revert it?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This is just nitpicking, but I think we're testing the wrong thing here: the change is in the type of the object that's passed to the Decimal subclass; the repr of the value was just a convenient way of demonstrating the difference in behaviours between the Python and C decimal implementations. How about recording and checking the type instead of the repr?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
@mdickinson good idea, thanks!
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
@mdickinson thanks! I've fixed all the nitpickings you mentioned. Also updated NEWS. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@andrewnester: Thank you! One last nitpick: please could you change the name of the test? Apart from that, this looks good to go. Did you fill out the CLA? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@mdickinson fixed. yes, I filled it couple of hours ago :) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
In, that case, LGTM unconditionally. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Codecov Report
@@ Coverage Diff @@ ## master #65 +/- ## ========================================== - Coverage 82.37% 82.37% -0.01% ========================================== Files 1427 1427 Lines 350948 350959 +11 ========================================== + Hits 289095 289100 +5 - Misses 61853 61859 +6 Continue to review full report at Codecov.
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
The coverage gods seem a bit peeved, but I can't make head or tail of the coverage report. Which 6 lines are new misses? (And which 5 lines are new hits?) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Merged. Thanks for the contribution! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
* refactor: return BB metadata from BB creation function * feat: add execute jitted code in BB_BRANCH * nit: disable JIT debug * nit: Removed debugging comment in ceval_macros.h * nit: Removed indirection warning in jit.py --------- Co-authored-by: Jules <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.