python - PyCharm & VirtualEnvs - How To Remove Legacy -

how remove traces of legacy projects pycharm?

background: upgraded pycharm community edition pycharm pro edition today. reason work on django projects, , in particular, fledgling legacy project called 'deals'.

i deleted legacy project folders.

i opened pro edition , went through steps of creating django project called 'deals' python3.4 interpreter in virtualenv.

it didn't work, got error message saying missing file, , in pycharm project explorer, see was

• deals

  .ideas

so deleted (ie. deleted folders in both ~/.virtualenvs/deals , ~/projects/deals).

i tried again, although time got interpreter number suffix, ie. python3.4 (1). continued, , got same empty file structure.

i deleted both folders again, went , cleaned out intepreters in settings > project interpreters .

i tried again, getting 'new' interpreters,until had python3.4 (5) plus, along way invalidated caches , restarted. (ie. file > invalidate caches/restart)

then prove if works @ all, tried brand new name 'junk'. time worked fine, , see django folders in pycharm explorer. great.

but want work on project called 'deals'. deleted 'deal's folders again, , tried create deals django project again. same result.

after googling, went settings > project structure > + content root, , pointed folder @ ~/.virtual/deals.

ok, see files in virtual env, there's no django files, , plus, project folder separate virtualenv folder, eg

• deals

  • deals (~/project/deals) <- separate

  • deals (~/.virtualenvs/deals) <- separate

    • deals

      init.py settings.py urls.py wsgi.py

    manage.py

really stuck now.

any advice on how working please? eg. how i

(i) 'cleanskin' can start django project , proper folders in project space.

(ii) working virtualenv, , ensure interpreter doesn't have number suffix, such python3.4(6)

many in advance,

chris

you can clean out old pycharm interpreters no longer associated project via settings -> project interpreter, click on gear in top right, click "more". gives listing can rid of old virtualenvs pycharm thinks still around. prevent "(1)", "(2)" part.

you don't want make virtualenv content root. project's code content root.

as suggestion:

• clear out registered virtual envs

• make virtualenv, outside of pycharm

• create new project using pycharm's django template

you should have working example.