home.social

#ipython — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ipython, aggregated by home.social.

fetched live
  1. Every terminal debugger forces a choice: a REPL with full evaluation power but no source context, or an editor with visual breakpoints but a crippled debug console. dap-mux removes the need to choose.

    Connect your editor and your REPL to the same debug session. Both are first-class clients. Neither knows the other is there.

    Ships with an IPython frontend. Speaks standard DAP — any language, any editor. This is the very first release. There's so much work to do.

    github.com/dap-mux/dap-mux
    #Python #debugging #Helix #neovim #IPython

  2. Taking a python path on plural sight now, and I find it puzzling that none of these python suggest installing `ipython` ... Why is it so?

    #python #ipython #question #fediverse #askfedi #computerscience #datascience #devops #linux

  3. Taking a python path on plural sight now, and I find it puzzling that none of these people suggest installing `ipython` ... Why is it so?

    #python #ipython #question #fediverse #askfedi #computerscience #datascience #devops #linux

  4. #sagemath #ipython #kitty #kitten #kissat
    Много лет пользуюсь
    x11-terms/kitty поэтому радуюсь появлению https://github.com/sagemath/sage/issues/42054
    sci-mathematics/kissat я собираю с --no-kitten)

  5. Did not expect to get a reminder about International Transgender Day of Visibility in #ipython, but glad I did :)

  6. Nice tip from IPython today.

    > Tip: Happy International Transgender Day of Visibility! You are valid. You matter. en.wikipedia.org/wiki/Internat

    #Python #IPython

  7. Nice tip from IPython today.

    > Tip: Happy International Transgender Day of Visibility! You are valid. You matter. en.wikipedia.org/wiki/Internat

    #Python #IPython

  8. Windows at work, always a fresh inconvenience:

    C:\>python -m pip install ipython
    Requirement already satisfied: ipython in c:\users\[...]

    C:\>ipython
    'ipython' is not recognized [...]

    #ipython #windows #python

  9. Windows at work, always a fresh inconvenience:

    C:\>python -m pip install ipython
    Requirement already satisfied: ipython in c:\users\[...]

    C:\>ipython
    'ipython' is not recognized [...]

    #ipython #windows #python

  10. I'm still learning how to submit a patch or pull request to Guix to propose updated definitions of some packages... but---while I figure things out---here's a general guide on how to get new packages installed by defining package variants and rewriting package inputs. In short, the steps to do so are:

    1. Get the sha256sum hash in the nix-base-32 format (either via `guix download` or `guix hash` of a repository)
    2. Prepare the package variant Scheme file (see images; e.g. "package-variant.scm")
    3. Run `guix build -f ./package-variant.scm` to build the new package in the store
    4. (Optional, but recommended) Test that things work by running `git shell -f ./package-variant.scm`
    5. Install the package by running `guix package -f ./package-variant.scm`

    #guix #python #emacs #JupyterNotebook #ipython #sql #package #variants

  11. I'm still learning how to submit a patch or pull request to Guix to propose updated definitions of some packages... but---while I figure things out---here's a general guide on how to get new packages installed by defining package variants and rewriting package inputs. In short, the steps to do so are:

    1. Get the sha256sum hash in the nix-base-32 format (either via `guix download` or `guix hash` of a repository)
    2. Prepare the package variant Scheme file (see images; e.g. "package-variant.scm")
    3. Run `guix build -f ./package-variant.scm` to build the new package in the store
    4. (Optional, but recommended) Test that things work by running `git shell -f ./package-variant.scm`
    5. Install the package by running `guix package -f ./package-variant.scm`

    #guix #python #emacs #JupyterNotebook #ipython #sql #package #variants

  12. The site has a handful of "synthetic users" that serve to hold items from external sources like debug pages and the "%pastebin" magic. Their profile pages recently got a little revamp, with a bot icon and more account info.

    If you'd like a similar setup for your public dpaste.com integration, drop a line!

    * dpaste.com/profile/2
    * dpaste.com/profile/1003

  13. How to best create, maintain and archive custom environments from within Jupyter? .. just updated the documentation for Carto-Lab Docker with examples for Python [1] and R [2].

    The tricky part is linking Kernels from custom envs with a Jupyter kernelspec (specifically if the Jupyter server and the Kernel are in two different environments). However, most of this can be stored in Jupyter notebook cells, for reproducibility.

    There's also a section on archival of package versions with Conda's `env export` (yml approach) and `conda list --explicit` (full archival).

    [1]: cartolab.theplink.org/use-case
    [2]: cartolab.theplink.org/use-case

    #jupyter #R #ipython # #reproducibility #Notebooks #conda

  14. Do you use pg.ConsoleWidget and have some preference for it over ‘s QtConsole? If so I’d like to hear from you. We’re considering deprecating ConsoleWidget and directing users to use the Jupyter/IPython QtConsole instead.

  15. Jeden błąd w #PyPy naprawiony, i #IPython w #Gentoo jest na #PyPy 3.11.

    Jeden błąd w bibliotece standardowej #Pythona naprawiony, #Django w Gentoo jest na PyPy 3.11.

    Powiedziałbym, że całkiem udany dzień.

    github.com/pypy/pypy/pull/5239
    github.com/python/cpython/pull

    #Python

  16. Some fun numbers: out of 823 packages featuring #PyPy 3.x support in #Gentoo, 712 have already been ported to PyPy 3.11. There are a few significant blockers left (notably #IPython, with hanging IPyParallel), and a fair number of packages that simply don't have tests (so I haven't looked at them yet).

    Interesting enough, the most common test failures seen while porting to PyPy 3.11 are:

    • flaky tests (i.e. just need to rerun, especially without parallelization of testing 70 packages simultaneously)
    • existing, irrelevant test regressions (i.e. confirmed by testing with CPython 3.11)
    • existing test problems with PyPy3.10 (i.e. need to copy deselects)
    • some minor differences, such as slightly different exception messages

    Serious issues are really rare, and they are often fixed (or worked around by me) promptly. Really great release! Thanks to everyone involved!

  17. Some fun numbers: out of 823 packages featuring #PyPy 3.x support in #Gentoo, 712 have already been ported to PyPy 3.11. There are a few significant blockers left (notably #IPython, with hanging IPyParallel), and a fair number of packages that simply don't have tests (so I haven't looked at them yet).

    Interesting enough, the most common test failures seen while porting to PyPy 3.11 are:

    • flaky tests (i.e. just need to rerun, especially without parallelization of testing 70 packages simultaneously)
    • existing, irrelevant test regressions (i.e. confirmed by testing with CPython 3.11)
    • existing test problems with PyPy3.10 (i.e. need to copy deselects)
    • some minor differences, such as slightly different exception messages

    Serious issues are really rare, and they are often fixed (or worked around by me) promptly. Really great release! Thanks to everyone involved!

  18. It's been a while without news, but #IPython 9.0 beta 1 is out. "biggest" features are complete rewrite of the theme engine which now supports arbitrary colors, and unicode (I'd love new themes please !) also optional LLM integrations. PLease help me write the changelog as well : ipython.readthedocs.io/en/late

  19. It's been a while without news, but #IPython 9.0 beta 1 is out. "biggest" features are complete rewrite of the theme engine which now supports arbitrary colors, and unicode (I'd love new themes please !) also optional LLM integrations. PLease help me write the changelog as well : ipython.readthedocs.io/en/late

  20. I have no idea what magic makes this possible, but I love it: github.com/evcxr/evcxr/blob/ma #Evcxr, a #Rust #Jupyter kernel.

    I've been planning to actually sit down and start learning the language finally but have been putting it off.

    But... a Rust REPL in Jupyter? Yes, Finally. #IPython/Jupyter have become my natural habitat over the past decade. This will make playing around with and learning to think in Rust *much* easier.

  21. Wow! New #Python discovery, I knew you could invoke a python or #ipython shell inside a script to examine variables and such, but I somehow always thought it was impossible to actually change them. Turns out there is no such protection in place, you can jump into an ipython shell in a running program with lots of threads doing stuff and manually actually... do stuff. Added a shell drop command to debug - now it's the most powerful UI element and my whole namespace is just.. there.

  22. #Jupyter #Python folks:

    Anyone else find that you just do *everything* in Jupyter and #ipython?

    Every time I boot up my computer, I start a #jupyterlab server running and launch a browser to connect to it. That browser window will then run in full-screen on it's own desktop for days, weeks, possibly months to come, various notebook tabs being opened and closed and a scratch notebook always open for just doing "stuff" on my computer (whatever I wanna use my computer for at the moment).

  23. A guide on integrating #emacs + #python + #hatch using [mostly] builtin tooling and project local .dir-locals.el variables.

    Specifically, this setup uses #Eglot + #pyright for live syntax checking, #pytest for code running, #MyPy for type-checking, and #IPython as the shell

    Feedback would be welcome -- trying to get it robust + idiomatic.

    jtmoulia.srht.site/guides/emac

  24. Great, #IPython finally fixed #PyTest 8 compatibility.

    Oh, wait… they've just fixed one trivial issue and declared it fixed, without actually testing at all or looking at the bugs already reported. Quality work!

    github.com/ipython/ipython/com

    #Gentoo #Python

  25. Recently I've added a cheap hack to the standard #Gentoo invocation for #PyTest to throw errors if unhandled async functions are detected. The goal was to increase our chances of finding packages with missing dependency on dev-python/pytest-asyncio (or another equivalent plugin), or packages disabling plugin autoloading and failing to load such a plugin.

    Today, I've gotten a first bug report, regarding dev-python/ipython. I've grepped the sources and confirmed that the package depends on PyTest-AsyncIO, except that it pins to < 0.22. Well, we don't have one that old but let's hope it works anyway. So I've tried adding the dep, `-p asyncio`… and PyTest still apparently couldn't find the plugin. I've scratched my head and tried `PYTEST_PLUGINS` instead — still the same result. What the…?

    So I've checked the git repository out, tried with older PyTest-AsyncIO, and indeed the tests worked. Tried with the newest, 0.23.6, and the same issue occurred. I've checked the git history and discovered that the version pin was added because of a buggy 0.22.0 release. However, the issue has been fixed since, the release was yanked and my problem was nothing like that.

    So I've investigated more. For some reason, #IPython test suite does not mark tests with `pytest.mark.asyncio` marker directly. Instead, it globally iterates over all test functions, and implicitly adds the marker to all coroutines. This used to work with older versions, but does not work anymore — the test is correctly marked, but for some reason it stops being recognized as a coroutine. So I've made a minimal reproducer and filed a bug.

    The key point here is: the (potential) bug went unnoticed for a while now, because of the premature, then obsolete pin in IPython.

    gitweb.gentoo.org/repo/gentoo.
    bugs.gentoo.org/928411
    github.com/ipython/ipython/com
    github.com/pytest-dev/pytest-a

    #Python

  26. #IPython 8.23 includes improved autocomplete (when jedi is turned off) now being able to suggest completions based on advanced Python return type annotations (like `Literal`, `Protocol`, `Union`, etc). github.com/ipython/ipython/pul

    chaos.social/@Mbussonn/1121904

  27. New #IPython release 8.23, see what's new there. ipython.readthedocs.io/en/8.23 Usually on Fridays, but for one on Sunday. So dedicated to out :trans_flag: friends. #TransDayOfVisiblity ❤️

  28. You can use a question mark in any #iPython derivative, such as #Jupyter.

  29. Using #IPython #Jupyter Magic Commands to Improve the #JupyterNotebook Experience

    The article we’ll show how your team can turn any utility function(s) into reusable IPython Jupyter magics.

    By Stefan Krawczyk | Feb, 2024 | Towards Data Science towardsdatascience.com/using-i

    #Programming

  30. CW: asdf, python, ipython, fish shell, borken

    Ich mach
    > asdf install python 3.12.2; and asdf global python 3.12.2; and python -m pip install ipython; and echo it should work now

    Am Ende steht da "it should work now".

    "ipython" eingeben führt dann aber zu
    > No preset version installed for command ipython
    > Please install a version by running one of the following:
    >
    > asdf install python 3.12.2

    Isses #asdf, oder #python bzw #ipython unter asdf oder unter #fish, oder wie oder was?