Ezio Melotti added the comment:
The emacs page (http://docs.python.org/devguide/emacs.html) could also be moved
outside the devguide.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20062
Tshepang Lekhonkhobe added the comment:
I think there should not be any section about any editor in the devguide. It's
beyond scope, and it risks going stale.
--
nosy: +tshepang
___
Python tracker rep...@bugs.python.org
R. David Murray added the comment:
We have pointers to external resources all over the docs. Yes, they go stale
sometimes, and when somebody notices, we update them. What do you use for
development is a common topic of discussion, so I don't see any reason not to
include some pointers in
Ezio Melotti added the comment:
I don't think the devguide is a good place for this unless some editors support
features that are particularly interesting for CPython development (e.g.
something to check refleaks).
If the features are generic enough that any Python programmer would find them
New submission from R. David Murray:
This is a followup to issue 9893. There should be a section on vim in the
devguide just like there is currently a section on emacs.
--
components: Devguide
messages: 206897
nosy: ezio.melotti, r.david.murray
priority: normal
severity: normal
stage:
R. David Murray added the comment:
The Misc/TextMate directory was also removed. I wonder if what we really want
is an 'editor support' chapter that lists best practice for any editor any
committers use (and are willing to write the section for).
--
