summaryrefslogtreecommitdiffstats
path: root/FOSS/Python/Dependencies/future-0.18.2/docs/why_python3.rst
diff options
context:
space:
mode:
authoryum <yum.food.vr@gmail.com>2023-01-01 21:05:27 -0800
committeryum <yum.food.vr@gmail.com>2023-01-01 21:44:45 -0800
commite25bdba3a3a53b09be5269d8b065c13b73ab55c3 (patch)
tree1d1dc1d94cde92c2f4f8ce86017395054787515d /FOSS/Python/Dependencies/future-0.18.2/docs/why_python3.rst
parent0d408cc812a094a708edbe4baf536e928731cfc3 (diff)
Embed git in package
package.ps1 fetches PortableGit and embeds it in the package. This eliminates all but one runtime dependency (MSVC++ Redistributable). * Move Python into a new FOSS folder.
Diffstat (limited to 'FOSS/Python/Dependencies/future-0.18.2/docs/why_python3.rst')
-rw-r--r--FOSS/Python/Dependencies/future-0.18.2/docs/why_python3.rst66
1 files changed, 66 insertions, 0 deletions
diff --git a/FOSS/Python/Dependencies/future-0.18.2/docs/why_python3.rst b/FOSS/Python/Dependencies/future-0.18.2/docs/why_python3.rst
new file mode 100644
index 0000000..a4b535f
--- /dev/null
+++ b/FOSS/Python/Dependencies/future-0.18.2/docs/why_python3.rst
@@ -0,0 +1,66 @@
+.. _why-python3:
+
+Why Python 3?
+=============
+
+- Python 2.7 is the final Python 2.x release. Python 3.x is the future.
+ The Python ecosystem needs to consolidate. A split or schism between
+ different incompatible versions is not healthy for growing the
+ community.
+- Function annotations
+- Decimal module 100x faster. As fast as floats.
+- Easier to learn. (Less cruft in language and stdlib, more consistency, better docstrings, etc.)
+- Much safer handling of unicode text and encodings: fewer bugs.
+- More memory efficiency (shared dict keys (PEP 412) and space-efficient
+ Unicode representation (PEP 393))
+- Exception chaining
+
+Why are Unicode strings better on Python 3?
+-------------------------------------------
+
+- it is not the default string type (you have to prefix the string
+ with a u to get Unicode);
+
+- it is missing some functionality, e.g. casefold;
+
+- there are two distinct implementations, narrow builds and wide builds;
+
+- wide builds take up to four times more memory per string as needed;
+
+- narrow builds take up to two times more memory per string as needed;
+
+- worse, narrow builds have very naive (possibly even "broken")
+ handling of code points in the Supplementary Multilingual Planes.
+
+The unicode string type in Python 3 is better because:
+
+- it is the default string type;
+
+- it includes more functionality;
+
+- starting in Python 3.3, it gets rid of the distinction between
+ narrow and wide builds;
+
+- which reduces the memory overhead of strings by up to a factor
+ of four in many cases;
+
+- and fixes the issue of SMP code points.
+
+(quote from a mailing list post by Steve D'Aprano on 2014-01-17).
+
+
+New features
+------------
+
+Standard library:
+~~~~~~~~~~~~~~~~~
+
+- SSL contexts in http.client
+-
+
+
+
+Non-arguments for Python 3
+==========================
+
+-