[issue39867] randrange(N) for N's in same dyadic blocs have excessive correlations when sharing identical seeds

jfbu added the comment: "bug" is a strong word, which I did never employ myself, apart from using this channel of report. I rather think of a (non-documented) "deficiency", but I expect the consensus will again be that I am expressing a "raw expression". Howev

[issue39867] randrange(N) for N's in same dyadic blocs have excessive correlations when sharing identical seeds

jfbu added the comment: @tim.peters yes, a uniform random variable rescaled to two nearby scales N and M will display strong correlations. The CPython randrange() exhibits however orders of magnitude higher such correlations, but only in relation to a common bitlength. A randrange

[issue39867] randrange(N) for N's in same dyadic blocs have excessive correlations when sharing identical seeds

jfbu added the comment: Yes indeed the source code of _randbelow_with_getrandbits generates this effect. And I understand the puzzlement about my test file setting the same random seed and then complaining about correlations. But there is some non-uniformity which is enormous between what

[issue39867] randrange(N) for N's in same dyadic blocs have excessive correlations when sharing identical seeds

New submission from jfbu : We generate quadruples of random integers using randrange(n) and randrange(m) and count how many times the quadruples are identical, using the same random seed. Of course for nearby n and m (the real life example was with n==95 and m==97) we do expect matches. But

[issue35564] [DOC] Sphinx 2.0 will require master_doc variable set in conf.py

jfbu added the comment: sorry for previous message whose text mentioned the GitHub pull request number but this links to bpo issue of that number, of course completely unrelated -- pull_requests: +10525 ___ Python tracker <https://bugs.python.

[issue35564] [DOC] Sphinx 2.0 will require master_doc variable set in conf.py

Change by jfbu : -- pull_requests: -10524 ___ Python tracker <https://bugs.python.org/issue35564> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35564] [DOC] Sphinx 2.0 will require master_doc variable set in conf.py

jfbu added the comment: GitHub PR #11290 has been merged into master -- keywords: +patch pull_requests: +10524 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue35564] [DOC] Sphinx 2.0 will require master_doc variable set in conf.py

New submission from jfbu : When building CPython doc with master branch of dev repo of Sphinx (future Sphinx 2.0) one gets this warning: WARNING: Since v2.0, Sphinx uses "index" as master_doc by default. Please add "master_doc = 'contents'" to your conf.py. Fi

[issue35528] [DOC] [LaTeX] Sphinx 2.0 uses GNU FreeFont as default for xelatex

New submission from jfbu : Not sure if any issue at all, but as said in title, starting with Sphinx 2.0 (Spring 2019), XeLaTeX will be configured to use by default GNU FreeFont, (see https://github.com/sphinx-doc/sphinx/blob/master/CHANGES), and this means new dependency (for documentation

[issue34293] DOC: Makefile inherits a Sphinx 1.5 bug regarding PAPER envvar

jfbu added the comment: https://github.com/python/cpython/pull/8585 -- ___ Python tracker <https://bugs.python.org/issue34293> ___ ___ Python-bugs-list mailin

[issue34293] DOC: Makefile inherits a Sphinx 1.5 bug regarding PAPER envvar

Change by jfbu : -- keywords: +patch pull_requests: +8094 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34293> ___ ___ Python-

[issue34293] DOC: Makefile inherits a Sphinx 1.5 bug regarding PAPER envvar

New submission from jfbu : There has been a bug at Sphinx since release 1.5 https://github.com/sphinx-doc/sphinx/issues/5234 about wrong handling of PAPER environment variable. The Makefile in Doc/ reproduces the error. As a result the "A4 latex" and "letter latex" sub t

[issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters?

jfbu added the comment: Related https://github.com/sphinx-doc/sphinx/issues/4272 It is stated there that using babel-french in place of polyglossia-french avoids the "Improper discretionary list" xetex problem starting with xetex 0.2 (i.e. TeXLive 2015) whereas with polyglos

[issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters?

jfbu added the comment: On-going discussion at http://tug.org/pipermail/xetex/2017-December/027212.html has brought new element that polyglossia's French module is broken with xetex since TeXLive2016. We had only one problem, we now have two on our hands. Possibly Sphinx could be defaul

[issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters?

jfbu added the comment: I can confirm the "Improper discretionary list" error from xetex build is a xetex bug which is present at XeTeX 0.2 and absent at XeTeX 0.6 and presumably all more recent releases. It was seen at https://github.com/sphinx-doc/sphinx/issues/3546 and r

[issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15

jfbu added the comment: For info, the xetex problem "Improper discretionary list" is presumably the one seen at https://github.com/sphinx-doc/sphinx/issues/3546. I asked on xetex mailing list at http://tug.org/pipermail/xetex/2017-March/027056.html to which xetex bug it was rela

[issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters?

jfbu added the comment: I have made a PR at https://github.com/python/cpython/pull/4069 which enhances `conf.py` with some pdflatex extra Unicode configuration. I tested it with building PDF English documentation at master (at https://github.com/python/cpython/tree

[issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters?

Change by jfbu : -- pull_requests: +4040 ___ Python tracker <https://bugs.python.org/issue31589> ___ ___ Python-bugs-list mailing list Unsubscribe: