Mailman 3 April 2021 - Python-announce-list

Wing Python IDE 7.2.9 has been released
by Wingware April 12, 2021

April 12, 2021

Wing 7.2.9 adds remote development for 64-bit Raspberry Pi, improves auto-closing of quotes, optimizes change tracking when large numbers of project files change at once, improves debugger data display for some value types, and makes a number of other usability improvements. Details: https://wingware.com/news/2021-04-12 Downloads: https://wingware.com/downloads == About Wing == Wing is a light-weight but full-featured Python IDE designed specifically for Python, with powerful editing, code inspection, testing, and debugging capabilities. Wing's deep code analysis provides auto-completion, auto-editing, and refactoring that speed up development. Its top notch debugger works with any Python code, locally or on a remote host. Wing also supports test-driven development, version control, UI color and layout customization, and includes extensive documentation and support. Wing is available in three product levels: Wing Pro is the full-featured Python IDE for professional developers, Wing Personal is a free Python IDE for students and hobbyists (omits some features), and Wing 101 is a very simplified free Python IDE for beginners (omits many features). Learn more at https://wingware.com/

1 0

ANN: MiniFFTW 1.0.4, a FFTW wrapping C-extension
by Philipp Stanner April 11, 2021

April 11, 2021

Hi! I hereby want to announce a small C-Extension we created for an internal research project. It might be useful to scientists who use 1- dimensional fourier transforms frequently. It wrapps the "Fastest Fourier Transformation in the West", or at least a very small subset of it (currently only the complex 1D transform, both serial and with MPI, and wisdom handling). You can find the source code, licensed under GPLv3, here: https://git.sr.ht/~imperator/mini-mpi-fftw I have a sourcehut mailing list for discussions, bug reports etc. ~imperator/mini-mpi-fftw-discuss(a)lists.sr.ht https://lists.sr.ht/~imperator/mini-mpi-fftw-discuss ...and might in the future announce new versions on this mailing list: https://lists.sr.ht/~imperator/mini-mpi-fftw-announce Minifftw's main design goal is to make the FFTW on Linux clusters with MPI very easy to use for people without much experience on MPI. You can build two versions of the module * one without MPI, wrapping the serial FFTW for usage i.e. on desktop computers * one with MPI, wrapping the MPI-FFTW for distributed computing. Both versions behave exactly the same from the perspective of the Python program. Therefore, the programmer can run the same simulation program without changing the code on his laptop (within hardware resource limits, of course) or on a cluster. Another advantage is that it directly writes to and reads from the memory of passed numpy arrays, without copying memory when entering or leaving the API. MFFTW aims at mostly offering the FFTW API to the Python world, so you have the same functions (plan, execute) available and don't really need to relearn anything when you already know FFTW. MFFTW manually uses MPI to distribute and collect parts of a whole contiguous array behind the scenes. That's necessary because FFTW only supports pure distributed memory, where each process allocates and fills its memory slice locally. Therefore, MFFTW is intended for comparatively small transforms (currently maximum size 2^31-1 complex numbers), which you want to speed up using distributed computing. Our tests showed that, with the right configuration, you can gain significant performance, even with arrays much smaller to what distributed memory FFTW seems to be intended for. The disadvantage of this easy-to-use approach is that the control over MPI is taken away from the user, therefore I don't think it will be possible to use MFFTW and other MPI-requiring functions in the same simulation. Also, currently, the wrapper is very small according the implemented functionality. We maybe will implement more transforms and would accept patches implementing those, but our own simulations only need the DFT- 1D. The README should answer most questions about the internals, I hope. Next steps might include packaging for Debian and Arch-Linux. I am unsure, though, how much sense this makes, because you'd either have to provide two packages (w/ & ^w/ MPI), or needed a runtime-flag to use serial FFTW in a package build for MPI. Also, I expect the wrapper to be most useful on clusters, where you will likely have a custom build process without standard package managers. I hope it will be helpful to some of you. Greetings, P. <P><A HREF="https://git.sr.ht/~imperator/mini-mpi-fftw ">MiniFFTW 1.0.4</A> -short C-Extension for easy FFTW-MPI usage (11-April-21)

1 0

PyDev 8.3.0 Released
by Fabio Zadrozny April 10, 2021

April 10, 2021

