Friday, May 24, 2024
HomePythonThe PyCharm 2022.2.1 Launch Candidate Is Now Accessible!

The PyCharm 2022.2.1 Launch Candidate Is Now Accessible!


We’re working intently together with your suggestions on the PyCharm 2022.2 model that was launched final week. Thanks for sharing with us! Should you encounter a difficulty in PyCharm 2022.2, please attain out to our assist crew. We’re actively fixing regressions, and shall be delivering a minor bug-fix launch quickly.

You will get the brand new construct from our web page, by way of the free Toolbox App, or by utilizing snaps for Ubuntu. 

At the moment, the discharge candidate for the primary minor replace is offered. Listed below are the foremost fixes:

  • Docker: the console and debugger now join when utilizing a Docker interpreter on Linux. [PY-55338]
  • Docker compose: port configuration now works for the docker-compose interpreter. [PY-54302]
  • The Emulate terminal in output console choice now not results in sudden indentation within the console or debugger [PY-55322]
  • Debugger: debugging a multiprocessing script doesn’t result in an IDE exception error anymore. [PY-55104]
  • Debugger: Python Console now shows textual content containing ANSI shade sequences appropriately. [PY-54599]
  • Debugger: debugging Django initiatives with the Python 3.8 interpreter now works easily. [PY-40754]
  • PyCharm now acknowledges non-default Flask app names and units up the Flask run configuration accordingly. [PY-55347]
  • Utilizing __debug__ in if and elif statements now not ends in unreachable code. [PY-29435]

We’re engaged on fixes for the next latest regressions with native and distant interpreters – keep tuned:

  • Docker: an uncovered port doesn’t work whereas debugging Docker.  [PY-55294]
  • Customized interpreter paths aren’t supported within the distant interpreters. [PY-52925]
  • Docker: PyCharm can’t begin the undertaking’s interpreter. [PY-55423]
  • Debugger: PyCharm produces an error when debugging code containing non-ASCII encoding. [PY-55369]
  • Testing: Behave run configurations can’t run only one state of affairs from the folder, they run all accessible recordsdata from the goal listing. [PY-55434]
  • Django: utilizing the Docker-compose interpreter results in an error when attempting to open the console. [PY-52610]

Should you encounter any bugs or have suggestions to share, please submit it to our challenge tracker, by way of Twitter, or within the feedback part of this weblog publish.



Please enter your comment!
Please enter your name here

Most Popular

Recent Comments