j...@math.brown.edu wrote:
I understand from
https://github.com/cosmologicon/pywat/pull/40#discussion_r219962259
that "to always round up... can theoretically skew the data"
*Very* theoretically. If the number is even a whisker bigger than
2.5 it's going to get rounded up regardless:
>>>
On Wed, Sep 26, 2018 at 07:26:17AM -0400, j...@math.brown.edu wrote:
> I did find the revealingly-invalid bug report
> https://bugs.python.org/issue32956 ("python 3 round bug"), so I asked
> there, but wanted to invite anyone else on this list who might be
> interested to help.
What about those
Barry Warsaw writes:
> I like the idea of an “internals” C API documentation, separate
> from the public API.
FWIW, this worked well for XEmacs ("came for flamewars, stayed for the
internals manual").
Much of the stuff we inherited from GNU only got documented when there
was massive bugginess
Python 3.7.1rc1 and 3.6.7rc1 are now available. 3.7.1rc1 is the release
preview of the first maintenance release of Python 3.7, the latest feature
release of Python. 3.6.7rc1 is the release preview of the next maintenance
release of Python 3.6, the previous feature release of Python. Assuming no
In trying to find the location of a valid instance of PyInterpreterState in
the virtual memory of a running Python (3.6) application (using
process_vm_read on Linux), I have noticed that I can only rely on
_PyThreadState_Current.interp at the very beginning of the execution. If I
try to attach to
I recently found out about Python 3's round-to-even change (via
https://github.com/cosmologicon/pywat!) and am having trouble finding
where that change was discussed.
I did find the revealingly-invalid bug report
https://bugs.python.org/issue32956 ("python 3 round bug"), so I asked
there, but
