turn off "Show Import Popups"?

PyCharmers:

(version pycharm-94.454)

I am attempting to audition PyCharm for a suite of huge Django projects, and I my general impression is it has awesome, deep, and powerful features...

...which are often obscured by trivial irritations and user-hostilities. As a general example, before I get to a specific question, I cannot determine how to trigger a test run, such as 'fab test'. I hope I can figure this out in time!

The specific question: How to permanently turn off the "Show Import Popups"? They keep turning back on after I use the menu, and they are as annoying (and innacurate) as heck! They always obscure the line near the one where I'm typing. This eagerness to help reminds one of Clippit!

Enough flaming; otherwise this is an awesome editor and I can't wait to use its refactors!

--

  Phlip

  http://c2.com/cgi/wiki?ZeekLand

3 comments

Hello Phlip,

I am attempting to audition PyCharm for a suite of huge Django

projects, and I my general impression is it has awesome, deep, and

powerful features...

..which are often obscured by trivial irritations and

user-hostilities. As a general example, before I get to a specific

question, I cannot determine how to trigger a test run, such as 'fab

test'. I hope I can figure this out in time!

Is this a Django project or a regular Python one? To run tests in a Python

project, simply right-click a test class and select the run action from the

context menu. Running tests for Django apps will be supported in the next

EAP build.

The specific question: How to permanently turn off the "Show Import

Popups"? They keep turning back on after I use the menu, and they are

as annoying (and innacurate) as heck! They always obscure the line

near the one where I'm typing. This eagerness to help reminds one of

Clippit!

At the moment there's no option to turn off the auto-import popups. The problem

with them reappearing after use has been fixed in the latest EAP build (please

upgrade). As for the inaccurateness - please report specific problems; maybe

I can help you configure your project so that they will work correctly.

Specific feature requests and bug reports are always welcome in our issue

tracker: http://youtrack.jetbrains.net/

--

Dmitry Jemerov

Development Lead

JetBrains, Inc.

http://www.jetbrains.com/

"Develop with Pleasure!"

0

In general, please support this cycle:

- each project registers a test command line

      (example: fab test, or make test, or python manage.py etc.)

- one keystroke (such as F5) saves all files and runs the tests

    (the keystroke works regardless what file you are in)

- one keystroke (such as F4) navigates directly to a failing assertion

I worked several years with TextMate, which its adherents consider God's Gift to TDD, and the cycle was agonizing. For example, you had to save all files, then navigate to the test you need to run, then run it, then scrape the results off a crummy popup window, and then mouse back to the source. TDD should work by running the tests over and over again while looking at the production code. Going further, editors should read all the test transcripts to build their static analysis tables:

http://www.oreillynet.com/onlamp/blog/2008/05/dynamic_languages_vs_editors.html

Just a thought!

0

I found a solution to this (9 years too late)

Settings > Editor > General > Auto Import

    Section: Java

        Show import popup for:

            [ ] classes

            [ ] static methods and fields

Uncheck both boxes

0

Please sign in to leave a comment.