Hello All,
I have started building a Python Cheat Sheet. It aims to have Python's
most common language features and functions condensed in two pages. It
still needs a lot of improvement and better content.
If someone wants to use it as a reference, the first version can be found
on [1] an
Hi,
I updated the cheat sheet on the aesthetic side. Parts bloc and their
title are now more easily identified with colors (but its nice with B&W
printing too).
French and german versions have also been updated.
See https://perso.limsi.fr/pointal/python:memento
A+
L.Pointal.
--
h
Hello,
The Python 3 Sheet Cheat (Mémento Bases Python 3) has been
translated into german by StR Martin Putzlocher. Thanks to him.
It can be downloaded on the same page as english and french
versions: https://perso.limsi.fr/pointal/python:memento
A+
L.Pointal.
--
https://mail.python.org/mailman
Le Sat, 31 Oct 2015 12:16:08 +1100, Steven D'Aprano a écrit :
> On Sat, 31 Oct 2015 06:56 am, Laurent Pointal wrote:
>> https://perso.limsi.fr/pointal/python:memento
>
>
> Very nice! Thank you!
>
>
> Some small typos in the English version:
Thanks for your comments.
Q? Did you read
On Sat, 31 Oct 2015 06:56 am, Laurent Pointal wrote:
> Hello,
>
> I just updated my one recto-verso sheet Python 3 Cheat Sheet
>
> https://perso.limsi.fr/pointal/python:memento
Very nice! Thank you!
Some small typos in the English version:
Page 2, Conditional loop st
On 09/06/2015 13:15, Skip Montanaro wrote:
One thing which seems obvious now is that since format() delegates to
the individual types for formatting, much of the documentation of this
stuff must now be delegated to the individual types. However, I can't
find anything about the formatting syntax
On Tue, Jun 9, 2015 at 7:29 AM, wrote:
> Where have you looked? Have you read
> https://docs.python.org/3/library/string.html#formatspec ?
Yes, but I missed the None section. I looked closely at 'g', but
didn't see anything like "this is the default". I will admit I was a
bit frustrated to see t
On Tue, Jun 9, 2015, at 08:15, Skip Montanaro wrote:
> Skip> Why don't floats support "{:.Ns}"? (I know I can use "{!s}".)
>
> random832> Why would they? The old style didn't support %.Ns either.
>
> Well, the old style does, though it appears the N is ignored:
>
> >>> "%5s" % -0.00666762259822
Skip> Why don't floats support "{:.Ns}"? (I know I can use "{!s}".)
random832> Why would they? The old style didn't support %.Ns either.
Well, the old style does, though it appears the N is ignored:
>>> "%5s" % -0.00666762259822
'-0.00666762259822'
It doesn't raise an exception though.
(This i
e Perl code ). I am still only using Python 2.7, but have
recently started forcing myself to use the print() function. I
figure maybe I should also start to come to grips with the fancy new
string formatting.
Is there a cheat sheet around which shows some side-by-side examples
On Mon, Jun 8, 2015, at 16:32, Skip Montanaro wrote:
> This is counterintuitive:
>
> >>> "{:.3}".format(-0.00666762259822)
> '-0.00667'
> >>> "{:.3f}".format(-0.00666762259822)
> '-0.007'
> >>> "%.3f" % -0.00666762259822
> '-0.007'
> >>> "{:.3s}".format(-0.00666762259822)
> ValueError Unknown form
On 08.06.15 23:32, Skip Montanaro wrote:
This is counterintuitive:
>>> "{:.3}".format(-0.00666762259822)
'-0.00667'
>>> "{:.3f}".format(-0.00666762259822)
'-0.007'
>>> "%.3f" % -0.00666762259822
'-0.007'
>>> "{:.3s}".format(-0.00666762259822)
ValueError Unknown format code 's' for object of
It just means significant digits in the general format, which alternates
between 10-exponent notation and plain decimal notation.
https://docs.python.org/3.4/library/string.html#format-specification-mini-language
>>> '{:.3}'.format(0.356785)
'3.57e-05'
>>> '{:.3}'.format(0.0035678
This is counterintuitive:
>>> "{:.3}".format(-0.00666762259822)
'-0.00667'
>>> "{:.3f}".format(-0.00666762259822)
'-0.007'
>>> "%.3f" % -0.00666762259822
'-0.007'
>>> "{:.3s}".format(-0.00666762259822)
ValueError Unknown format code 's' for object of type 'float'
Why does the first form display f
elf to use the print() function. I figure maybe I should also start to come
to grips with the fancy new string formatting.
Is there a cheat sheet around which shows some side-by-side examples of the
{}-style and printf-style? I didn't see anything with a few Google searches.
Thx,
Skip
Hi
On Mon, Jun 8, 2015 at 3:05 PM, Steven K Knight wrote:
> I think http://pyformat.info/ is what you're looking for.
Perfect, thanks!
S
--
https://mail.python.org/mailman/listinfo/python-list
come to grips with the fancy new string formatting.
Is there a cheat sheet around which shows some side-by-side examples of the
{}-style and printf-style? I didn't see anything with a few Google searches.
Thx,
Skip
--
https://mail.python.org/mailman/listinfo/python-list
On Dec 3, 12:12 am, Terry Reedy wrote:
> At the moment (3.1) there are, unfortunately, library packages that
> require % for formatting (logging, I believe, for one). There has been
> discussion on adding a new option for 3.2, but I do not know what will
> happen. Depends on whether you want to be
On 3 Dec, 01:17, Antoine Pitrou wrote:
> Le Tue, 01 Dec 2009 06:03:36 -0800, Mark Summerfield a écrit :
>
> > I've produced a 4 page document that provides a very concise summary of
> > Python 2<->3 differences plus the most commonly used new Python 3
> > features. It is aimed at existing Python 2
On 2 Dec, 21:28, David H Wild wrote:
> In article
> <9d290ad6-e0b8-4bfa-92c8-8209c7e93...@a21g2000yqc.googlegroups.com>,
> Mark Summerfield wrote:
>
> > > There is a typographical fault on page 4 of this pdf file. The letter
> > > "P" is missing from the word "Python" at the head of the compar
In article
<9d290ad6-e0b8-4bfa-92c8-8209c7e93...@a21g2000yqc.googlegroups.com>,
Mark Summerfield wrote:
> > There is a typographical fault on page 4 of this pdf file. The letter
> > "P" is missing from the word "Python" at the head of the comparison
> > columns.
> I can't see that problem---I'
On Wed, Dec 02, 2009 at 08:03 -0800, Mark Summerfield wrote:
> On Dec 2, 11:20 am, Wolodja Wentland
> > It would be quite nice if you could mark all the Python 3 idioms that
> > work in Python 2.X as well. This would allow readers that are still using
> > Python 2.X and are used to the 'old way'
On 3 Dec, 01:17, Antoine Pitrou wrote:
> Le Tue, 01 Dec 2009 06:03:36 -0800, Mark Summerfield a écrit :
>
> > I've produced a 4 page document that provides a very concise summary of
> > Python 2<->3 differences plus the most commonly used new Python 3
> > features. It is aimed at existing Python 2
On 2 Dec, 20:59, MRAB wrote:
> Mark Summerfield wrote:
> > On 2 Dec, 19:28, David H Wild wrote:
> >> In article
> >> <351fcb4c-4e88-41b0-a0aa-b3d63832d...@e23g2000yqd.googlegroups.com>,
> >> Mark Summerfield wrote:
>
> >>> I only just found out that I was supposed to give a different URL:
> >
On 2 Dec, 22:49, "John Posner" wrote:
> On Wed, 02 Dec 2009 13:34:11 -0500, Carsten Haese
>
> wrote:
>
> > With string interpolation, you don't need to do that, either.
> '%*d' % (8,456)
> > ' 456'
>
> Thanks, Carsten and Mark D. -- I'd forgotten about the use of "*" in
> minimum-fie
Le Tue, 01 Dec 2009 06:03:36 -0800, Mark Summerfield a écrit :
> I've produced a 4 page document that provides a very concise summary of
> Python 2<->3 differences plus the most commonly used new Python 3
> features. It is aimed at existing Python 2 programmers who want to start
> writing Python 3
Mark Summerfield wrote:
Well it seems clear to me that the BDFL wants to kill of % formatting,
but wasn't able to for Python 3...
Definitely. I thought of adding autonumbering of fields (in 3.1) in
response to his inquiry about the barriers to moving to .format. That
solved 'simplicity of de
On Wed, 02 Dec 2009 13:34:11 -0500, Carsten Haese
wrote:
With string interpolation, you don't need to do that, either.
'%*d' % (8,456)
' 456'
Thanks, Carsten and Mark D. -- I'd forgotten about the use of "*" in
minimum-field-width specs and precision specs (doh). How about this:
Mark Summerfield wrote:
On 2 Dec, 19:28, David H Wild wrote:
In article
<351fcb4c-4e88-41b0-a0aa-b3d63832d...@e23g2000yqd.googlegroups.com>,
Mark Summerfield wrote:
I only just found out that I was supposed to give a different URL:
http://www.informit.com/promotions/promotion.aspx?promo=1
On 2 Dec, 19:28, David H Wild wrote:
> In article
> <351fcb4c-4e88-41b0-a0aa-b3d63832d...@e23g2000yqd.googlegroups.com>,
> Mark Summerfield wrote:
>
> > I only just found out that I was supposed to give a different URL:
> >http://www.informit.com/promotions/promotion.aspx?promo=137519
> > This
Mark Summerfield writes:
> On 1 Dec, 23:52, John Bokma wrote:
>> Mark Summerfield writes:
>> > It is available as a free PDF download (no registration or anything)
>> > from InformIT's website. Here's the direct link:
>> >http://ptgmedia.pearsoncmg.com/imprint_downloads/informit/promotions/...
In article
<351fcb4c-4e88-41b0-a0aa-b3d63832d...@e23g2000yqd.googlegroups.com>,
Mark Summerfield wrote:
> I only just found out that I was supposed to give a different URL:
> http://www.informit.com/promotions/promotion.aspx?promo=137519
> This leads to a web page where you can download the doc
On Dec 2, 4:41 pm, "John Posner" wrote:
> Goal: place integer 456 flush-right in a field of width 8
>
> Py2: "%%%dd" % 8 % 456
> Py3: "{0:{1}d}".format(456, 8)
>
> With str.format(), you don't need to nest one formatting operation within
> another. A little less mind-bending, and every l
John Posner wrote:
> Goal: place integer 456 flush-right in a field of width 8
>
> Py2: "%%%dd" % 8 % 456
> Py3: "{0:{1}d}".format(456, 8)
>
> With str.format(), you don't need to nest one formatting operation
> within another.
With string interpolation, you don't need to do that, either.
>
On Wed, 02 Dec 2009 10:55:23 -0500, Mark Summerfield
wrote:
On Dec 1, 2:03 pm, Mark Summerfield wrote:
I've produced a 4 page document that provides a very concise summary
of Python 2<->3 differences plus the most commonly used new Python 3
features. It is aimed at existing Python 2 program
On Dec 2, 4:22 pm, Mark Summerfield wrote:
> On Dec 2, 11:31 am, "Martin P. Hellwig"
> wrote:
>
> > MarkSummerfieldwrote:
>
> > > It is available as a free PDF download (no registration or anything)
> > > from InformIT's website. Here's the direct link:
> > >http://ptgmedia.pearsoncmg.com/imprint
On Dec 2, 11:31 am, "Martin P. Hellwig"
wrote:
> MarkSummerfieldwrote:
>
> > It is available as a free PDF download (no registration or anything)
> > from InformIT's website. Here's the direct link:
> >http://ptgmedia.pearsoncmg.com/imprint_downloads/informit/promotions/...
>
>
> Very handy! Am I
n for not wanting to do this is that the document is aimed at
people who want to write Python 3, not to encourage people to stick
with 2:-)
>
> And thanks for the nice cheat sheet! :-D
Thanks!
> --
> .''`. Wolodja Wentland
> : :' :
> `. `'` 4096R/CAF14EFC
> `- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC
>
> signature.asc
> < 1KViewDownload
--
http://mail.python.org/mailman/listinfo/python-list
On Dec 2, 8:53 am, Mark Dickinson wrote:
> On Dec 2, 8:01 am, MarkSummerfield wrote:
>
> > On 1 Dec, 17:50, Mark Dickinson wrote:
> > > My only quibble is with the statement on the first page that
> > > the 'String % operator is deprecated'. I'm not sure that's
> > > true, for all values of 'dep
On Dec 1, 2:03 pm, Mark Summerfield wrote:
> I've produced a 4 page document that provides a very concise summary
> of Python 2<->3 differences plus the most commonly used new Python 3
> features. It is aimed at existing Python 2 programmers who want to
> start writing Python 3 programs and want t
Mark Summerfield wrote:
It is available as a free PDF download (no registration or anything)
from InformIT's website. Here's the direct link:
http://ptgmedia.pearsoncmg.com/imprint_downloads/informit/promotions/python/python2python3.pdf
Very handy! Am I wrong in assuming that you forgot to inc
ders that are still using
Python 2.X and are used to the 'old way' to adapt their coding style
accordingly. You could just add a little (2.X) after the idiom for
example.
And thanks for the nice cheat sheet! :-D
--
.''`. Wolodja Wentland
: :' :
On Dec 2, 8:01 am, Mark Summerfield wrote:
> On 1 Dec, 17:50, Mark Dickinson wrote:
> > My only quibble is with the statement on the first page that
> > the 'String % operator is deprecated'. I'm not sure that's
> > true, for all values of 'deprecated'. There don't appear
> > to be any definite
On 1 Dec, 23:52, John Bokma wrote:
> Mark Summerfield writes:
> > It is available as a free PDF download (no registration or anything)
> > from InformIT's website. Here's the direct link:
> >http://ptgmedia.pearsoncmg.com/imprint_downloads/informit/promotions/...
>
> Thanks!
>
> > And of course,
On 1 Dec, 21:55, Terry Reedy wrote:
> Mark Summerfield wrote:
> > I've produced a 4 page document that provides a very concise summary
> > of Python 2<->3 differences plus the most commonly used new Python 3
> > features. It is aimed at existing Python 2 programmers who want to
> > start writing P
On 1 Dec, 18:30, Lie Ryan wrote:
> On 12/2/2009 1:03 AM, Mark Summerfield wrote:
>
>
>
> > I've produced a 4 page document that provides a very concise summary
> > of Python 2<->3 differences plus the most commonly used new Python 3
> > features. It is aimed at existing Python 2 programmers who wa
On 1 Dec, 17:50, Mark Dickinson wrote:
> On Dec 1, 2:03 pm, Mark Summerfield wrote:
>
> > I've produced a 4 page document that provides a very concise summary
> > of Python 2<->3 differences plus the most commonly used new Python 3
> > features.
>
> Very nice indeed!
>
> My only quibble is with t
Mark Summerfield writes:
> It is available as a free PDF download (no registration or anything)
> from InformIT's website. Here's the direct link:
> http://ptgmedia.pearsoncmg.com/imprint_downloads/informit/promotions/python/python2python3.pdf
Thanks!
> And of course, if you want more on Python
Mark Summerfield wrote:
I've produced a 4 page document that provides a very concise summary
of Python 2<->3 differences plus the most commonly used new Python 3
features. It is aimed at existing Python 2 programmers who want to
start writing Python 3 programs and want to use Python 3 idioms rath
On 12/2/2009 1:03 AM, Mark Summerfield wrote:
I've produced a 4 page document that provides a very concise summary
of Python 2<->3 differences plus the most commonly used new Python 3
features. It is aimed at existing Python 2 programmers who want to
start writing Python 3 programs and want to us
On Dec 1, 2:03 pm, Mark Summerfield wrote:
> I've produced a 4 page document that provides a very concise summary
> of Python 2<->3 differences plus the most commonly used new Python 3
> features.
Very nice indeed!
My only quibble is with the statement on the first page that
the 'String % operat
On Dec 1, 7:03 am, Mark Summerfield wrote:
> "Programming in Python 3 (Second Edition)" ISBN-10: 0321680561.
I ordered it...
-- Gnarlie
http://Gnarlodious.com
--
http://mail.python.org/mailman/listinfo/python-list
> I've produced a 4 page document that provides a very concise summary
> of Python 2<->3 differences plus the most commonly used new Python 3
> features. It is aimed at existing Python 2 programmers who want to
> start writing Python 3 programs and want to use Python 3 idioms rather
> than those fr
I've produced a 4 page document that provides a very concise summary
of Python 2<->3 differences plus the most commonly used new Python 3
features. It is aimed at existing Python 2 programmers who want to
start writing Python 3 programs and want to use Python 3 idioms rather
than those from Python
Riccardo T. ha scritto:
> I wrote a little cheat sheet for this wonderful language, but because of
> my still little experience with it, I would like to have a feedback
> Could you have a look at it and tell me what do you think about, please?
>
> http://greyfox.imente.org/
En Sat, 29 Dec 2007 06:58:27 -0200, ZeD <[EMAIL PROTECTED]> escribi�:
> Michele Simionato wrote:
>
>> Nowadays file is no more an alias for open.
>
> curious... maybe it's me, but I can't find a "What's New in Python" where
> this is said...
See Misc/NEWS:
- Patch #1479181: split open() and file(
ZeD ha scritto:
> Michele Simionato wrote:
>
>> Python 2.4.4 (#2, Oct 4 2007, 22:02:31)
> file is open
>> True
>>
>> Python 2.5.1 (r251:54863, Oct 5 2007, 13:36:32)
> file is open
>> False
>>
>> Nowadays file is no more an alias for open.
>
> curious... maybe it's me, but I can't find a
Scott David Daniels ha scritto:
> Riccardo T. wrote:
>> Maybe I'll add __builtin__ and os in place of the type hierarchy, but
>> I'm not sure about that. However, not in the next release. What do you
>> think about?
>
> How about:
> top line w/ __builtin__, os, os.path (and no contents -- inspire
Michele Simionato wrote:
> Python 2.4.4 (#2, Oct 4 2007, 22:02:31)
file is open
> True
>
> Python 2.5.1 (r251:54863, Oct 5 2007, 13:36:32)
file is open
> False
>
> Nowadays file is no more an alias for open.
curious... maybe it's me, but I can't find a "What's New in Python" where
t
Alaric ha scritto:
> Nicely done! I would suggest you put your website address on it and a revision
> number so that as it gains use on te web, people can find the "latest"
> version.
That's a good idea, thank you :)
--
GreyFox
--
http://mail.python.org/mailman/listinfo/python-list
Riccardo T. wrote:
>
>
> I wrote a little cheat sheet for this wonderful language, but because of
> my still little experience with it, I would like to have a feedback
> Could you have a look at it and tell me what do you think about, please?
>
> http://greyfox.iment
Riccardo T. wrote:
> Scott David Daniels ha scritto:
>> Riccardo T. wrote:
>>> Scott David Daniels ha scritto:
[in the .png]
> ...
> Callable types
>...
>User-definet methods
I personally prefer "User-defined methods"
>>> That's a typo, thank you.
>> Hope I didn't
Scott David Daniels ha scritto:
> Riccardo T. wrote:
>> Scott David Daniels ha scritto:
>>> [in the .png]
...
Callable types
...
User-definet methods
>>> I personally prefer "User-defined methods"
>>
>> That's a typo, thank you.
>
> Hope I didn't offend (I was simply tryi
Riccardo T. wrote:
> Scott David Daniels ha scritto:
>> [in the .png]
>>> ...
>>> Callable types
>>>...
>>>User-definet methods
>> I personally prefer "User-defined methods"
>
> That's a typo, thank you.
Hope I didn't offend (I was simply trying to be cute).
Some from a bit further along.
c james ha scritto:
> On the svg version, as viewed on firefox, the sections "Simple
> statements", "Definations" and "Comments"; there appears to be a problem
> with text wrapping.
I see, it has already been signaled by mail. I'm not sure about how to
fix that, I'll have to ask someone who knows
Riccardo T. wrote:
> I wrote a little cheat sheet for this wonderful language, but because of
> my still little experience with it, I would like to have a feedback
> Could you have a look at it and tell me what do you think about, please?
>
> http://greyfox.imente.org/
On Dec 28, 12:40 pm, "Riccardo T." <[EMAIL PROTECTED]> wrote:
> > "file" objects are generally supposed to be built with the
> > open function, not instantiated as shown.
>
> Since open() is just an alias for file(), changing the name should be
> enough, right?
It depends on the Python version:
P
Scott David Daniels ha scritto:
> [in the .png]
>> ...
>> Callable types
>>...
>>User-definet methods
>
> I personally prefer "User-defined methods"
That's a typo, thank you.
>>...
>>Class instances
> I'd try:
> Class instances with a __call__ method.
Yes, it's more clear
Looks good thanks!
On Dec 27, 2007 11:06 PM, Scott David Daniels <[EMAIL PROTECTED]> wrote:
> Riccardo T. wrote:
> > I wrote a little cheat sheet for this wonderful language, but because of
> > my still little experience with it, I would like to have a feedback
> >
Riccardo T. wrote:
> I wrote a little cheat sheet for this wonderful language, but because of
> my still little experience with it, I would like to have a feedback
> Could you have a look at it and tell me what do you think about, please?
>
> http://greyfox.imente.org/
Carl Banks ha scritto:
> On Dec 27, 12:38 pm, "Riccardo T." <[EMAIL PROTECTED]> wrote:
>> I wrote a little cheat sheet for this wonderful language, but because of
>> my still little experience with it, I would like to have a feedback
>> Could you have a loo
On Dec 27, 12:38 pm, "Riccardo T." <[EMAIL PROTECTED]> wrote:
> I wrote a little cheat sheet for this wonderful language, but because of
> my still little experience with it, I would like to have a feedback
> Could you have a look at it and tell me what do you thin
Markus Gritsch ha scritto:
> On Dec 27, 11:38 am, "Riccardo T." <[EMAIL PROTECTED]> wrote:
>> I wrote a little cheat sheet for this wonderful language, but because of
>> my still little experience with it, I would like to have a feedback
>> Could you have a loo
On Dec 27, 11:38 am, "Riccardo T." <[EMAIL PROTECTED]> wrote:
> I wrote a little cheat sheet for this wonderful language, but because of
> my still little experience with it, I would like to have a feedback
> Could you have a look at it and tell me what do you thin
ython-list/2006-June/386662.html
>
> > Mike
>
> Thanks :)
> I'll read them to improve my python knowledge, but I prefere to have a
> very small cheat sheet to keep near me.
>
> --
> GreyFox
Yeah...they can be handy. I like that Quick Reference card, but it is
a little unwieldy.
Mike
--
http://mail.python.org/mailman/listinfo/python-list
ledge, but I prefere to have a
very small cheat sheet to keep near me.
--
GreyFox
--
http://mail.python.org/mailman/listinfo/python-list
On Dec 27, 11:38 am, "Riccardo T." <[EMAIL PROTECTED]> wrote:
> I wrote a little cheat sheet for this wonderful language, but because of
> my still little experience with it, I would like to have a feedback
> Could you have a look at it and tell me what do you thin
I wrote a little cheat sheet for this wonderful language, but because of
my still little experience with it, I would like to have a feedback
Could you have a look at it and tell me what do you think about, please?
http://greyfox.imente.org/index.php?id=73
--
GreyFox
--
http://mail.python.org
78 matches
Mail list logo
