[issue19608] devguide needs pictures
Changes by Ezio Melotti ezio.melo...@gmail.com: -- resolution: - works for me stage: - resolved status: open - closed type: - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19608 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19608] devguide needs pictures
Mark Lawrence added the comment: Please close this. -- nosy: +BreamoreBoy status: pending - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19608 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19608] devguide needs pictures
Nick Coghlan added the comment: We're not designers either. However, something that *could* help is to investigate whether or not the blockdiag and seqdiag Sphinx extensions can be integrated into the build toolchain for the devguide and the main Python docs. That would drastically lower the barrier for including basic diagrams where appropriate (since it would just be ASCII art inside an appropriate Sphinx directive) and thus greatly increase the chance of it happening. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19608 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19608] devguide needs pictures
Ezio Melotti added the comment: Plain ASCII-art might also be enough, but without specific indication of what kind of pictures you want and where you want them I'm going to close this. -- status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19608 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19608] devguide needs pictures
New submission from anatoly techtonik: http://docs.python.org/devguide/ it covers pretty much complicated stuff, which takes a lot of time to grasp. Pictures help to save hours if not weeks. There needs to be some immediate intro picture at the top of front page illustrating transformation of Python code through the toolchain to machine execution instructions. -- components: Devguide messages: 202933 nosy: ezio.melotti, techtonik priority: normal severity: normal status: open title: devguide needs pictures ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19608 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19608] devguide needs pictures
Nick Coghlan added the comment: Feel free to draw some and send a patch. -- nosy: +ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19608 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19608] devguide needs pictures
anatoly techtonik added the comment: Thanks for the proposal, but you know perfectly that I am not a designer. I don't believe that there are no talented people who find this ticket interesting. You just need to add tag:easy to is (or allow others to do), so it became visible to these people via OpenHatch or through PSF outreach initiatives. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19608 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
