This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients belopolsky, docs@python, eric.araujo, ezio.melotti, georg.brandl, lemburg, mark.dickinson, pitrou, rhettinger
Date 2011-07-13.15:01:20
SpamBayes Score 1.3698359e-06
Marked as misclassified No
Message-id <1310569281.38.0.0268808175276.issue4819@psf.upfronthosting.co.za>
In-reply-to
Content
I spent a few minutes updating the cheatsheet.  I think that the document is an outdated duplicate of random parts of the docs (syntax, man page, library reference, etc.) that’s rather hard to maintain for little benefit.  Is there any evidence that people used it?

I’d like to propose that we delete the file in 2.7 (it’s already gone from 3.2+) and that we start anew on a real cheatsheet, i.e. one or two A4 pages, in HTML and PDF and t-shirts, which are a useful summary of commonly used things.  I think one Python language cheatsheet and one standard library cheatsheet could be useful (one set for 2.7, another one for 3.2).

Regarding process, I’m not sure using a wiki or a non-reST file not included in the real docs is the way to go.  Maybe volunteers could work with the PSF team that’s producing a brochure?  (http://brochure.getpython.info/ —I discovered it recently, and don’t know at all who works on it and how)
History
Date User Action Args
2011-07-13 15:01:21eric.araujosetrecipients: + eric.araujo, lemburg, georg.brandl, rhettinger, mark.dickinson, belopolsky, pitrou, ezio.melotti, docs@python
2011-07-13 15:01:21eric.araujosetmessageid: <1310569281.38.0.0268808175276.issue4819@psf.upfronthosting.co.za>
2011-07-13 15:01:20eric.araujolinkissue4819 messages
2011-07-13 15:01:20eric.araujocreate