kjodle/Notes-on-Python
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Minor updates

Browse Source
This commit is contained in:
Kenneth John Odle 2023-07-28 23:53:41 -04:00
parent 6661e5ab8b
commit f2e65649b9
1 changed files with 30 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
Notes on Python.tex
View File

@ -6,38 +6,39 @@
\usepackage{fancyvrb} % Even better code blocks
\usepackage{fvextra} % Even more better code blocks
\usepackage{enumitem} % Control spacing inside list environments
\usepackage{microtype}
\usepackage{microtype} % Better typography
\usepackage{wrapfig} % Allows us to use \wrapfigure command
\usepackage{adjustbox} % Adjust padding inside \minipage environment
\usepackage{tikz}
\usepackage{tikz} % Draw pictures
% Packages with options %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\usepackage{multicol}
\usepackage{multicol} % Most of our text will have two columns
\setlength\columnsep{25pt}
\usepackage{fancyhdr}
\pagestyle{fancy}
\fancyhf{} % Clear existing header/footer entries
\fancyhead[LE, RO]{\thepage} % Page number is always on the outside
\usepackage{fancyhdr} % Granular control over headers and footers
\pagestyle{fancy} % Define pagesyle «fancy»
\fancyhf{} % Clear existing header/footer entries
\fancyhead[LE, RO]{\thepage} % Page number is always on the outside
\fancyhead[CE, CO]{Notes on Python} % Title is always in the middle
\fancyhfoffset[LE,RO]{0in} % Adjust header and footer width to match text width
% \cfoot{Page \thepage}
% \renewcommand{\footrulewidth}{0.5pt}
\fancyhfoffset[LE,RO]{0in} % Adjust header and footer width to match text width
\renewcommand{\headrulewidth}{0.5pt}
\usepackage{geometry}
\geometry{
bmargin=0.75in, % bottom margin
tmargin=1in, % top margin
hmargin=0.75in, % horizontal margin
bindingoffset=0.25in
\usepackage{geometry} % Adjust margins
\geometry{ % Package options
bmargin=0.75in, % bottom margin
tmargin=1in, % top margin
hmargin=0.75in, % horizontal margin (both sides)
bindingoffset=0.25in % Just in case this is printed and bound
}
\usepackage[nottoc,numbib]{tocbibind} % Add references to TOC
\usepackage[hidelinks]{hyperref} % Include URLs
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% My macros %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Make a nice border and box for the tops of our examples
\newcommand\klab[3]{\vspace{#1}\noindent{}\hrulefill~~\fbox{\texttt{~#2~}}~~\hrulefill\vspace{#3}}
@ -50,7 +51,7 @@
% Make some call outs
\newcommand\kpull[2]{
\setlength{\intextsep}{5.0pt plus 2.0pt minus 2.0pt}%
\setlength{\intextsep}{3.0pt plus 2.0pt minus 2.0pt}
\setlength{\columnsep}{10pt}
\begin{wrapfigure}[]{r}[8pt]{0pt}
\fbox{
@ -65,7 +66,8 @@
} % End adjustbox
} % End fbox
\end{wrapfigure}
}
} % The width variable comes after the contents variable because the contents should give you some idea of how wide to make this.
% And make them work nicely with out multicol environment
% Not quite sure if commented lines are needed. More testing is required.
%\def\ksep{25pt}
@ -84,7 +86,7 @@
}
% Make a Python Symbol like a LaTeX symbol
\newcommand\kpy{P{\scriptsize \raisebox{-0.4em}{\hspace{-0.16em}Y}}T{\scriptsize \raisebox{-0.2em}{h}}\hspace{-0.1em}\raisebox{0.4em}{o}\hspace{0.05em}\raisebox{-0.2em}N}
\newcommand\kpy{P{\scriptsize \raisebox{-0.4em}{\hspace{-0.16em}Y}}T{\scriptsize \raisebox{-0.3em}{h}}\hspace{-0.15em}\raisebox{0.4em}{o}\hspace{0.05em}\raisebox{-0.2em}N}
% Additional options %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\raggedbottom
@ -122,12 +124,16 @@
\subsection{Why use Python?}
Many fields depend on \kpy\footnote{This is my attempt to produce a text symbol for Python, similar to \LaTeX{}. My thought is that it looks like a snake wriggling back and forth. Your mileage, of course, may (and probably will) vary.} to process data.
I won't bore you with details. If you have made enough effort to find this document, you are probably aware of the importance of the Python programming language. If not, however, I'll give a brief summary.
Mueller\cite{mueller:jp23} has many reasons why a knowledge of Python may be useful in a career search.
Many fields depend on \kpy\footnote{This is my attempt to produce a text symbol for Python, similar to \LaTeX{}. My thought is that it looks like a snake wriggling back and forth. Your mileage, of course, may (and probably will) vary. If you would like to use this in your own documents (why?) I have defined it as a macro, which you can obtain from the source code for this document. See the abstract for its location.} to process data.
Mueller\cite{mueller-jp:23} has many reasons why a knowledge of Python may be useful in a job search. \kpull{This is \textit{not} my favorite book.}{22mm} They were fairly accurate as of their publication (2023),but things change quickly, so a keyword search of your preferred job boards is always in order.
\subsection{IDEs and Python}
\subsection{Version 2 versus Version 3}
\kcole
\newpage
@ -147,10 +153,10 @@ Mueller\cite{mueller:jp23} has many reasons why a knowledge of Python may be use
\kcolb
\bibitem{mueller:jp23}
\bibitem{mueller-jp:23}
Mueller, John Paul.
\textit{Beginning Programming with Python for Dummies}.
John Wiley \& Sons Inc. (United States: New Jersey: Hoboken).
John Wiley \& Sons Inc. (United States: New Jersey: Hoboken).
3rd Edition,
2023.\\
\kbib{}This book \textit{heavily} emphasizes the use of Google Colab. It's basically an advertisement for the $\Gamma$oogle and \textit{highly} disappointing. Python is meant to be fairly universal and this book's approach seems to work counter to that intention.
@ -158,7 +164,7 @@ Mueller\cite{mueller:jp23} has many reasons why a knowledge of Python may be use
\bibitem{pythonorg:main}
python.org.
``Python for Beginners'',\\
\kref{https://www.python.org/about/gettingstarted/}{https://www.python.org/about/\\gettingstarted/}\\
\kbib\kref{https://www.python.org/about/gettingstarted/}{https://www.python.org/about/\\gettingstarted/}\\
\kbib The official site of the Python Software Foundation.
\kcole