[Python-Dev] Moving stuff out of Misc and over to the devguide

Brett Cannon brett at python.org
Thu Jan 20 20:43:59 CET 2011

Short of moving README.coverity (I'm waiting to here back from the
company), I'm done with my tweaks to the directory.

On Wed, Jan 19, 2011 at 15:31, Brett Cannon <brett at python.org> wrote:
> OK, here is my plan that I will implement:
> ----------
> developers.txt
> maintainers.rst
> README.gdb
> README.coverity
> README.Emacs
> DELETE (seem way too old to still be relevant; tell me if I am wrong)
> -----------
> cheatsheet
> LEAVE everything else (with README properly edited and simplified to
> only list files with non-obvious names)
> On Mon, Jan 17, 2011 at 12:32, Brett Cannon <brett at python.org> wrote:
>> There is a bunch of stuff in Misc that probably belongs in the
>> devguide (under Resources) instead of in svn. Here are the files I
>> think can be moved (in order of how strongly I think they should be
>> moved):
>> README.coverty
>> README.klocwork
>> README.valgrind
>> Porting
>> developers.txt
>> maintainers.rst
>> SpecialBuilds.txt
>> Now before anyone yells "that is inconvenient", don't forget that all
>> core developers can check out and edit the devguide, and that almost
>> all of the files listed (SpecialBuilds.txt is the exception) are
>> typically edited and viewed on their own.
>> Anyway, if there is a file listed here you don't think should move out
>> of py3k and into the devguide, speak up.

More information about the Python-Dev mailing list