Mailman 3 February 2026 - Python-list

Re: Python
by rbowman March 11, 2026

March 11, 2026

On Tue, 16 Dec 2025 21:45:42 -0000 (UTC), Lawrence D’Oliveiro wrote: > On Mon, 15 Dec 2025 12:57:57 +0000, mm0fmf wrote: > >> On 14 Dec 2025 11:56:42 GMT, Stéphane CARPENTIER wrote: >> >>> My issues with python are: >>> - It's using indentations, so when I comment a block of code to see >> >> ''' and ''' are your friend > > Unless the block has triply-quoted strings inside it ... Yeah, well. I've been burned more than once by someone who added /* stupid comment */ someplace west of the 80th column in the code.

17 25

Parsing XMPP URI
by Schimon Jehudah March 1, 2026

March 1, 2026

Greetings. I am interested at advisory as to how to handle XMPP URI links. This is how module "urllib" handles this type of URI. urlparse -------- from urllib.parse import urlparse urlparse("xmpp:pubsub.python.i2p?;node=xmpp-python-news") ParseResult( scheme='xmpp', netloc='', path='pubsub.python.i2p', params='', query=';node=xmpp-python-news', fragment='') urlparse("xmpp:monty@python.i2p?;node=urn:xmpp:microblog:0;item=xmpp-and-python") ParseResult( scheme='xmpp', netloc='', path='monty(a)python.i2p', params='', query=';node=urn:xmpp:microblog:0;item=xmpp-and-python', fragment='') Hostname (netloc) should be "pubsub.movim.eu" and "python.i2p". parse_qs -------- Another issue, is not recognizing query parameters. from urllib.parse import parse_qs parse_qs("xmpp:monty@python.i2p?;node=urn:xmpp:microblog:0;item=xmpp-and-python") {'xmpp:monty@python.i2p?;node': ['urn:xmpp:microblog:0;item=xmpp-and-python']} The query parameters are not recorgnized unless the URI is formed in a similar fashion to HTTP URI, which is not a valid XMPP URI. parse_qs("xmpp://monty@python.i2p/?node=urn:xmpp:microblog:0&item=xmpp-and-python") {'xmpp://monty@python.i2p/?node': ['urn:xmpp:microblog:0'], 'item': ['xmpp-and-python']} Request ------- I would appreciate your advisory. Kind reagrds, Schimon

7 15

Hi New comer here !!
by Fahamidur Rahaman Feb. 28, 2026

Feb. 28, 2026

Hi there, I am new to open source contributions. I have 4+ years of experience working in AI/ML space. However I want to help build the next python by contributing as well as increase my understanding of this language. Wish me luck!!

2 1

ANN: EmPy 4.2.1 -- a powerful, robust and mature templating system for Python
by Erik Max Francis Feb. 9, 2026

Feb. 9, 2026

# EmPy 4.2.1 release announcement I'm pleased to announce the release of EmPy 4.2.1. The 4._x_ series is a modernization of the software and a revamp of the EmPy system to update its feature set and make it more consistent with the latest Python versions and practices. EmPy 4._x_ was also relicensed to BSD. The 4._x_ series adds new markups, including inline comments, backquote literals, chained if-then-else extended expression, functional expressions, support for modern Pythonic controls, stringized and multiline significators, disabling and re-enabling output, named escapes, diacritics, icons, emojis, and customizable extension markups. It adds support for configuration objects (replacing options dictionaries); native support for Unicode, file buffering, reference counted `sys.stdout` proxies and error dispatchers and handlers; fixes several serious bugs; has a set of full unit and system tests, an extensive builtin help system; and the online documention has been rewritten and expanded. It also allows customizing the underlying interpreter core and full support for EmPy modules -- EmPy documents which can be imported as modules. Attempts have been made to make EmPy 4._x_ as backward compatible as is practical. Most common markup has not changed; conversion of options (`..._OPT`) to configurations; the only changes being the change of `repr` markup to backquote markup; the removal of literal close parenthesis, bracket and brace markup; in-place markup has changed syntax (to make way for emojis); and custom (now extension) markup is now parsed more sensibly. Most backward-incompatible changes are in the embedding interface. The `Interpreter` constructor and global `expand` function now require keyword arguments to prevent further backward compatibility problems, though effort has been made to make the behavior as backward compatible as possible. The supported environment variables have changed, as well as the filter, diversion and hook APIs, and options dictionaries no longer exist (in deference to configurations). For a comprehensive list of changes from 3._x_ to 4.2.1, see: <http://www.alcyone.com/software/empy/ANNOUNCE.html#changes> ## Introduction: Welcome to EmPy! [EmPy](http://www.alcyone.com/software/empy/) is a powerful, robust and mature templating system for inserting Python code in template text. EmPy takes a source document, processes it, and produces output. This is accomplished via expansions, which are signals to the EmPy system where to act and are indicated with markup. Markup is set off by a customizable prefix (by default the at sign, `@`). EmPy can expand arbitrary Python expressions, statements and control structures in this way, as well as a variety of additional special forms. The remaining textual data is sent to the output, allowing Python to be used in effect as a markup language. EmPy also supports hooks, which can intercept and modify the behavior of a running interpreter; diversions, which allow recording and playback; filters, which can alter output and can be chained together. The system is highly configurable via command line options, configuration files, and environment variables. EmPy documents can also be imported as modules, and an extensive API is also available for embedding EmPy functionality in your own Python programs. EmPy also has a supplemental library for additional non-essential features (`emlib`), a documentation building library used to create this documentation (`emdoc`), and an extensive help system (`emhelp`) which can be queried from the command line with the main executable `em.py` (`-h/--help`, `-H/--topics=TOPICS`). The base EmPy interpreter can function with only the `em.py`/`em` file/module available. EmPy can be used in a variety of roles, including as a templating system, a text processing system (preprocessing and/or postprocessing), a simple macro processor, a frontend for a content management system, annotating documents, for literate programming, as a souped-up text encoding converter, a text beautifier (with macros and filters), and many other purposes. ### Markup overview Expressions are embedded in text with the `@(...)` notation; variations include conditional expressions with `@(...?...!...)` and the ability to handle thrown exceptions with `@(...$...)`. As a shortcut, simple variables and expressions can be abbreviated as `@variable`, `(a)object.attribute`, `@sequence[index]`, `@function(arguments...)`, and combinations. Functions can be called with expanded markup as arguments using `@function{markup}{...}`. Full-fledged statements are embedded with `@{...}`. Control flow in terms of conditional or repeated expansion is available with `@[...]`. A `@` followed by any whitespace character (including a newline) expands to nothing, allowing string concatenations and line continuations. Line comments are indicated with `@#...` including the trailing newline. `@*...*` allows inline comments. Output can be disabled and re-enabled with `@-...` and `@+...`, including the trailing newlines. Escapes are indicated with `@\...`; diacritics with `@^...`; icons with `@|...`; and emoji with `@:...:`. `@%...`, `@%!...`, `@%%...%%` and `@%%!...%%` indicate "significators," which are distinctive forms of variable assignment intended to specify document metadata in a format easy to parse externally. In-place expressions are specified with `@$...$...$`. Context name and line number changes can be made with `@?...` and `@!...`, respectively. A set of markups (`@((...))`, `@[[...]]`, `@{{...}}`, `@<...>`) are customizable by the user and can be used for any desired purpose. `` @`...` `` allows literal escaping of any EmPy markup. Output can be toggled on and off with `@+` and `@-`, respectively. And finally, a `@@` sequence (the prefix repeated once) expands to a single literal at sign. The prefix defaults to `@` but can be changed with the command line option `-p/--prefix=CHAR` (_environment variable:_ `EMPY_PREFIX`, _configuration variable:_ `prefix`). ### Getting the software The current version of EmPy is 4.2.1. The official URL for this Web site is <http://www.alcyone.com/software/empy/>. The latest version of the software is available in a tarball here: <http://www.alcyone.com/software/empy/empy-latest.tar.gz>. The software can be installed through PIP via this shell command: ``` % python3 -m pip install empy ``` For information about upgrading from 3._x_ to 4._x_, see <http://www.alcyone.com/software/empy/ANNOUNCE.html#changes>. ### Requirements EmPy works with any modern version of Python. Python version 3._x_ is expected to be the default and all source file references to the Python interpreter (_e.g._, the bangpath of the .py scripts) use `python3`. EmPy also has legacy support for versions of Python going back all the way to 2.4, with special emphasis on 2.7 regardless of its end-of-life status. It has no dependency requirements on any third-party modules and can run directly off of a stock Python interpreter. EmPy will run on any operating system with a full-featured Python interpreter; this includes, but is probably not limited to, the operating systems Linux, Windows, Windows Subsystem for Linux 2 (WSL2) and macOS (Darwin). Using EmPy requires knowledge of the [Python language](https://www.python.org/). EmPy is compatible with many different Python implementations, interpreter variants, packaging systems, and enhanced shells: {#supported-versions-table} | Variant | Supported versions | Description | | --- | --- | --- | | [CPython](https://www.python.org/) | 2.4 and up | Standard implementation in C | | [PyPy](https://www.pypy.org/) | 2.7 and up | Implementation with just-in-time compiler | | [Stackless Python](https://github.com/stackless-dev/stackless/wiki/) | 2.4 and up | Implementation supporting microthreading | | [IronPython](https://ironpython.net/) | 2.7 and up | Implementation for .NET CLR and Mono | | [Jython](https://www.jython.org/) | 2.5 to 2.7 (and up?) | Implementation for JVM | | [ActiveState Python](https://www.activestate.com/products/python/) | 2.7 and up | Secure supply chain open source solution | | [eGenix PyRun](https://www.egenix.com/products/python/PyRun/) | 2.5 and up | One-file, no-installation CPython environment | | [WinPython](https://winpython.github.io/) | 3.0 and up | Portable Scientific Python for Windows | | [PortablePython](https://portablepython.com/) | 2.7 and up | Minimalistic Python distribution for Windows | | [IDLE](https://docs.python.org/3/library/idle.html) | all | Python's Integrated Development and Learning Environment | | [IPython](https://ipython.org/) | all | Powerful interactive shell; kernel for [Jupyter](https://jupyter.org/) | EmPy is also compatible with scaled-down implementations of Python, provided they support the set of standard modules that EmPy requires, namely: - `codecs` - `copy` - `getopt` - `os` - `platform` - `re` - `sys` - `unicodedata` Only a few .py module file(s) are needed to use EmPy; they can be installed system-wide through a distribution package, via PIP, or just dropped into any desired directory in the `PYTHONPATH` (as a module) and/or `PATH` (as an executable). A minimal installation need only install the em.py file, either as an importable module or an executable, or both, depending on the user's needs. EmPy also has optional support for several [third-party emoji modules](#third-party-emoji-modules); see [](#emoji-markup) for details. The testing system included (the test.sh script and the tests and suites directories) is intended to run on Unix-like systems with a Bourne-like shell (_e.g._, sh, bash, zsh, etc.). EmPy is routinely tested with all supported versions of all available interpreters. If you find an incompatibility with your Python interpreter or operating system, [let me know](#reporting-bugs). ### License This software is licensed under [BSD (3-Clause)](https://opensource.org/licenses/bsd-3-clause/). ### Recent release history (since 3._x_) {#latest-release} 4.2.1 (2026 Feb 8) : `codecs.open` is deprecated as of Python 3.14, so use `open` instead in binary mode; better proxy and module finder management using `sys` module; uniform attachment and detachment of plugins; converted and expanded documentation to Furo theme; better Java exception printing under Jython; add preinitializers, postinitialiers, and requirements for testing; additions to named escapes; add `SimpleToken` token factory. -- Erik Max Francis && max(a)alcyone.com && http://www.alcyone.com/max/ San Jose, CA, USA && 37 18 N 121 57 W && Skype erikmaxfrancis Human love is often but the encounter of two weaknesses. -- Francois Mauriac

1 0

def __getitem__(self, key=None)
by Lex Feb. 8, 2026

Feb. 8, 2026

def __getitem__(self, key=None): if key is None: return self.items[0] return self.items[key] myitemsobject[] -> item #0 or custom

1 0