PyDev 8.3.0 Release Highlights - *Java 11* is now required to run PyDev. - *External linters* - Configurations of the linters can be saved to the project or user settings. - Flake8 has a more flexible UI for configuration. - *Others* - Option to add comments all at a single indent (note: this is now the default). - LRU for context-insensitive completion/quick fix. - Fixed some code-completion cases where *self* was wrongly added. - Environment variables are now supported in *.pydevproject* (expected format: *${env_var:VAR_NAME}*). About PyDev PyDev is an open-source Python IDE on top of Eclipse for Python, Jython and IronPython development, now also available for Python on Visual Studio Code. It comes with goodies such as code completion, syntax highlighting, syntax analysis, code analysis, refactor, debug, interactive console, etc. It is also available as a standalone through LiClipse with goodies such as multiple cursors, theming and support for many other languages, such as Django Templates, Jinja2, Html, JavaScript, etc. Links: PyDev: http://pydev.org PyDev Blog: http://pydev.blogspot.com PyDev on VSCode: http://pydev.org/vscode LiClipse: http://www.liclipse.com PyVmMonitor - Python Profiler: http://www.pyvmmonitor.com/ Cheers, Fabio Zadrozny

1 0

Hypertag. New language for HTML templating /w Django support
by Marcin April 9, 2021

April 9, 2021

