I think there's some ambiguity in the current wording for 'continue Statements'.

Current wording is:

When the program execution reaches a continue statement, the program execution immediately jumps back to the start of the loop.

To me the ambiguity is that it might be interpreted as saying that the loop starts entirely again as though it had not yet been started.

Less ambiguous might be:

When the program execution reaches a continue statement, the program execution skips directly to the start of the next iteration of the loop (if there is one or more remaining), bypassing any other code remaining in the current iteration of the loop.

https://peps.python.org/pep-0318/

They are less seen in the wild but really useful to maximize code compatibility

https://docs.python.org/3/library/multiprocessing.html

https://wiki.python.org/moin/Generators

https://docs.python.org/3/library/time.html

"Requests" is a common topic in technical interviews, where you have to share your screen and retrieve data from a public API. Would be helpful for many to have it on the cheat sheet.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency @headlessui/vue to v1.7.20
• Update dependency prettier-plugin-tailwindcss to v0.5.14
• Update dependency vite to v5.2.9
• Update vue monorepo to v3.4.23 (@vue/compiler-dom, vue)
• Update dependency eslint-plugin-vue to v9.25.0
• Update dependency eslint to v9
• Update dependency happy-dom to v14
• Update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

https://docs.python.org/3/library/glob.html

https://docs.python.org/3/library/uuid.html

https://docs.python.org/3/library/argparse.html

https://docs.python.org/3/library/math.html

https://docs.python.org/3/library/threading.html

https://docs.python.org/3/library/pdb.html

https://docs.python.org/3/library/typing.html

The Regular Expressions page contains the following sentence in the "The Caret and Dollar sign characters" section:

The r'\d\$' regular expression string matches strings that end with a numeric character from 0 to 9:

I believe the backslash before the '$' is incorrect. FYI.

Python 3.6+: dataclasses
Python 2.7+: attrs

they are not part of the std (from 3.7, dataclasses are), but really really make the code much more readable

Add a new topic to the cheat sheet: Classes

Example of code in the section has errors. The real output will be different from what is said in listing.
It will be

-- division finished --
2.0
-- division finished --
12.0
Error: Invalid argument: division by zero
-- division finished --
None

instead of

21.0
-- division finished --
3.5
-- division finished --
Error: Invalid argument: division by zero
-- division finished --
None
-- division finished --

Add a new topic to the cheat sheet: pathlib module.

This is awesome :) I don't see any mention of String Formatting though. I think it'd be useful to have this right by the String Concatenation since it should preferred over chaining concatenations for more complex strings.

key = "foo"
value = "bar"

baz = "{}: {}".format(key, value)
baz = "First value: {0}, Second value: {1}".format(key, value)
baz = "key: {key}, value: {value}".format(key=key, value=value)

The .format method should be used over the % formatting syntax for compatibility with Python 3. A notable exception is logging. In the Logging section you have the following line:

logging.debug('Start of factorial(%s)' % (n))

This is a total micro-optimization but doing this causes the string formatting to occur even if the log level isn't debug. You can skip the formatting and pass the variables as extra arguments and the logging library will automatically format the message before printing:

logging.debug('Start of factorial(%s)', n)

However in that case only the % formatting syntax is supported in Python 2.

There is mistake in zip's result, last output of func should be 'Elizabeth is 44 years old', not 'Alice is 44 years old', logic does not change, but eyes mazolite.

https://docs.python.org/3/library/io.html

I've been reading through the guide and was a little confused by the dedent clarification (https://github.com/wilfredinni/python-cheatsheet#multiline-strings-with-triple-quotes). Just thought one or two more lines here may be helpful about dedent function and why the .strip() method was used on the print function.

There are missing parentheses in Path examples, in Linux and Mac. If someone just copy and paste on terminal, it doesn't work.

In the first sentence it says:

There are two main modules in Python that deals with path manipulation.

should be:

There are two main modules in Python that deal with path manipulation.

https://docs.python.org/3/library/collections.html

Would a section on OOP basics be worthy or too much content for the cheatsheet?

• Define a Class in Python
• Instantiate an Object
• Inherit From Other Classes
• Calling Methods

https://docs.python.org/3/library/copy.html

https://docs.python.org/3/library/csv.html

https://docs.python.org/3/library/asyncio.html

The Python cheatsheet currently contains the following inaccurate information in the Boolean Evaluation section:

These statements are equivalent:

>>> if a is True:
>>>    pass
>>> if a is not False:
>>>    pass
>>> if a:
>>>    pass

And these as well:

>>> if a is False:
>>>    pass
>>> if a is not True:
>>>    pass
>>> if not a:
>>>    pass

Unfortunately, the above is incorrect. Consider the following:

Python 3.10.2 (tags/v3.10.2:a58ebcc, Jan 17 2022, 14:12:15) [MSC v.1929 64 bit (AMD64)] on win32
>>> a = 4
>>> a is True
False
>>> a is not False
True
>>> if a:
...     print('a evaluates to True even though it is not True')
...    
a evaluates to True even though it is not True

>>> b = 0
>>> b is False
False
>>> b is not True
True
>>> if b:
...     print('b evaluates to True')
... else:
...     print('b evaluates to False even though it is not False')
... 
b evaluates to False even though it is not False

I guess there is a typo in the article. You used %x instead of %d
the %d format specifier is used to convert an int value to a string, while %x helps to format the hexadecimal representation of the integer.

.title() method is missing from the Maniupulating Strings section of the cheatsheet.

Current situation:
Title is only referenced by way of the istitle() method in the IsX section. I.e. no reference to string.title() method.
Contrast this with methods for upper and lower, both of which have sections for .isupper()/islower() and .upper()/.lower().

Expected behaviour:
string.title() explicitly explained in the Manipulating Strings section of the cheatsheet.
E.g. Include string.title() in the same box as upper() and lower() methods. In which case it would also probably make sense to pull istitle() out of the IsX box and instead include it alongside isupper() and islower() for consistency.

on this page: https://www.pythoncheatsheet.org/cheatsheet/virtual-environments#anaconda

the hyperlink is pointing to Pipenv website (https://pipenv.pypa.io/en/latest/)

Add a new topic to the cheat sheet: json module

furniture[-1] = bed
furniture

Hi. I thought about adding a new topic "Metaclass".