"Run manage.py task" with imported Django project

Hey .*,

I just imported an existing Django project (using "Open Directory"). After configuring the project paths (adding the in-repo Django installation and the app's directory as source paths), running the server using the default Run Configuration works fine. However, the "Tools->Run manage.py task" menu item is 'greyed out' ie not clickable, so is the one saying "Run Django Console".

The local Django installation seems to have been recognized well, as said, the default Run Config works, Ctrl-clicking on Django defined stuff works too.

I'm working with PyCharm build 96.1063 (Beta 2), CPython 2.6.6 and Django 1.2.1 on Windows 7.

Any hints on what I may be missing? Or might this even be a bug?

TIA,

Jan

8 comments

I have the exact same problem. Manage.py isnt found.

0

Hello Jan,

probably you should specify the root of your Django project and location of settings.py file in File | Settings | Django Support menu.

0

Hello Dmitry,

thank you for your answer. And sorry for not making it clear in my original question but those settings have already been set correctly on importing the project. Django Support is enabled, the 'Django root folder' and 'Settings' fields are filed with the absolute Paths of the Django project and the settings.py file respectively. It's a simple standard setup, so settings.py lives in the same directory configured as 'Django root folder', which of course is also the folder containing manage.py. Even the templates folder was detected correctly without me having to configure it. The mentioned Run Configuration for starting the project using manage.py runserver was created automatically on import as well. Still, even after upgrading to the RC, the entries under  Tools | {Run Django Console..., Run manage.py task...}  are still disabled.

regards,

Jan

0

Hello again,

I'd like to add that this isn't a problem I only have with one specific Django project. So far, I've never seen those two menu entries clickable.

Another thing I might not have made clear enough is that I don't have a Django installation in my usual sys.path. I have a copy of Django inside each project directory, adding it as 'Source' directory in 'Settings -> Project Structure' so PyCharm knows about it. (Which works at least in so far as me being able to Ctrl+click on Django-defined stuff and be thrown to those Django sources and PyCharm completing stuff from there)


Just some additional thoughts about things I think might be related to my problem...

Hope anyone can help,

~Jan

0

Hello Jan,

Have you upgraded to PyCharm 1.0 RC? It has some fixes specifically related

to Django installations outside of site-packages.

I'd like to add that this isn't a problem I only have with one

specific Django project. So far, I've never seen those two menu

entries clickable.

Another thing I might not have made clear enough is that I don't have

a Django installation in my usual sys.path. I have a copy of Django

inside each project directory, adding it as 'Source' directory in

'Settings -> Project Structure' so PyCharm knows about it. (Which

works at least in so far as me being able to Ctrl+click on

Django-defined stuff and be thrown to those Django sources and PyCharm

completing stuff from there)

Just some additional thoughts about things I think might be related to

my problem...

Hope anyone can help,

--

Dmitry Jemerov

Development Lead

JetBrains, Inc.

http://www.jetbrains.com/

"Develop with Pleasure!"

0

Hey, sorry for the delay.

I've upgraded to RC2 by now, didn't change anything.

I've also tried moving aside the PyCharm dotdir to start with fresh settings/cache/everything, but that didn't help either.

0

Hello Jan,

Hey, sorry for the delay.

I've upgraded to RC2 by now, didn't change anything.

I've also tried moving aside the PyCharm dotdir to start with fresh

settings/cache/everything, but that didn't help either.

Indeed, I've checked and found that the specific configuration of having

Django in a separate content root wasn't supported. This will be fixed in

the final 1.0 release. Sorry for the trouble.

--

Dmitry Jemerov

Development Lead

JetBrains, Inc.

http://www.jetbrains.com/

"Develop with Pleasure!"

0

Hey Dmitry,

Indeed, I've checked and found that the specific configuration of having

Django in a separate content root wasn't supported. This will be fixed in

the final 1.0 release. Sorry for the trouble.

that's very nice to hear, thank you very much! Looking forward to the final release even more now. :-)

0

Please sign in to leave a comment.