Hypertag (http://hypertag.io/ ) is a new language for document generation and HTML templating that has been released recently. Inspired by indentation-based template languages (Slim, Haml, Shpaml), it provides clean, readable syntax, and multiple original features: native custom tags, Python-like imports and control blocks, DOM manipulation, complex expressions, filter pipelines, Django integration, and more... Available on GitHub and PyPI: - https://github.com/mwojnars/hypertag - https://pypi.org/project/hypertag-lang/ EXAMPLE #1: ul li | Cat li | Dog li | Rabbit & Guinea pig The above Hypertag script is rendered to: <ul> <li>Cat</li> <li>Dog</li> <li>Rabbit & Guinea pig</li> </ul> EXAMPLE #2: h1 | Table of Contents div for k in [1,2,3]: a href='#heading-{k}' : b : i | Heading no. $k This script contains a control block (for), chained tags (a, b, i) and an attribute (href). It is rendered to: <h1>Table of Contents</h1> <div> <a href="#heading-1"><b><i>Heading no. 1</i></b></a> <a href="#heading-2"><b><i>Heading no. 2</i></b></a> <a href="#heading-3"><b><i>Heading no. 3</i></b></a> </div> Hypertag can be called directly from Python code, or be plugged as a template backend into Django. Hypertag scripts can use all of Django’s filter functions. Hypertag is a full-featured standalone language that is not limited to HTML alone and can be adapted to produce different markups. See the Quick Start (https://github.com/mwojnars/hypertag) and Language Reference (http://hypertag.io/) for details. Install from PyPI as "hypertag-lang". Best regards, Marcin Wojnarski (mwojnarski "at" paperity.org) -- Marcin Wojnarski, Founder and CEO at Paperity, www.paperity.org www.linkedin.com/in/marcinwojnarski www.facebook.com/Paperity https://twitter.com/Paperity Paperity. Open science aggregated.

1 0

PyCon ZA 2021 - Call for Submissions
by Neil Muller April 8, 2021

April 8, 2021

PyCon ZA 2021 will take place on the 7th & 8th of October, 2021. This year, due to the ongoing pandemic, PyCon ZA will again be an online event. We are looking for the following presentations: - Keynotes (45 minute long talks on a subject of general interest) - Talks (30 minute long talks on more specific topics) If you would like to give a presentation, please register at https://za.pycon.org/ and submit your proposal, following the instructions at https://za.pycon.org/talks/submit-talk/ . We have a number of tracks available, including: Data Science, Teaching and Learning with Python, Web, Scientific Computing, Testing and Other (which includes all talks that don't fall under the mentioned tracks). We hope to notify accepted presenters by no later than the 31st of August 2021. Speakers will be expected to be available after the presentation for a short Q&A session. Shared sessions are also possible. The presentations will be in English. PyCon ZA offers a mentorship program for inexperienced speakers. If you would like assistance preparing your submission, email team(a)za.pycon.org with a rough draft of your talk proposal and we'll find a suitable experienced speaker to act as a mentor. If you want to present something that doesn't fit into the two talk categories at PyCon ZA, please contact the organising committee at team(a)za.pycon.org so we can discuss whether that will be feasible. -- Neil Muller On behalf of the PyCon ZA organising committee

1 0

Presenting our EuroPython 2021 logo
by M.-A. Lemburg April 7, 2021

April 7, 2021

Over the last couple of weeks, we have worked with our designer Jessica Peña to come up with a logo which reflects both our desire to come together online during the pandemic and shows how well our community is interconnected around the world. Here's our brand new logo for EuroPython 2021 Online: https://blog.europython.eu/presenting-our-europython-2020-logo/ Hope you like it :-) We will soon make EuroPython 2021 merchandise available with the new logo in our EuroPython merch shop, so you can order t-shirts, sweatshirts, caps and mugs to show your support and love for the conference. Help spread the word -------------------- Please help us spread this message by sharing it on your social networks as widely as possible. Thank you ! Link to the blog post: https://blog.europython.eu/presenting-our-europython-2020-logo/ Tweet: https://twitter.com/europython/status/1379750330347499520 Enjoy, -- EuroPython 2021 Team https://www.europython-society.org/

1 0

[RELEASE] The last Python 3.10 alpha (3.10.0a7) is available - Prepare for beta freeze
by Pablo Galindo Salgado April 6, 2021

April 6, 2021

Brrrrr..... do you feel that? That's the chill of *beta freeze* coming closer. Meanwhile, your friendly CPython release team doesn’t rest even on holidays and we have prepared a shiny new release for you: Python 3.10.0a7. **************************************************** Dear fellow core developer: This alpha is the last release before feature freeze (2021-05-03), so make sure that all new features and PEPs are landed in the master branch before we release the first beta. Please, be specially mindfully to check the CI and the buildbots, maybe even using the test-with-buildbots label in GitHub before merging so the release team don’t need to fix a bunch of reference leaks or platform-specific problems on the first beta release. **************************************************** *Go get the new alpha here:* https://www.python.org/downloads/release/python-3100a7/ *Python 3.10.0a7*Release Date: April 5, 2021 This is an early developer preview of Python 3.10 *Major new features of the 3.10 series, compared to 3.9* Python 3.10 is still in development. This release, 3.10.0a7 is the last of seven planned alpha releases. Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process. During the alpha phase, features may be added up until the start of the beta phase (2021-05-03) and, if necessary, may be modified or deleted up until the release candidate phase (2021-10-04). Please keep in mind that this is a preview release and its use is not recommended for production environments. Many new features for Python 3.10 are still being planned and written. Among the new major new features and changes so far: PEP 623 – Deprecate and prepare for the removal of the wstr member in PyUnicodeObject. PEP 604 – Allow writing union types as X | Y PEP 612 – Parameter Specification Variables PEP 626 – Precise line numbers for debugging and other tools. bpo-38605: from __future__ import annotations (PEP 563) is now the default. PEP 618 – Add Optional Length-Checking To zip. bpo-12782: Parenthesized context managers are now officially allowed. PEP 632 – Deprecate distutils module. PEP 613 – Explicit Type Aliases PEP 634 – Structural Pattern Matching: Specification PEP 635 – Structural Pattern Matching: Motivation and Rationale PEP 636 – Structural Pattern Matching: Tutorial PEP 644 – Require OpenSSL 1.1.1 or newer PEP 624 – Remove Py_UNICODE encoder APIs PEP 597 – Add optional EncodingWarning (Hey, fellow core developer, if a feature you find important is missing from this list, let Pablo know.) The next pre-release of Python 3.10 will be 3.10.0b1 ( the first beta release and feature freeze ), currently scheduled for Monday, 2021-05-03. *And now for something completely different* In physics, the twin paradox is a thought experiment in special relativity involving identical twins, one of whom makes a journey into space in a high-speed rocket and returns home to find that the twin who remained on Earth has aged more. This result appears puzzling because each twin sees the other twin as moving, and so, as a consequence of an incorrect and naive application of time dilation and the principle of relativity, each should paradoxically find the other to have aged less. However, this scenario can be resolved by realising that the travelling twin is undergoing acceleration, which makes him a non-inertial observer. In both views, there is no symmetry between the spacetime paths of the twins. Therefore, the twin paradox is not a paradox in the sense of a logical contradiction. Your friendly release team, Pablo Galindo Salgado @pablogsal Ned Deily @nad Steve Dower @steve.dower

1 0

NoPdb 0.1.0 – Non-interactive Python Debugger
by Ondřej Cífka April 6, 2021

April 6, 2021

I'm happy to announce the release of NoPdb 0.1.0! NoPdb is a non-interactive (programmatic) debugger for Python. This means it gives you access to debugger-like superpowers directly from your code. NoPdb allows to: - capture function calls, including arguments, local variables, return values and stack traces - set "breakpoints" that trigger user-defined actions when hit, namely: - evaluate expressions to retrieve their values later - execute arbitrary code, including modifying local variables - enter an interactive debugger like pdb Installation: pip install nopdb Docs: https://nopdb.readthedocs.io/ GitHub: https://github.com/cifkao/nopdb License: BSD-3-Clause <P><A HREF="https://github.com/cifkao/nopdb">NoPdb 0.1.0</A>, a non-interactive Python debugger. (06-Apr-21)</P>

1 0

[RELEASE] Python 3.9.4 hotfix is now available
by Łukasz Langa April 4, 2021

April 4, 2021

Python 3.9.3 was released two days ago on Friday, April 2nd. It contains important security content listed below for reference. Unfortunately, it also introduced an unintentional ABI incompatibility, making some C extensions built with Python 3.9.0 - 3.9.2 crash with Python 3.9.3 on 32-bit systems. To minimize disruption, I decided to recall 3.9.3 and introduce this hotfix release: 3.9.4. We highly recommend upgrading your Python 3.9 installations to 3.9.4 at your earliest convenience. Get it here: https://www.python.org/downloads/release/python-394/ <https://www.python.org/downloads/release/python-394/> What is “ABI compatibility”? Python guarantees that within a given language series (like the current 3.9) binary extensions written in C or C++ and compiled against headers of one release (like 3.9.0) will be importable from other versions in the same series (like 3.9.3). If this weren’t the case, library authors would have to ship separate binary wheels on PyPI for every single bugfix release of Python. That would be very inconvenient. <https://discuss.python.org/t/python-3-9-4-hotfix-is-now-available/8056#what…>What broke in Python 3.9.3? In a fix for a corner-case crash around recursion limits and exceptions, the PyThreadState struct needed to change. While PyThreadState’s only documented public member is the *interp field <https://docs.python.org/3.9/c-api/init.html#c.PyThreadState>, it’s not uncommon for C extensions to access other fields in this struct as well. When I approved the backport of this fix, I missed the fact that the variable size change would change the memory layout of said struct on 32-bit systems (on 64-bit systems alignment rules made the size change backwards compatible). Merging the backport was a mistake, and so 3.9.4 reverts it to restore compatibility with binary extensions built against Python 3.9.0 - 3.9.2. Details in bpo-43710 <https://bugs.python.org/issue43710>. <https://discuss.python.org/t/python-3-9-4-hotfix-is-now-available/8056#secu…>Security Content in Python 3.9.3 bpo-43631 <https://bugs.python.org/issue43631>: high-severity CVE-2021-3449 and CVE-2021-3450 were published for OpenSSL, it’s been upgraded to 1.1.1k in CI, and macOS and Windows installers. bpo-42988 <https://bugs.python.org/issue42988>: CVE-2021-3426: Remove the getfile feature of the pydoc module which could be abused to read arbitrary files on the disk (directory traversal vulnerability). Moreover, even source code of Python modules can contain sensitive data like passwords. Vulnerability reported by David Schwörer. bpo-43285 <https://bugs.python.org/issue43285>: ftplib no longer trusts the IP address value returned from the server in response to the PASV command by default. This prevents a malicious FTP server from using the response to probe IPv4 address and port combinations on the client network. Code that requires the former vulnerable behavior may set a trust_server_pasv_ipv4_address attribute on their ftplib.FTP instances to True to re-enable it. bpo-43439 <https://bugs.python.org/issue43439>: Add audit hooks for gc.get_objects(), gc.get_referrers() and gc.get_referents(). Patch by Pablo Galindo. <https://discuss.python.org/t/python-3-9-4-hotfix-is-now-available/8056#rele…>Release Calendar Maintenance releases for the 3.9 series will continue at regular bi-monthly intervals, with 3.9.5 planned for May 3rd 2021 as well. <https://discuss.python.org/t/python-3-9-4-hotfix-is-now-available/8056#what…>What’s new? The Python 3.9 series contains many new features and optimizations over 3.8. See the “What’s New in Python 3.9 <https://docs.python.org/3.9/whatsnew/3.9.html>” document for more information about features included in the 3.9 series. We also have a detailed change log for 3.9.3 <https://docs.python.org/release/3.9.3/whatsnew/changelog.html> specifically. Detailed information about all changes made in version 3.8.9 can be found in its respective changelog <https://docs.python.org/release/3.8.9/whatsnew/changelog.html>. <https://discuss.python.org/t/python-3-9-4-hotfix-is-now-available/8056#we-h…>We hope you enjoy those new releases! Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. Your friendly release team, Łukasz Langa @ambv <https://discuss.python.org/u/ambv> Ned Deily @nad <https://discuss.python.org/u/nad> Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>

1 0

pytest 6.2.3
by Ran Benita April 3, 2021

April 3, 2021

pytest 6.2.3 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at https://docs.pytest.org/en/stable/changelog.html. Thanks to all of the contributors to this release: * Bruno Oliveira * Ran Benita Happy testing, The pytest Development Team

1 0