Ouranosinc / xclim / 36919560411
91%

DEFAULT BRANCH: main
Ran
Jobs 0
Files 0
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
36919560411

push

github

web-flow 
Bump pylint from 4.0.8 to 4.0.9 in /.github (#2440)

Bumps [pylint](https://github.com/pylint-dev/pylint) from 4.0.8 to
4.0.9.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pylint-dev/pylint/releases">pylint's
releases</a>.</em></p>
<blockquote>
<h2>v4.0.9</h2>
<h2>What's new in Pylint 4.0.9?</h2>
<p>Release date: 2026-09-23</p>
<h2>Security Fixes</h2>
<ul>
<li>Someone without access to the configuration or linted code, but with
access
to the cache directory (predictable <code>PYLINT_HOME</code> on a
multi-user host) can no
longer write a crafted pickle that will runs arbitrary code when pylint
access its
stat cache. The result cache is now stored as JSON instead of pickle,
preventing code-execution. The workaround is upgrading or not pointing
<code>PYLINT_HOME</code>
to an untrusted, shared, or group-writable directory. The default value,
<code>~/.cache/pylint</code>,
is writable only by the user running pylint. (CVE with the same
information pending)</li>
</ul>
<h2>False Positives Fixed</h2>
<ul>
<li>
<p>Fixed a false positive for <code>no-self-use</code> on a method that
only uses
<code>self</code> before a locally defined class (or other nested
method), because
the checker's could-be-a-function tracking state was not restored after
visiting the nested method.</p>
<p>Closes <a
href="https://redirect.github.com/pylint-dev/pylint/issues/3705">#3705</a></p>
</li>
<li>
<p>Fix a false positive for :ref:<code>not-callable</code> when calling
functions constructed with
<code>types.FunctionType</code> or <code>types.LambdaType</code>.</p>
<p>Closes <a
href="https://redirect.github.com/pylint-dev/pylint/issues/7500">#7500</a></p>
</li>
<li>
<p>Fix a false positive for <code>unnecessary-direct-lambda-call</code>
when a directly called
lambda in a class body wraps a comprehension containing an assignment
expression.
PEP 572 makes that a <code>SyntaxError</code> without the lambda's
scope, so following the
message p... (continued)
Source Files on build 36919560411
Detailed source file information is not available for this build.