2019.3 EAP 3

Posted on by Joaquin Treviño

A new version of the Early Access Program (EAP) for PyCharm 2019.3 is available now! Download it from our website.

New for this version

Literal types support

Python 3.8 release is right around the corner and we are working on supporting its latest features. PyCharm 2019.3 EAP 3 introduces the support for Literal types. Literal types is Python 3.8’s new alternative to define type signatures for functions (PEP-0586). With this now you have the ability to indicate that some expression expects a specific and concrete value.

Screenshot 2019-09-26 at 11.54.59 AM

Further improvements

  • Our stub support was extended to support proper code autocompletion for modules like ‘sys’, ‘logging’, ‘concurrent’ and ’email’.
  • An issue causing the output of a Jupyter notebook not to render properly was fixed.
  • We renamed the tabs for the Jupyter toolwindow to avoid confusions. Now it will more obvious that the outer one refers to the process and the inner one to its output.
  • For more details on what’s new in this version, see the release notes

Interested?

Download this EAP from our website. Alternatively, you can use the JetBrains Toolbox App to stay up to date throughout the entire EAP.

If you’re on Ubuntu 16.04 or later, you can use snap to get PyCharm EAP, and stay up to date. You can find the installation instructions on our website.

Comments below can no longer be edited.

9 Responses to 2019.3 EAP 3

  1. Skip Montanaro says:

    July 23, 2015

    Alas, as someone who has never used PyCharm before, I can’t see how to “create a file with an .ipynb extension.” I get two choices: open an existing file or create a new project. The former fails if the file doesn’t exist. The latter seems to want to create something much more complex than a single file.

    • Dmitri Nesteruk says:

      July 24, 2015

      Oh, you need to be working with a Python project already. Once you’ve got a project open, simply go to New|File, and specify a filename with a .ipynb extension.

  2. Russel Winder says:

    July 24, 2015

    But do remember that IPython Notebook has morphed into Jupyter: https://jupyter.org/

  3. Yury V. Zaytsev says:

    July 25, 2015

    You could have as well mentioned Pandas next to NumPy and SciPy in the context of quantitative research.

  4. Google’s Deep Dream in PyCharm | JetBrains PyCharm Blog says:

    August 7, 2015

    […] The example code for image generation kindly shared by Google is available as an IPython Notebook on Google’s GitHub repository. I couldn’t miss the chance to try it in PyCharm. PyCharm natively supports IPython Notebook since v4 as described in this blog post. In the latest v4.5, this support is even better and can be applied to many areas, including quantitative research as described here. […]

  5. walter says:

    August 13, 2015

    I’m trying it, I start up ipython in a window console with the command:
    ipython notebook –profile=pyspark
    and then create a new file with extension on pycharm with extension .ipynb, but
    it doesn’t recognize the ‘sc’ variable context
    a help would be highly appreciated

    thank you

  6. Chris Seymour says:

    March 31, 2016

    I get a message that says ipython notebook is deprecated — how can that be changed to use jupyter notebook ?

    Thank you

  7. Scott Palmer says:

    October 31, 2019

    Will PyCharm 2019.3 support *typing_extensions* package just as it does *typing* package?
    Both are written by the CPython team.

    https://pypi.org/project/typing-extensions/
    https://github.com/python/typing/tree/master/typing_extensions

    For example..

    Will the inspector treat:
    `from typing import Literal`
    the same as:
    `from typing_extensions import Literal`

    • Paul Everitt says:

      November 1, 2019

      The first line of the README says that typing_extensions is experimental.

Subscribe

Subscribe for updates