add python docs option.

Author: v0lta

data/python_docs/input.txt

@@ -0,0 +1,19 @@
+""" Merge the python docs into a single file."""
+
+import os
+import pathlib
+
+
+if __name__ == '__main__':
+
+	with open("input.txt", "w") as write_to_input_file:
+		for root, folder, docfiles in os.walk("./python-3.13-docs-text"):
+			for docfile in docfiles:
+				if docfile.split(".")[-1] == 'txt':
+					path = pathlib.Path(f"{root}/{docfile}")
+					with open(path, "r") as read_file:
+						lines = read_file.readlines()
+						write_to_input_file.writelines(lines)
+						write_to_input_file.write(" ")
+
+

data/python_docs/merge.py

@@ -0,0 +1,33 @@
+About this documentation
+************************
+
+Python's documentation is generated from reStructuredText sources
+using Sphinx, a documentation generator originally created for Python
+and now maintained as an independent project.
+
+Development of the documentation and its toolchain is an entirely
+volunteer effort, just like Python itself.  If you want to contribute,
+please take a look at the Dealing with Bugs page for information on
+how to do so.  New volunteers are always welcome!
+
+Many thanks go to:
+
+* Fred L. Drake, Jr., the creator of the original Python documentation
+  toolset and author of much of the content;
+
+* the Docutils project for creating reStructuredText and the Docutils
+  suite;
+
+* Fredrik Lundh for his Alternative Python Reference project from
+  which Sphinx got many good ideas.
+
+
+Contributors to the Python documentation
+========================================
+
+Many people have contributed to the Python language, the Python
+standard library, and the Python documentation.  See Misc/ACKS in the
+Python source distribution for a partial list of contributors.
+
+It is only with the input and contributions of the Python community
+that Python has such wonderful documentation -- Thank You!

data/python_docs/python-3.13-docs-text/about.txt

