-
-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Misc/cheatsheet needs updating #49069
Comments
Misc/cheatsheet could do with an upgrade, both for the 2.x and 3.x branches. For 3.x, I guess the changes needed are quite extensive. I'm not sure |
Some more for both 2. and 3.0:
I am sure I missed a lot, but the core language sections should be It would be nice to reformat it in ReST as well. |
Merging nosy from duplicate report. |
Misc/cheatsheet has been removed in r88127. Should this be closed? |
Well, perhaps Marc-André wants to revive it. Otherwise, suggest closing indeed. |
Updating the cheat sheet would be a great summer of code like project. We are considering using the cheat sheet as basis for a flyer in the PSF marketing material project. Please add it back and add a note to it, that it currently is missing a few language features (e.g. add Alexanders list to it). Thanks. |
IMO it's not only about updating. It's about converting it to some By the way the Python 3 transition means that it not only misses some |
Perhaps the cheatsheet can be transferred to a wiki page and we can put out a comp.lang.python call for updates. Also, +1 on the summer of code idea. |
I agree that it would be nice to have a cheatsheet somewhere, possibly in the official doc and not as a plain txt file in Misc/. |
FWIW, I updated the first couple of pages. If anyone finds my changes useful, here they are in bpo-4819.diff. |
Past experience has shown that a cheatsheet in the main repository gets neglected. How about we open it up via a wiki or somesuch so that the community if free to update it? |
Leaving it in the wiki for a while so that the community can update and improve it might be a good idea, but ultimately I think it should go in the doc. |
Raymond Hettinger wrote:
Good idea. I just want to prevent the text from being lost in SVN
|
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) |
Another idea might be to have a "cheatsheet" in the official docs with links to the right section and possibly a minimal description. It would be useful to get a quick overview of the features of the language and use the links to jump to the extended doc without having duplication. |
Given that Misc/cheatsheet doesn't exist any more in the Python 3 repo, and Python 2 is nearing end-of-life, I suspect this should just be closed. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: