If you encounter any bugs or have feedback to share, please submit it to our issue tracker, via Twitter, or in the comments section of this blog post.Two weeks have passed since the release of P圜harm 2021.2, and we’ve spent this time working on enhancing the performance of the product. Django: The “Run browser” feature that enables running the application in the default browser doesn’t work.SSH: Setting up an SSH interpreter leads to infinite reload of the popup window for Jupyter server settings.Docker Compose: P圜harm continues the interpreter setup process even if Docker introspection fails during the process.Docker: An exposed port doesn’t work while debugging Docker.Django: Using the Docker-compose interpreter leads to an error when trying to open the manage.py console.Custom interpreter paths aren’t supported in the remote interpreters.We’re working on fixes for the following recent regressions with local and remote interpreters – stay tuned: The new UI is enabled for setting up an interpreter via the Show all popup menu in the Python Interpreter popup window.Docker Compose: running Django with a Docker compose interpreter doesn’t lead to an HTTP error.Docker: Docker container settings for Docker-based interpreter are now applied to the run.,.This week we’re delivering a second release candidate for P圜harm 2022.2.1 with the following bug fixes: You can get the new build from our page, via the free Toolbox App, or by using snaps for Ubuntu. This will help us quickly investigate the major issues that are affecting your daily work and solve them. If you encounter an issue in P圜harm 2022.2, please reach out to our support team. Last week, in the first release candidate for 2022.2.1, we delivered some critical fixes to use the new functionality of P圜harm 2022.2 without having issues with remote interpreters. This is a new update for the upcoming minor bug-fix release for 2022.2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |