Having Django supporting IDEs represented at http://djangoproject.com/

[Dmitry Jemerov]

Hello,

At the moment, the Django site doesn't provide any guidance about the
development tools (editors or IDEs) that can be used for developing Django
applications. There are already a number of IDEs with good Django support
(disclaimer: I'm the lead developer on one of them, namely PyCharm), and I
think that it would be very helpful, at least for novice developers, to
provide links to such tools.

The Ruby on Rails site does a great job at that, in my opinion:
http://rubyonrails.org/ecosystem

I've discussed this with Russell Keith-Magee during DjangoCon.EU, and he
seemed to be in favor of this. Does the community think that it's
worthwhile? Is there anything specific we can do to get this moving?

I can submit a proposed patch to the documentation if that's an acceptable
approach.

Thanks in advance!
Dmitry

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Having Django supporting IDEs represented at http://djangoproject.com/

[Dmitry Jemerov]

Hello Alex,

On Oct 11, 3:25 pm, Alex Gaynor  wrote:
> I hate to use the "w" word, but this seems infinitely better as a wikipage.
>  For one we avoid any appearance of endorsement (and given the diversity of
> options in this space, that's not a bad thing).  Second, it allows for much
> more comprehensive information.  In addition to just "what text editor/IDE"
> there are also a myriad of questions surrounding the correct usage of
> plugins (i.e. it's not fair to compare PyCharm to VIM, it's fair to compare
> PyCharm to VIM with 700 plugins).  Trying to make this an official doc page
> will, I fear, lead to a pile of tickets asking for slight changes to feature
> one plugin, or theme, or whatever else, with no way for core developers to
> actually know which is preferred unless they happen to use that editor.

I'm completely in favor of having all the specific information on a
Wiki page, but I still think it's worth linking to that page from the
introductory documentation (a note in the tutorial, a question in the
FAQ and maybe some other places).

Dmitry

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.