PyCharm build 100.34 is available

Now that the stress of the IntelliJ IDEA 10 release is behind us, we can return to the regular schedule of PyCharm 1.1 Early Access Preview builds. During the three weeks that have passed since the previous EAP, the PyCharm team has created quite a few new features:

  • Initial support for remote debugging, the most highly voted feature in our issue tracker;
  • New test runner for nose tests, with support for nose plugins;
  • Several new quickfixes, for example, one to add forgotten ‘self.’ qualifier for instance attribute access;
  • New intentions, such as ‘join ifs’;
  • Support for Python 3 parameter and function annotations for specifying types used by code analysis and code completion;
  • A number of other fixes and productivity improvements.

You can download the new build from the EAP page. In the coming days, we plan to publish a number of blog posts (and maybe even screencasts) describing how to use the new features of PyCharm 1.1 in more detail.

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

11 Responses to PyCharm build 100.34 is available

  1. Rob W says:

    Bad news, as 100.34 appears to be DOA for me.

    I just downloaded and installed 100.34. Upon launch, I get an error message about an IDE fatal error followed by an error about indexes. Then some things blink, I get a red icon in the bottom. I’ve done the report thing a few iterations, but after reporting and clearing — the list of errors just repopulates. Again and again, even if I restart.

    I did not see this issue running the prior 1.1 EAP — 98.404. Nor with release 1.0.1 (97.87).

    Running PyCharm on Windows7 64-bit Pro.

    Cheers,
    Rob

  2. Eka says:

    Linux version doesnt work check packing

  3. Rob W says:

    Bad news, as 100.34 appears to be DOA for me.

    I just downloaded and installed 100.34. Upon launch, I get an error message about an IDE fatal error followed by an error about indexes. Then some things blink, I get a red icon in the bottom. I’ve done the report thing a few iterations, but after reporting and clearing — the list of errors just repopulates. Again and again, even if I restart.

    I did not see this issue running the prior 1.1 EAP — 98.404. Nor with release 1.0.1 (97.87).

    Running PyCharm on Windows7 64-bit Pro.

    Cheers,
    Rob

  4. Pingback: Tweets that mention JetBrains PyCharm Blog » Blog Archive » PyCharm build 100.34 is available -- Topsy.com

  5. At the first glance, the archive has wrongly packaged pych folder. Must be a bug in your release packaging scripts.

  6. Peter Smit says:

    Yes, the linux package has also this folder. When I copied the pycharm.sh to the real bin folder it worked.

  7. I filed few bugs concerning the packaging.

    Unfortunately the fix for NumPy / SciPy didn’t make it into this release. I have to admit that a huge progress has been made since the last EAP though. I already noted on several occasions that the IDE is getting smarter than me.

    Just a bit more effort to fix the support for numeric modules and I can finally switch to PyCharm :-)

  8. Sayane says:

    It’s f…ing awesome ! Great work.

  9. yole says:

    Rob,
    Could you please file an issue at http://youtrack.jetbrains.net/ and attach %USERHOME%.PyCharm10systemlogsidea.log ?

  10. Rob W says:

    @Yole

    I opened YouTrack PY-2444 for the 100.34 stability issue I’m having and attached the idea.log file. If you need anything else, please let me know.

    Cheers,
    Rob

  11. Sayane says:

    It seems that something is broken with javascript. I have ExtJs library in my project, but PyCharm doesn’t know about it. It worked in PyCharm 1.0. Is it a bug or am I missing somthing?

Leave a Reply

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

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">