CPython VS ipython

Python and some Bash scripts — for the enrichment logic and updates

If your version is 3.9 or above, you’re good to go. If not, download the latest version from python.org.

The quality of documentation is a known, highlighted concern in the community. There is particular interest in adopting Diataxis principles to improve documentation, both for Python itself and for packaging (see e.g. the user guide at https://packaging.python.org/en/latest/ , or the PyPA main site https://www.pypa.io/en/latest/ ).

If you want to help, there's a section on the Python forum (https://discuss.python.org/c/documentation/26) and a Discord server, and issues with documentation can also be reported on the main Python GitHub issue tracker (https://github.com/python/cpython/labels/docs).

Prior to having a bool type, Python didn't even have True/False keywords.

The reason something silly like `4 + True` works is because the bool type implements `tp_as_number` [0]. The reason it works this way is intentional because it would been a Python 3 str-style debacle if ints and bools were not interchangeable.

[0] https://github.com/python/cpython/blob/main/Objects/boolobje...

There's no mention of what Python version this is actually in.

After some digging, it looks like the answer is 3.14 [0], so we won't be seeing this until October [1].

One could argue that this is a security fix (just read the first sentence of the blog post) and should be included in all the currently supported Python versions (3.9+) [2].

[0] https://github.com/python/cpython/blob/main/Doc/whatsnew/3.1...

[1] https://peps.python.org/pep-0745/

[2] https://devguide.python.org/versions/

Then one day, the upcoming CPython 3.13.3 release, which we've taken on the e6dfa9d commit, came to our attention. I usually check projects in the Debug configuration. However, this time, I was curious and wanted to run the analysis in the Release configuration to see what happens in the interpreter shipped to the end user.

❯ CFLAGS="-I$(brew --prefix openssl)/include -I$(brew --prefix bzip2)/include -I$(brew --prefix readline)/include -I$(xcrun --show-sdk-path)/usr/include" \ LDFLAGS="-L$(brew --prefix openssl)/lib -L$(brew --prefix readline)/lib -L$(brew --prefix zlib)/lib -L$(brew --prefix bzip2)/lib" \ pyenv install --patch 3.7.2 < <(curl -sSL 'https://github.com/python/cpython/commit/8ea6353.patch?full_index=1') python-build: use [email protected] from homebrew python-build: use readline from homebrew Installing Python-3.7.2... patching file 'Misc/NEWS.d/next/macOS/2020-06-24-13-51-57.bpo-41100.mcHdc5.rst' patching file configure patching file configure.ac python-build: use tcl-tk from homebrew python-build: use readline from homebrew python-build: use zlib from xcode sdk Installed Python-3.7.2 to /Users/ryanlee/.pyenv/versions/3.7.2

GitHub Reference material: https://github.com/Fortune-Ndlovu/Intelligent-Support-Ticket-Routing-with-NLP-and-XGBoost/tree/main This notebook assumes you have the latest Python and the following libraries installed. First things first, Set Up Your Environment (Anaconda) by creating a new conda environment you can achieve this by opening up your terminal (or Anaconda Prompt):

If python is not installed in your PC then you can download it from https://www.python.org/

from concurrent.futures import ThreadPoolExecutor, as_completed from tqdm import tqdm urls = [ 'https://example.com', 'https://www.python.org', 'https://www.wikipedia.org', # Add more URLs... ] results = [] with ThreadPoolExecutor(max_workers=10) as executor: futures = {executor.submit(scrape_page, url): url for url in urls} for future in tqdm(as_completed(futures), total=len(futures), desc="Scraping"): results.append(future.result())

If you’re already using ipython, this isn’t a problem because you’ll already need to download most of these dependencies anyway. But if you’re not using ipython… you’ll still need to download those dependencies.

!pip install is error-prone, it is better to use %pip install, ipython even warns about this, https://github.com/ipython/ipython/pull/12954/

The git history (here is the git blame) shows it has not been updated in 9 year. Looks like a documentation issue that you should open an issue against.

Do you know IPython? It is a modern Python console that extends the capabilities of the classic builtin Python shell by offering introspection, tab completion, syntaxing coloring, as well as history. If you don't know it, I can't recommend it enough. More information can be found in its GitHub page.

There is an IPython ticket on GitHub on the topic, but it's unclear if the problem has been solved.

For further documentation on ipython using the CLI, you can refer to the GitHub link or the documentation page.

There’s one I’ve come across recently here where you’re fighting against syntax highlighting with extra error context. https://github.com/ipython/ipython/issues/13446#issuecomment...

I see. https://github.com/ipython/ipython/issues/13529