IPython 8

[Carreau]

Text styling

• [x] The blog is written with plain language (where relevant).
• [x] If there are headers, they use the proper header tags in order to do so (with only one level-one header).
• [x] All links describe where they link to (for example, check the Quansight labs website).
• [x] Any kind of styling that the author uses (for example, bold for emphasis) is consistent throughout the blog.

Non-text contents

• [x] All content is represented as text (for example, images need alt text and videos need captions or descriptive transcripts).
• [x] If there are emojis, there are not more than three in a row.
• [x] Don't use flashing gifs or videos.
• [x] If it were to be read as plain text, the blog still makes sense and no information is missing.

[netlify[bot]]

✔️ Deploy Preview for admiring-northcutt-a5be8c ready!

🔨 Explore the source changes: daf8bdfba53fd19c8f73df71a1de35066844608a

🔍 Inspect the deploy log: https://app.netlify.com/sites/admiring-northcutt-a5be8c/deploys/61ded543c61f3f0008717ccc

😎 Browse the preview: https://deploy-preview-289--admiring-northcutt-a5be8c.netlify.app

[Carreau]

Thanks @thomasjpfan , I've updated the sections you commented on.

[ccordoba12]

I don't understand: why this one was merged before the final IPython 8 release?

[Carreau]

Because it was uploading while I merged.

https://pypi.org/project/ipython/8.0.0/

[ccordoba12]

Ups, sorry about that. Since I saw a placeholder link for a release announcement at the Jupyter blog, I thought this could be a mistake.

[Carreau]

I also needed the URL to be live to update https://blog.jupyter.org/release-of-ipython-8-0-6e034ff122ef and link to it, this other blog post was published at the "same" time.

[rgommers]

Nice post Matthias!

[Carreau]

Ups, sorry about that. Since I saw a placeholder link for a release announcement at the Jupyter blog, I thought this could be a mistake.

Yeah it's a bit of a chicken and egg problem, I need to publish and update after, and it takes time to deploy. I think I should be able to guess the final URL but I was a bit lazy. It should be fixed in the source now, but will take time to hit CDN.

Nice post Matthias!

Thanks ! Any chance for numpy to grow a version_info tuple ?

[rgommers]

Thanks ! Any chance for numpy to grow a version_info tuple ?

Depends, for what? There's a bunch of flavors in np.version, but that's a weird thing. The only thing that was meant to be public was np.__version__.

There's no standard for a tuple version; the string can adhere to PEP 440. So is a tuple useful?

[Carreau]

So is a tuple useful

It's much easier to compare, especially since tuple don't need to be the same length:

>>> (3,) < (7,3,'7rc')
True

Using a version string is tricky as I pointed in the post as splitting on dots and converting to int may fail. For me at least a tuple that has major/minor as numeric values.

The following would be cool for me

version_info = packaging.version.parse(numpy.__version__).release

Also numpy is taken as an example by many other project in the scientific ecosystem. Or at least if not a tuple, expose a version object that properly compare itself to tuples, so that dependees don't roll their own parsing logic.

[rgommers]

Okay, we can add it I think. As a plain tuple of 3 integers. I'd prefer it be called version_tuple rather than version_info. Wanna submit a PR?

[Carreau]

Okay, we can add it I think. As a plain tuple of 3 integers. I'd prefer it be called version_tuple rather than version_info. Wanna submit a PR?

https://github.com/numpy/numpy/pull/20803