<div class="highlight highlight-source-python notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="&gt;&gt;&gt; np.full_like(np.array([1,0]), np.nan)
array([-9223372036854775808, -9223372036854775808])"><pre class="notranslate"><span class="pl-c1">&gt;&gt;</span><span class="pl-c1">&gt;</span> <span class="pl-s1">np</span>.<span class="pl-en">full_like</span>(<span class="pl-s1">np</span>.<span class="pl-en">array</span>([<span class="pl-c1">1</span>,<span class="pl-c1">0</span>]), <span class="pl-s1">np</span>.<span class="pl-s1">nan</span>)
<span class="pl-en">array</span>([<span class="pl-c1">-</span><span class="pl-c1">9223372036854775808</span>, <span class="pl-c1">-</span><span class="pl-c1">9223372036854775808</span>])</pre></div>
<p dir="auto">Normally, conversion of an NaN to an int fails:</p>
<div class="highlight highlight-source-python notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="&gt;&gt;&gt; np.int(np.nan) 
ValueError: cannot convert float NaN to integer"><pre class="notranslate"><span class="pl-c1">&gt;&gt;</span><span class="pl-c1">&gt;</span> <span class="pl-s1">np</span>.<span class="pl-en">int</span>(<span class="pl-s1">np</span>.<span class="pl-s1">nan</span>) 
<span class="pl-v">ValueError</span>: <span class="pl-s1">cannot</span> <span class="pl-s1">convert</span> <span class="pl-s1">float</span> <span class="pl-v">NaN</span> <span class="pl-s1">to</span> <span class="pl-s1">integer</span></pre></div>
<p dir="auto">I suspect the <code class="notranslate">full_like</code> behaviour should similarly raise an error. I'm not sure how common this behaviour is.</p>
<h3 dir="auto">Issue with current documentation:</h3>
<p dir="auto">I wanted to test the PDF build of documentation for 1.24, and the build ended with this report:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Latexmk: ====List of undefined refs and citations:
  Missing character: There is no 琴 (U+7434) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
  Missing character: There is no 春 (U+6625) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
  Missing character: There is no 鈴 (U+9234) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
  Missing character: There is no 猫 (U+732B) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
  Missing character: There is no 傅 (U+5085) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
  Missing character: There is no 立 (U+7ACB) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
  Missing character: There is no 业 (U+4E1A) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
 And 2 more --- see log file."><pre class="notranslate"><code class="notranslate">Latexmk: ====List of undefined refs and citations:
  Missing character: There is no 琴 (U+7434) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
  Missing character: There is no 春 (U+6625) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
  Missing character: There is no 鈴 (U+9234) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
  Missing character: There is no 猫 (U+732B) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
  Missing character: There is no 傅 (U+5085) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
  Missing character: There is no 立 (U+7ACB) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
  Missing character: There is no 业 (U+4E1A) in font [FreeSerif.otf]/OT:script=latn;language=dflt;mapping=tex-text;!
 And 2 more --- see log file.
</code></pre></div>
<p dir="auto">Then I checked log file where the page numbers are indicated (339 and 363 for my build but my virtual environment was lacking some stuff so warnings were reported about doxygen and scipy, perhaps I am missing pages in my build) and this actually maps to the Release notes for 1.23.3 and 1.21.4.</p>
<p dir="auto">Indeed here is a screenshot for the 1.21.4 Release pages in the <a href="https://numpy.org/doc/1.23/numpy-user.pdf" rel="nofollow">PDF for 1.23 release</a></p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/2589111/210667353-c5a23333-f0c8-49ae-8ab0-77714f06c96f.png"><img src="https://user-images.githubusercontent.com/2589111/210667353-c5a23333-f0c8-49ae-8ab0-77714f06c96f.png" alt="Capture d’écran 2023-01-05 à 00 00 04" style="max-width: 100%;"></a></p>
<p dir="auto">By the way according to Google translate <code class="notranslate">傅立业</code> indicated missing in this screenshot (page 363 in my build of 1.24.1 documentation) means <code class="notranslate">Fourier</code>...</p>
<h3 dir="auto">Idea or request for content:</h3>
<p dir="auto">Unfortunately I personally am very little familiar with <code class="notranslate">xelatex</code> but I think it should be possible to configure it to switch to another font for CJK ideograms, I can not help currently though, but surely others will.</p>
<p dir="auto">By the way, with recent LaTeX (since 2021) one can (via <code class="notranslate">\tracinglostchars3</code> in the preamble) let such missing characters cause a LaTeX build error... if one really really wishes this.</p>
<p dir="auto">Completely unrelated note: I wanted to test how the PDF looked with Sphinx development tip (future 6.1.0).  It does look fine (code-blocks with rounded corners and background gray, tables with rows of alternating grayish colors).  I had to install <code class="notranslate">sphinx_design</code> and then reinstall Sphinx as <code class="notranslate">sphinx_design</code> pins it to <code class="notranslate">&lt;6</code>.</p>