PyCharm 1.2.1 Release Candidate: py.test 2.0, buildout 1.5

Even though PyCharm 1.2 was released a few days ago, we’re already working on an update with a number of important enhancements, and the Release Candidate for the new update is available today. Here’s the summary of changes:

  • Buildout support updated for compatibility with Buildout 1.5;
  • py.test support is now compatible with version 2.0.x of py.test;
  • Many bugfixes and usability improvements for the new Find/Replace UI;
  • Other bugfixes and improvements

You can download PyCharm 1.2.1 Release Candidate or see the release notes on the EAP page.

And last but not least: we have some important information for you if you’re using PyCharm with Django 1.3. One of the latest commits to Django before the 1.3 release broke the possibility to run Django applications from any IDE (the problem is not specific to PyCharm) when the autoreload mode is used. The problem does not occur on Windows. Until the problem is fixed in an official Django release, you can fix it yourself by applying the patch to your local Django installation. PyCharm 1.2.1 RC will automatically detect the broken Django version and enable the –no-reload option if necessary.

This entry was posted in Early Access Preview and tagged , . Bookmark the permalink.

4 Responses to PyCharm 1.2.1 Release Candidate: py.test 2.0, buildout 1.5

  1. Helmut says:

    Thanks for the fast answer referring to Changeset 15911. Helped me a lot

  2. More like two weeks ago, I would say, but in essence you are right: time flies like an arrow, fruit flies like banana.

  3. NA says:

    Performance is DISMAL on Windows 7 with 3GB RAM and dual core 2 DUO 2.0 GHZ. This is on a code base of 200 lines. It’s slow from the start. Too many things are trying to happen at once by default.

  4. Maraka says:

    I still get the same error with a patch and with PyCharm 1.5.2.

Leave a Reply

Your email address will not be published. Required fields are marked *