JupyterLab VS ruff

Does this allow to run a long running task in the background so that a user can close & reopen the tab and continue seeing all the output that has been produced thus far?

This is currently being worked on in Jupyter: https://github.com/jupyterlab/jupyterlab/pull/15448

This is a problem with codemirror 6. You can upvote https://github.com/jupyterlab/jupyterlab/issues/14589 and help by contributing (or sponsor someone to do so)

https://github.com/jupyterlab/jupyterlab/issues/12422

That whole issue feels so stupid.

I quite enjoy jupyter lab otherwise, even if a lot of it is brittle and annoying.

Could you add your details to https://github.com/jupyterlab/jupyterlab/issues/14625 it seems like a browser specific kssue

This will be possible in JupyterLab 4.0 and Jupyter Notebook 7 to be released in Q2/Q3 this year, see https://github.com/jupyterlab/jupyterlab/pull/13285

The posted SO is irrelevant. The true answer is that a new dependency included in 3.6 did not have binaries for some platforms. These were now uploaded so after refreshin pip cache you should be good to go. If it still does not work please post details in https://github.com/jupyterlab/jupyterlab/issues/13920

After a quick look I found the same issue here.

Yes, Jupyter notebook has used CodeMirror for nearly a decade. The official Jupyter notebook has never used Monaco, but the Google version (colab) uses Monaco in order to very nicely leverage LSP support (similar to VS Code). There is preliminary work under way right now to switch from CodeMirror 5 to CodeMirror 6 in the official Jupyter project, but that's going to be significant work (see https://github.com/jupyterlab/jupyterlab/pull/11638).

It doesn't seem like there is much overlap between Replit and Jupyter notebooks right now, as far as I can tell...

With the support of a team member with prior experience auditing for accessibility, we pinpointed specific ways in which JupyterLab lacked support for accessibility broken up by WCAG 2.1 standards.

Leverage Python Tools: Tapyr takes advantage of Python’s ecosystem tools, including ruff, pytest, and others.

I think I mention this all the time when this comes up, but I learned the most 'best practices' through using ruff.

https://docs.astral.sh/ruff/

I just installed and enabled all the rules by setting

Ruff is a Python linter that helps to identify and remove code smells. Over 700 built-in rules: Ruff includes native re-implementations of popular Flake8 plugins, like flake8-bugbear. And also built-in caching to avoid re-analyzing unchanged files.

Because the Python's "ast" modules is too slow, and lacks proper "format" feature (it has unparse but it removes comments, and forgets the current style completely). I use "ruff" a lot (https://github.com/astral-sh/ruff) which is in Rust. But I want to be able to implement fast custom linters in Go (linters that ruff / fixit lack, and Python linters lack or are too slow).

I think it’s interesting that rye uses ruff (https://github.com/astral-sh/ruff) for linting and formatting. That’s the right call, and it’s also correct to bundle that in for an integrated dev experience.

I had to guess, that’s the path that the Astral team would take as well - expand ruff’s capabilities so it can do everything a Python developer needs. So the vision that Armin is describing here might be achieved by ruff eventually. They’d have an advantage that they’re not a single person maintenance team, but the disadvantage of needing to show a return to their investors.

Adding more weight to ease of setup and configurability, the choice came down on flake8. It is easy to integrate, since its also available through pip and let’s you configure which standards you want to omit by simply stating them as a list via the --ignore switch. Moving to ruff appears quite smooth, so future updates may do so.

I confess I stole the pip recipe from Charlie :D

https://github.com/astral-sh/ruff/blob/main/.github/workflow...

Ruff is an emerging tool in the Python ecosystem that describes itself as "an extremely fast Python linter and code formatter, written in Rust".