Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Visual Studio Code's Python extension goes to Jupyter

A preview of next year's .NET Framework also emitted

The hardworking elves toiling in the corridors of Redmond loaded up Santa's sled with two more developer treats in the form of Python updates for Visual Studio Code and a fresh preview of the venerable .NET Framework.

Jupyter Ascending

Fresh from an early November release rammed with data science goodness, the team responsible for the Python extension for Visual Studio code has added more Jupyter support for a bit of festive fun.

Or at least as festive as data scientists get after a hard day's work spent crushing the dreams of children.

Jupyter itself is an open-source project (naturally) that arose from the IPython project and is geared towards data science across multiple programming languages including, of course, Python.

A key part of the Jupyter project is the Notebook concept – effectively a JSON document containing all manner of handy information such as code, mathematics and annotations. The aim is to document, execute and explain the results of the sometimes brain-melting data science involved.

In November, the VS Code Python team added the ability to import Jupyter Notebooks into the open-source code wrangler. Of course, the extension only pulled out actual Python code and Markdown blocks – there would be little point in extracting much else – but was directionally limited. It was possible to export the results spat out by code, but that was pretty much it.

The new release adds the ability to export Python code as Jupyter Notebooks, further closing the loop.

Support for Remote Jupyter Notebooks has also made an appearance, allowing resource-intensive computation to be offloaded elsewhere if needed.

.NET Framework – still not dead

Microsoft would really, really like you to be looking at the shiny open source .NET Core. However, if you are still shackled to the venerable .NET Framework, the software giant had a treat for those hardy souls unafraid of pre-production code, in the form of a fresh preview of version 4.8.

Running on all flavours of Windows 10 from version 1607 as well as Windows 8.1 and Windows 7, the preview brings a torrent of fixes to the framework as its 2019 release nears.

The promised DPI awareness continues to spread over Windows Forms, with the PropertyGrid and ToolStrip now understanding per monitor DPI. The Windows Presentation Framework (WPF) has received a fix for an infinite loop issue arising from the setting of the height of a listbox, among other improvements.

The Common Language Runtime (CLR) and the Base Class Library (BCL) have also seen bugs squashed in what, in our experience, seems like a pretty stable release. Not that we'd let it anywhere near a production environment, of course.

Microsoft plans a few more releases of the aging framework over the coming months, meaning Build 3707 is not the last word on the thing. It will also make an appearance in the next update for Windows 10. ®

 

Similar topics

TIP US OFF

Send us news


Other stories you might like