We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
conda update spyder
pip
jupyter qtconsole
spyder --reset
In Spyder 6.0.0b1, inline code analysis is truncated and does not show the source of the error, see attached image:
Compare with Spyder 5.5.4:
In this case, the error (mypy str-bytes-safe) comes via pylsp-mypy, in case it's relevant.
f"{b''}"
The same thing may happen with long error messages other than str-bytes-safe, but I haven't been able to find one long enough to test.
The output should not be truncated, or should include the error source (mypy str-bytes-safe in this case) even after truncation.
# Mandatory: aiohttp >=3.9.3 : 3.9.5 (OK) asyncssh >=2.0.0,<3.0.0 : 2.14.2 (OK) atomicwrites >=1.2.0 : 1.4.0 (OK) chardet >=2.0.0 : 4.0.0 (OK) cloudpickle >=0.5.0 : 2.1.0 (OK) cookiecutter >=1.6.0 : 1.7.3 (OK) diff_match_patch >=20181111 : 20200713 (OK) intervaltree >=3.0.2 : 3.1.0 (OK) IPython >=8.13.0,<9.0.0,!=8.17.1 : 8.18.1 (OK) jedi >=0.17.2,<0.20.0 : 0.18.1 (OK) jellyfish >=0.7 : 0.9.0 (OK) jsonschema >=3.2.0 : 4.5.1 (OK) keyring >=17.0.0 : 23.5.1 (OK) nbconvert >=4.0 : 6.5.0 (OK) numpydoc >=0.6.0 : 1.3.1 (OK) parso >=0.7.0,<0.9.0 : 0.8.3 (OK) pexpect >=4.4.0 : 4.8.0 (OK) pickleshare >=0.4 : 0.7.5 (OK) psutil >=5.3 : 5.9.1 (OK) pygments >=2.0 : 2.17.2 (OK) pylint >=3.1,<4 : 3.1.0 (OK) pylint_venv >=3.0.2 : 3.0.2 (OK) pyls_spyder >=0.4.0 : 0.4.0 (OK) pylsp >=1.11.0,<1.12.0 : 1.11.0 (OK) pylsp_black >=2.0.0,<3.0.0 : 2.0.0 (OK) pyuca >=1.2 : 1.2 (OK) qdarkstyle >=3.2.0,<3.3.0 : 3.2.3 (OK) qstylizer >=0.2.2 : 0.2.2 (OK) qtawesome >=1.3.1,<1.4.0 : 1.3.1 (OK) qtconsole >=5.5.1,<5.6.0 : 5.5.1 (OK) qtpy >=2.4.0 : 2.4.1 (OK) rtree >=0.9.7 : 1.0.0 (OK) setuptools >=49.6.0 : 62.3.2 (OK) sphinx >=0.6.6 : 4.5.0 (OK) spyder_kernels >=3.0.0b6,<3.0.0b7 : 3.0.0b6 (OK) superqt >=0.6.1,<1.0.0 : 0.6.6 (OK) textdistance >=4.2.0 : 4.2.2 (OK) three_merge >=0.1.1 : 0.1.1 (OK) watchdog >=0.10.3 : 2.1.8 (OK) xdg >=0.26 : 0.27 (OK) yarl >=1.9.4 : 1.9.4 (OK) zmq >=24.0.0 : 25.0.2 (OK) # Optional: cython >=0.21 : None (NOK) matplotlib >=3.0.0 : 3.5.2 (OK) numpy >=1.7 : 1.22.4 (OK) pandas >=1.1.1 : 1.4.2 (OK) scipy >=0.17.0 : 1.8.1 (OK) sympy >=0.7.3 : None (NOK)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue Report Checklist
conda update spyder
(orpip
, if not using Anaconda)jupyter qtconsole
(if console-related)spyder --reset
Problem Description
In Spyder 6.0.0b1, inline code analysis is truncated and does not show the source of the error, see attached image:
Compare with Spyder 5.5.4:
In this case, the error (mypy str-bytes-safe) comes via pylsp-mypy, in case it's relevant.
What steps reproduce the problem?
f"{b''}"
in a new file and save it.The same thing may happen with long error messages other than str-bytes-safe, but I haven't been able to find one long enough to test.
What is the expected output? What do you see instead?
The output should not be truncated, or should include the error source (mypy str-bytes-safe in this case) even after truncation.
Versions
Dependencies
The text was updated successfully, but these errors were encountered: