🐛 bug fixes

We closed 14 bug issues this release 👏

• #1826 - Fixed panic/crash caused by capacity overflow with large tuple expansion.
• #1809 - Fixed __future__ imports being incorrectly flagged as unused, as they have necessary module-level side effects.
• #1794 - Fixed a panic/crash when a text range calculation exceeded the document buffer size limit.
• #1418 - Fixed function hover popups (especially in numpy) missing the function name in the header when resolving from stub files.
• #1289 -Fixed special casing for numba jit decorators (corrected path handling).
• And more: #1348, #1214, #820, #253, #1667, #1787, #1799, #1821, #1709

Thank-you to all our contributors who found these bugs and reported them! Did you know this is one of the most helpful contributions you can make to an open-source project? If you find any bugs in Pyrefly we want to know about them! Please open a bug report issue here

📦 Upgrade

pip install --upgrade pyrefly==v0.46.0

How to safely upgrade your codebase

Upgrading the version of Pyrefly you're using or a third-party library you depend on can reveal new type errors in your code. Fixing them all at once is often unrealistic. We've written scripts to help you temporarily silence them. After upgrading, follow these steps:

1. pyrefly check --suppress-errors
2. run your code formatter of choice
3. pyrefly check --remove-unused-ignores
4. Repeat until you achieve a clean formatting run and a clean type check.

This will add # pyrefly: ignore comments to your code, enabling you to silence errors and return to fix them later. This can make the process of upgrading a large codebase much more manageable.

Read more about error suppressions in the Pyefly documentation

🖊️ Contributors this release

@javabster, @AryanBagade, @asukaminato0721, @connernilsen, @DanielNoord, @yangdanny97, @dearfl, @fangyi-zhou, Jack, @jvansch1, @kinto0, Liam, @arthaud, @rchen152, @samwgoldman, @stroxler, @tianhan0, @migeed-z