Try the full version of any of our products for up to 30 days,and fall in love with the vast capabilities of ACDSee software. Studio 2 lets you export in H.264, JPEG, ProRes 422 & ProRes 4444. New options have been added to let you export your project at 1:1, exactly the same size as your original recording. IShowU Studio 2.2.2 macOS 25 mbBuilt from day one with a single core idea: easy screen recording editing on your Mac - so that it's easy to capture what you need; edit; and then share where you want to. It's easy to add text, annotations, transitions, pointers and highlights and then share.
September 3, 2019 by Matt Hernandez, @fiveisprime
It's been a couple of months since the initial betas for the Windows Subsystem for Linux 2 (WSL 2) were launched and I wanted to share a bit about what this is all about and how this will help you be more productive. I've been using the beta since it landed in Windows Insiders and I quickly switched over to using WSL 2 exclusively in my daily development tasks.
What's changing in WSL 2
The first version implemented system calls natively on Windows. System calls are essentially functions provided by the kernel, which means that only the calls that were implemented were supported in the WSL environment. You may have noticed this if you used early versions of WSL and found libraries and tools that were attempting to access system calls that hadn't been implemented (for example, the Go debugger). While incremental improvements were made to add support for more functions, WSL 2 takes a completely different approach to this by shipping a lightweight virtual machine with a complete Linux kernel.
That's right, WSL 2 now ships a VM, but it's not the experience you might expect from a VM. Where traditional VMs may be slow to start and feel isolated, WSL 2 is just as seamless as the previous version. Expect high levels of integration between Windows and Linux, extremely fast boot times, a small resource footprint, and absolutely no VM configuration or management.
All of this translates to increased IO performance – up to 20x faster compared to WSL 1 - and full system call capability. Your modules will install quicker, your repositories will clone quicker, and your favorite libraries will work reliably. The increase in performance means you can also run alternate shells such as Zsh and even use your favorite Node.js version management utility.
WSL 2 and Visual Studio Code
If you're following along, make sure you've opted into Windows Insiders builds and enabled WSL 2. You can learn more about how to get started in the Installation instructions for WSL 2.
You'll also need to install Visual Studio Code and the Remote - WSL extension. Optionally, check out the beta Windows Terminal for the best possible terminal experience on Windows.
Open WSL either by launching the Windows Terminal and creating a new WSL tab or by launching the Linux distro that you installed. You can also switch into Linux directly from the Command Prompt or PowerShell by entering
wsl
in the terminal - that's just one of the many ways WSL is so deeply integrated into Windows. You can also use WSL inline to do ridiculous things like…
From your terminal, launch into Visual Studio Code using
code .
from WSL. You can even use wsl code .
to switch to Linux inline, launch into VS Code, then return to your Windows shell. ?
Personally, I'm using WSL 2 for 100% of my development on Windows – all dev tools such as Git and Node.js are installed in my Linux environment. Check out this Tips and Tricks post for more on customizing VS Code in WSL to meet your needs.
![Studio Studio](https://macx.ws/uploads/posts/2016-08/1470830067_ishowustudio.png)
Here's a look at my setup.
Notice in the screenshot that I'm connected to my WSL 2 instance (see 'Ubuntu-18.04' in the bottom-left as the remote source) and I've started a Node.js app from the debugger and it's at a breakpoint. In the Debug console, I've entered
process.platform
to show how the Remote - WSL extension defaults all editor interaction to the Linux environment. There is absolutely no configuration required to get this working, just connect to your WSL environment from the Remote - WSL extension and get to work. Also notice that my line endings are defaulted to LF (shown in the Status bar) without having to set any additional Git configuration options - if you're on Windows working in open source, you understand why this is a big deal.
All my favorite extensions work and are targeting the correct environment. For example, the Source Control view is showing changes to my project using the version of Git that's installed in WSL 2 and the Docker extension is configured to access the Docker Desktop WSL 2 technical preview.
All of this is made possible by using the Remote - WSL extension. Editing, debugging, and even extensions all work exactly the way you've come to expect in your favorite editor.
Benefits of WSL 2
To recap:
- Virtual machines are resource intensive and create a very disconnected experience.
- The original WSL was very connected, but had fairly poor performance compared to a VM.
- WSL 2 brings a hybrid approach with a lightweight VM, a completely connected experience, and high performance.
Add in the Remote - WSL extension in Visual Studio Code and you have the best of all worlds – Linux and Windows compatibility for your tools with excellent performance and a seamless development experience.
Further reading
To help you set up VS Code with WSL, there is a Working in WSL tutorial. If you want to learn more about VS Code Remote and how it can also work over SSH and inside Docker containers, see the full VS Code Remote Development documentation.
Happy Remote Coding,
Matt Hernandez, VS Code Program Manager @fiveisprime
As a popular open source development project, Python has an activesupporting community of contributors and users that also make their softwareavailable for other Python developers to use under open source license terms.
This allows Python users to share and collaborate effectively, benefitingfrom the solutions others have already created to common (and sometimeseven rare!) problems, as well as potentially contributing their ownsolutions to the common pool.
This guide covers the installation part of the process. For a guide tocreating and sharing your own Python projects, refer to thedistribution guide.
Note
For corporate and other institutional users, be aware that manyorganisations have their own policies around using and contributing toopen source software. Please take such policies into account when makinguse of the distribution and installation tools provided with Python.
Key terms¶
-
pip
is the preferred installer program. Starting with Python 2.7.9, itis included by default with the Python binary installers. -
a virtual environment is a semi-isolated Python environment that allowspackages to be installed for use by a particular application, rather thanbeing installed system wide
-
virtualenv
is a third party tools for creating virtual environments, itis defaults to installingpip
into all created virtual environments. -
the Python Packaging Index is a public repository ofopen source licensed packages made available for use by other Python users
-
the Python Packaging Authority are the group ofdevelopers and documentation authors responsible for the maintenance andevolution of the standard packaging tools and the associated metadata andfile format standards. They maintain a variety of tools, documentationand issue trackers on both GitHub andBitBucket.
-
distutils
is the original build and distribution system first added tothe Python standard library in 1998. While direct use ofdistutils
isbeing phased out, it still laid the foundation for the current packagingand distribution infrastructure, and it not only remains part of thestandard library, but its name lives on in other ways (such as the nameof the mailing list used to coordinate Python packaging standardsdevelopment).
Basic usage¶
The standard packaging tools are all designed to be used from the commandline.
The following command will install the latest version of a module and itsdependencies from the Python Packaging Index:
Note
For POSIX users (including Mac OS X and Linux users), the examples inthis guide assume the use of a virtual environment. You may install
virtualenv
to provide such environments using either pip(pipinstallvirtualenv
) or through your system package manager(commonly called virtualenv
or python-virtualenv
).
For Windows users, the examples in this guide assume that the option toadjust the system PATH environment variable was selected when installingPython.
It’s also possible to specify an exact or minimum version directly on thecommand line. When using comparator operators such as
>
, <
or some otherspecial character which get interpreted by shell, the package name and theversion should be enclosed within double quotes:
Normally, if a suitable module is already installed, attempting to installit again will have no effect. Upgrading existing modules must be requestedexplicitly:
More information and resources regarding
pip
and its capabilities can befound in the Python Packaging User Guide.
See also
How do I …?¶
Ishowu Studio 2 2 180
These are quick answers or links for some common tasks.
… install pip
in versions of Python prior to Python 2.7.9?¶
Python only started bundling
pip
with Python 2.7.9. For earlier versions,pip
needs to be “bootstrapped” as described in the Python PackagingUser Guide.
See also
… install packages just for the current user?¶
Passing the
--user
option to python-mpipinstall
will install apackage just for the current user, rather than for all users of the system.
… install scientific Python packages?¶
A number of scientific Python packages have complex binary dependencies, andaren’t currently easy to install using
pip
directly. At this point intime, it will often be easier for users to install these packages byother meansrather than attempting to install them with pip
.
See also
… work with multiple versions of Python installed in parallel?¶
On Linux, Mac OS X and other POSIX systems, use the versioned Python commandsin combination with the
-m
switch to run the appropriate copy ofpip
:
Ishowu Studio 2 2 18 Inch
(appropriately versioned
pip
commands may also be available)
On Windows, use the
py
Python launcher in combination with the -m
switch:
Common installation issues¶
Installing into the system Python on Linux¶
On Linux systems, a Python installation will typically be included as partof the distribution. Installing into this Python installation requiresroot access to the system, and may interfere with the operation of thesystem package manager and other components of the system if a componentis unexpectedly upgraded using
pip
.
On such systems, it is often better to use a virtual environment or aper-user installation when installing packages with
pip
.
Pip not installed¶
It is possible that
pip
does not get installed by default. One potential fix is:
There are also additional resources for installing pip.
Installing binary extensions¶
Python has typically relied heavily on source based distribution, with endusers being expected to compile extension modules from source as part ofthe installation process.
With the introduction of support for the binary
wheel
format, and theability to publish wheels for at least Windows and Mac OS X through thePython Packaging Index, this problem is expected to diminish over time,as users are more regularly able to install pre-built extensions ratherthan needing to build them themselves.
Some of the solutions for installing scientific softwarethat is not yet available as pre-built
wheel
files may also help withobtaining other binary extensions without needing to build them locally.
See also