@@ -0,0 +1,111 @@
+Dealing with Bugs
+*****************
+
+Python is a mature programming language which has established a
+reputation for stability.  In order to maintain this reputation, the
+developers would like to know of any deficiencies you find in Python.
+
+It can be sometimes faster to fix bugs yourself and contribute patches
+to Python as it streamlines the process and involves less people.
+Learn how to contribute.
+
+
+Documentation bugs
+==================
+
+If you find a bug in this documentation or would like to propose an
+improvement, please submit a bug report on the tracker.  If you have a
+suggestion on how to fix it, include that as well.
+
+You can also open a discussion item on our Documentation Discourse
+forum.
+
+If you find a bug in the theme (HTML / CSS / JavaScript) of the
+documentation, please submit a bug report on the python-doc-theme bug
+tracker.
+
+If you're short on time, you can also email documentation bug reports
+to [email protected] (behavioral bugs can be sent to python-
+[email protected]). 'docs@' is a mailing list run by volunteers; your
+request will be noticed, though it may take a while to be processed.
+
+See also:
+
+  Documentation bugs
+     A list of documentation bugs that have been submitted to the
+     Python issue tracker.
+
+  Issue Tracking
+     Overview of the process involved in reporting an improvement on
+     the tracker.
+
+  Helping with Documentation
+     Comprehensive guide for individuals that are interested in
+     contributing to Python documentation.
+
+  Documentation Translations
+     A list of GitHub pages for documentation translation and their
+     primary contacts.
+
+
+Using the Python issue tracker
+==============================
+
+Issue reports for Python itself should be submitted via the GitHub
+issues tracker (https://github.com/python/cpython/issues). The GitHub
+issues tracker offers a web form which allows pertinent information to
+be entered and submitted to the developers.
+
+The first step in filing a report is to determine whether the problem
+has already been reported.  The advantage in doing so, aside from
+saving the developers' time, is that you learn what has been done to
+fix it; it may be that the problem has already been fixed for the next
+release, or additional information is needed (in which case you are
+welcome to provide it if you can!). To do this, search the tracker
+using the search box at the top of the page.
+
+If the problem you're reporting is not already in the list, log in to
+GitHub. If you don't already have a GitHub account, create a new
+account using the "Sign up" link. It is not possible to submit a bug
+report anonymously.
+
+Being now logged in, you can submit an issue. Click on the "New issue"
+button in the top bar to report a new issue.
+
+The submission form has two fields, "Title" and "Comment".
+
+For the "Title" field, enter a *very* short description of the
+problem; fewer than ten words is good.
+
+In the "Comment" field, describe the problem in detail, including what
+you expected to happen and what did happen.  Be sure to include
+whether any extension modules were involved, and what hardware and
+software platform you were using (including version information as
+appropriate).
+
+Each issue report will be reviewed by a developer who will determine
+what needs to be done to correct the problem. You will receive an
+update each time an action is taken on the issue.
+
+See also:
+
+  How to Report Bugs Effectively
+     Article which goes into some detail about how to create a useful
+     bug report. This describes what kind of information is useful and
+     why it is useful.
+
+  Bug Writing Guidelines
+     Information about writing a good bug report.  Some of this is
+     specific to the Mozilla project, but describes general good
+     practices.
+
+
+Getting started contributing to Python yourself
+===============================================
+
+Beyond just reporting bugs that you find, you are also welcome to
+submit patches to fix them.  You can find more information on how to
+get started patching Python in the Python Developer's Guide.  If you
+have questions, the core-mentorship mailing list is a friendly place
+to get answers to any and all questions pertaining to the process of
+fixing issues in Python.

data/python_docs/python-3.13-docs-text/bugs.txt

@@ -0,0 +1,60 @@
+Abstract Objects Layer
+**********************
+
+The functions in this chapter interact with Python objects regardless
+of their type, or with wide classes of object types (e.g. all
+numerical types, or all sequence types).  When used on object types
+for which they do not apply, they will raise a Python exception.
+
+It is not possible to use these functions on objects that are not
+properly initialized, such as a list object that has been created by
+"PyList_New()", but whose items have not been set to some non-"NULL"
+value yet.
+
+* Object Protocol
+
+* Call Protocol
+
+  * The *tp_call* Protocol
+
+  * The Vectorcall Protocol
+
+    * Recursion Control
+
+    * Vectorcall Support API
+
+  * Object Calling API
+
+  * Call Support API
+
+* Number Protocol
+
+* Sequence Protocol
+
+* Mapping Protocol
+
+* Iterator Protocol
+
+* Buffer Protocol
+
+  * Buffer structure
+
+  * Buffer request types
+
+    * request-independent fields
+
+    * readonly, format
+
+    * shape, strides, suboffsets
+
+    * contiguity requests
+
+    * compound requests
+
+  * Complex arrays
+
+    * NumPy-style: shape and strides
+
+    * PIL-style: shape, strides and suboffsets
+
+  * Buffer-related functions

data/python_docs/python-3.13-docs-text/c-api/abstract.txt

@@ -0,0 +1,62 @@
+Allocating Objects on the Heap
+******************************
+
+PyObject *_PyObject_New(PyTypeObject *type)
+    *Return value: New reference.*
+
+PyVarObject *_PyObject_NewVar(PyTypeObject *type, Py_ssize_t size)
+    *Return value: New reference.*
+
+PyObject *PyObject_Init(PyObject *op, PyTypeObject *type)
+    *Return value: Borrowed reference.** Part of the Stable ABI.*
+
+   Initialize a newly allocated object *op* with its type and initial
+   reference.  Returns the initialized object.  Other fields of the
+   object are not affected.
+
+PyVarObject *PyObject_InitVar(PyVarObject *op, PyTypeObject *type, Py_ssize_t size)
+    *Return value: Borrowed reference.** Part of the Stable ABI.*
+
+   This does everything "PyObject_Init()" does, and also initializes
+   the length information for a variable-size object.
+
+PyObject_New(TYPE, typeobj)
+
+   Allocate a new Python object using the C structure type *TYPE* and
+   the Python type object *typeobj* ("PyTypeObject*"). Fields not
+   defined by the Python object header are not initialized. The caller
+   will own the only reference to the object (i.e. its reference count
+   will be one). The size of the memory allocation is determined from
+   the "tp_basicsize" field of the type object.
+
+PyObject_NewVar(TYPE, typeobj, size)
+
+   Allocate a new Python object using the C structure type *TYPE* and
+   the Python type object *typeobj* ("PyTypeObject*"). Fields not
+   defined by the Python object header are not initialized.  The
+   allocated memory allows for the *TYPE* structure plus *size*
+   ("Py_ssize_t") fields of the size given by the "tp_itemsize" field
+   of *typeobj*.  This is useful for implementing objects like tuples,
+   which are able to determine their size at construction time.
+   Embedding the array of fields into the same allocation decreases
+   the number of allocations, improving the memory management
+   efficiency.
+
+void PyObject_Del(void *op)
+
+   Releases memory allocated to an object using "PyObject_New" or
+   "PyObject_NewVar".  This is normally called from the "tp_dealloc"
+   handler specified in the object's type.  The fields of the object
+   should not be accessed after this call as the memory is no longer a
+   valid Python object.
+
+PyObject _Py_NoneStruct
+
+   Object which is visible in Python as "None".  This should only be
+   accessed using the "Py_None" macro, which evaluates to a pointer to
+   this object.
+
+See also:
+
+  "PyModule_Create()"
+     To allocate and create extension modules.

data/python_docs/python-3.13-docs-text/c-api/allocation.txt

@@ -0,0 +1,69 @@
+API and ABI Versioning
+**********************
+
+CPython exposes its version number in the following macros. Note that
+these correspond to the version code is **built** with, not
+necessarily the version used at **run time**.
+
+See C API Stability for a discussion of API and ABI stability across
+versions.
+
+PY_MAJOR_VERSION
+
+   The "3" in "3.4.1a2".
+
+PY_MINOR_VERSION
+
+   The "4" in "3.4.1a2".
+
+PY_MICRO_VERSION
+
+   The "1" in "3.4.1a2".
+
+PY_RELEASE_LEVEL
+
+   The "a" in "3.4.1a2". This can be "0xA" for alpha, "0xB" for beta,
+   "0xC" for release candidate or "0xF" for final.
+
+PY_RELEASE_SERIAL
+
+   The "2" in "3.4.1a2". Zero for final releases.
+
+PY_VERSION_HEX
+
+   The Python version number encoded in a single integer.
+
+   The underlying version information can be found by treating it as a
+   32 bit number in the following manner:
+
+   +---------+---------------------------+---------------------------+----------------------------+
+   | Bytes   | Bits (big endian order)   | Meaning                   | Value for "3.4.1a2"        |
+   |=========|===========================|===========================|============================|
+   | 1       | 1-8                       | "PY_MAJOR_VERSION"        | "0x03"                     |
+   +---------+---------------------------+---------------------------+----------------------------+
+   | 2       | 9-16                      | "PY_MINOR_VERSION"        | "0x04"                     |
+   +---------+---------------------------+---------------------------+----------------------------+
+   | 3       | 17-24                     | "PY_MICRO_VERSION"        | "0x01"                     |
+   +---------+---------------------------+---------------------------+----------------------------+
+   | 4       | 25-28                     | "PY_RELEASE_LEVEL"        | "0xA"                      |
+   |         +---------------------------+---------------------------+----------------------------+
+   |         | 29-32                     | "PY_RELEASE_SERIAL"       | "0x2"                      |
+   +---------+---------------------------+---------------------------+----------------------------+
+
+   Thus "3.4.1a2" is hexversion "0x030401a2" and "3.10.0" is
+   hexversion "0x030a00f0".
+
+   Use this for numeric comparisons, e.g. "#if PY_VERSION_HEX >= ...".
+
+   This version is also available via the symbol "Py_Version".
+
+const unsigned long Py_Version
+    * Part of the Stable ABI since version 3.11.*
+
+   The Python runtime version number encoded in a single constant
+   integer, with the same format as the "PY_VERSION_HEX" macro. This
+   contains the Python version used at run time.
+
+   Added in version 3.11.
+
+All the given macros are defined in Include/patchlevel.h.