testmon.org @1testmon

pytest-testmon 2.0.7 is out. The patch version (the version number after second dot) is ignored when storing and determining packages installed in your environment.

Every Python dialect, subset, or superset: Cython: Superset of Python that lets you write C extensions. Python-like syntax, static typing, and direct C API access. Hy: A Lisp dialect that embedded in Python. Transforms Lisp code into a Python AST. Mojo: A new Python superset that seems to integrate with Cython and provide more extensions to target accelerators. Stackless Python: A modified version of the Python interpreter that supports lightweight concurrency that avoids adding a new frame to the call stack for every function. RPython: A subset of Python used to write the PyPy interpreter. Statically typed and has some restrictions. It can be translated to C. Skylark (Starlark): A dialect of Python used as the configuration language for the Bazel build system. Syntactically a subset of both Python 2 and Python 3. Pythran: Ahead-of-time compiler for a subset of Python with a focus on scientific computing. Numba: JIT compiler for a subset of Python and NumPy code. MicroPython: A subset that aims to efficiently implement Python 3 for microcontrollers and other constrained environments. CircuitPython: A fork of MicroPython geared at educational use cases (e.g., RaspberryPi, Adafruit). TorchScript: A subset of Python used to create serializable and optimizable models from PyTorch code. Jython: Implements Python in Java, running on the JVM. Mainly used to embed Python in Java as a scripting language. GraalPy: Like Jython, but targets the GraalVM. IronPython: Implements Python in .NET. RustPython: Implements Python in Rust. Coconut: A functional programming language that compiles to Python. Any valid Python code is valid Coconut code. Brython: Python 3 adapted to HTML5 and the DOM. Use Python inside script tags. Converts Python into JavaScript.

@ericsnowcrntly Thanks and congrats! What is the rationale not to call the interpreters "sub-interpreters" to clearly indicate they aren't separate processes? Could you recommend a good write-up of substance of the PEP? In your link it seems to be quite buried in history and discussion.

Version 2.0 of pytest-testmon is out! Most changes compared to version 1.4.5 are internal. They will allow better maintenance and the ability to add new features.

We have put together a short tip which I think every user of GitHub Actions and Python should know about. testmon.org/blog/better-gi…

There is a little known tool for GH Actions which should be used more. A blog post: testmon.org/blog/better_gi…

Oh wow, Python is at the stage of life where they're starting to focus their social circle and invest in skincare.

Josh Long @starbuxman

4 years ago

Happy 32nd birthday Python!

1 2 25 15K 0

neptyne.com is another cool product which tries to bring Python to the spreadsheet. There have been attempts in the past (Resolver One), but it’s very difficult to dethrone Excel.

I think y'all would be more open to rebasing if the dominant tooling (GitHub) were less hostile to it. At Meta, nobody complains about rebasing because our tools (Phabricator, Interactive Smartlog) are designed make trunk-based dev a pleasant experience sapling-scm.com/docs/addons/isl

Half of testmon is at FOSDEM Brussels this weekend. Anybody wants to chat there? :) #fosdem #python #automatedtesting #testing #pytest

🤯 Flaky tests can be a frustrating problem for any software development team. 🦾 To fight flaky tests, you need solid processes and learned lessons over time. Remember; you wrote them, you can fix them! Take a look at our article's tips. ⬇️ blog.mergify.com/flaky-tests-ho…

pytest-testmon with xdist support is out! testmon.org/v14-with-xdist…

Great podcast episode: about.sourcegraph.com/podcast/jean-y… ~"Dev tools which help you understand and evolve already written software are as important or more important than tools helping you to write new software." Definitely also the case with test suites. @sourcegraph @AkitaSoftware

pytest-testmon v1.3.6 is out. Ironing out a few kinks and compatibility with Python 3.11!

Version 1.3.4 of pytest-testmon is out: --testmon-noselect now sorts the tests! All the tests are executed but the affected go first. Unaffected tests only follow afterwards. Quickest tests are still prioritized within each subgroup. (+ edge case fixes and refactoring)

Version 1.3.1 of pytest-testmon is out!: Not only modified time but also checksum of files is now correctly used to detect changes. Checksum of methods was working correctly but caused unnecessary AST parsing which took a long time on large projects. (especially relevant for CI)

pytest-testmon version 1.3.0 is out now! Please try and let us know what you think: * much smaller .testmondata saving space and improving performance * doctest and doctest modules support * support for pytest 7 * xdist is not supported and the related warnings were fixed

@anthonypjshaw In Python 3.11 there will be almost no overhead for Python to Python calls thought. Mark and I worked on inlining the ceval loops so there is no consumption of the C stack. And the references to the arguments are stolen from the caller so there is close to 0 overhead 🚀

Django 4.0 released ift.tt/31zz5VB