Updating mypy test coverage

enchancing mypy coverage

enchancing mypy coverage

handle_line_and_cell

modify-parser-logic

fix-time-magic-interrupt-handling

Fix attribute completion for expressions with comparison operators (#14898) ## Fixes #14897 ### Description Modified `_attr_matches()` to check if an expression contains comparison operators `(=, ==, !=, etc.)` outside of parentheses. If so, it extracts the right-hand side of the operator for evaluation, providing appropriate completions. For parenthesized expressions like `(x==y).<tab>`, the code preserves the entire expression to ensure it's evaluated as a bool. Fixing completions fully is quite tricky. The current implementation still has flaws, especially in cases where comparison operators are involved. For example: ```python {"==", "abc"}.<tab> ``` In this case, dictionary methods are not shown because the logic incorrectly separates the expression at the `"=="` operator. While the current solution resolves some major issues, it also introduces new, albeit minor, ones. Feedback on better approaches or alternative strategies is highly appreciated.

fix-lint

add-test-case

strip-on-all-operators

improve-code-strip-logic

remove-comment

handle_edge_case_1

improve-completer

Remove unused import

back to dev

release 9.2.0

Add what's new for IPython 9.2 and 8.36 (#14892) Add what's new for IPython 9.2 and 8.36

Add what's new for 9.2 and 8.36

docs: Recommend `ipykernel.embed.embed_kernel()` (#14887) Followup to #14734, cc @Carreau Following the current doc prints warning: https://github.com/ipython/ipython/blob/aa25535d3765641e31f1d218537540e41b6f1a74/IPython/__init__.py#L96-L98 (which BTW sounded to me like it was deprecated since 2013 — I assume the meaning is that `ipykernel.embed` works since 2013?) ---- P.S. Mild argument against the deprecation: IMHO, it's convenient to remember one place to import both `embed` and `embed_kernel` from. These are most useful if memorized, so one can type them without thinking, similar to how we all used to memorize `import pdb; pdb.set_trace()` — but became easier to teach with py3.7 `breakpoint()`. There is no `ipykernel.embed.embed`, and I assume won't be, as it starts an in-process shell which is _not really a kernel_? But both are legitimate under `IPython`. ---- There is also a question which package(s) one must install to use these forms — _and does this need documenting_? * I see that a clean env `uvx --with ipykernel python` also drags in IPython as a dependency, so both forms work. * OTOH `uvx --with IPython python` allows importing IPython but not ipykernel. In such env, `IPython.embed_kernel()` is **importable but broken**: ``` File "/home/beni/.cache/uv/archive-v0/_NUp3oIPKrkvaYJk8f7Nm/lib64/python3.13/site-packages/IPython/__init__.py", line 110, in embed_kernel from ipykernel.embed import embed_kernel as real_embed_kernel ModuleNotFoundError: No module named 'ipykernel' ``` This was counter-intuitive, and the deprecation avoids that! I guess "install what you import" is a better quality then my above concern with "easy to remember" :+1: - [x] Should the API doc https://ipython.readthedocs.io/en/stable/api/generated/IPython.html#IPython.embed_kernel also mention it's deprecated? - [x] Should the API doc also mention it will not work without optional `ipykernel` dependency?