Mailman 3 - Twisted - python.org

Packaging update
by Ofek Lev Oct. 9, 2022

Oct. 9, 2022

Hello Twisted devs! I wanted to give everyone a heads-up that there's an open pull request <https://github.com/twisted/twisted/pull/11656> to update the way the project is packaged. The main changes are: 1. metadata is now defined in a `pyproject.toml` file as specified by PEP 621 <https://peps.python.org/pep-0621/>/PEP 631 <https://peps.python.org/pep-0631/> 2. the `.whl` and `.tar.gz` artifacts are built by default in an isolated manner as specified by PEP 517 <https://… [View More]

1 0

Property testing in Twisted
by Jean-Paul Calderone Sept. 21, 2022

Sept. 21, 2022

Hello all, I'd like to start a discussion (but hopefully a brief one!) about using property testing techniques in Twisted. For those who aren't familiar with them, a property test is a kind of unit test written such that it can assert a certain invariant holds over a range of inputs. This is in contrast with more conventional unit tests in which a single test asserts a certain invariant holds for a single input and typically many such tests are written to cover the necessary range of inputs. … [View More] Twisted mostly uses conventional unit tests though it does include a few property tests written in an ad hoc way. If you search for loops in the test suite you quickly come across them. For example, twisted.test.test_amp.ParsingTests includes several. test_booleanValues does not use a loop but it is a property test. test_ParsingRoundTrip does use a loop and is also a property test. In these cases, the developer knew they wanted to exercise the implementation against more than one input but they were limited in how exhaustive they could be by the tools available. There is a popular library for property testing in Python called Hypothesis. I've pushed some changes to *a branch* <https://github.com/twisted/twisted/compare/26c3c04e55d0b25532709e1e1dc5d143…> to demonstrate usage (note: *not* currently for review) of some of the basic APIs and the tests that result: - The given decorator marks a test as a property test. The consequence of this is usually that the test method runs more than once. The "strategies" passed to given determine how it is called. - Strategies like tuples, lists, integers specify what values are passed to the decorated function. Each will correspond to a parameter the test method accepts. A simple strategy like integers will result in int values being passed. Many strategies can be composed. A strategy like tuples will result in tuple values being passed, with the elements of the value determined by the strategies passed to the tuples strategy. - Helper functions like assume support dealing with corner cases related to invalid inputs which are tricky to avoid in a strategy. If it is hard to constructively define exactly the right set of inputs, you can define a strategy that finds "too many" and filter out the bad ones afterwards. The test is then written to make an assertion that is correct with respect to the specific values the test is called with. For complex code, it can take a while to get used to writing tests in this style but for simpler code it's often only a matter of using the strategy-provided values instead of some hard-coded values. Once using given, the test method actually runs many times, each time with different values "drawn" from the given strategies. When the test fails, Hypothesis tries to "shrink" the values - it simplifies them as far as it can while still causing the test to fail. When it has simplified them as much as it can without making the test pass, those simpler values are reported. This means that Hypothesis can find complex inputs that break the code under test but when *simple* values will do, those are the ones a developer gets to work with. There are many other benefits to this style of testing, such as reduced effort required to write comprehensive tests and improved code re-use in the test suite. I won't describe them further here but you can learn more at the Hypothesis website - https://hypothesis.works/. I think property testing is a valuable tool in the testing toolbox and Twisted should consider adopting Hypothesis to employ it for some tests. Thoughts? Jean-Paul [View Less]

3 6

On the sneaky caching behavior of twisted.python.filepath.FilePath
by Jean-Paul Calderone Sept. 21, 2022

Sept. 21, 2022

Hello, I was reviewing some third-party code today and noticed many bugs in it that arise from FilePath's caching behavior. I found https://github.com/twisted/twisted/issues/3161 (only after I wrote up https://github.com/twisted/twisted/issues/11676 though). The cache behavior is long-standing but I think it needs to go. It represents a dangerous and subtle trap for anyone who tries to use FilePath, which I would *like *to be everyone - but that would be an easier sell without traps like this one. Jean-Paul

3 3

Ldaptor - adding authentication to an external ldap directory
by DEV Sept. 13, 2022

Sept. 13, 2022

Hi! I'm trying to add authentication to an existing ldap service, that is unable to handle authentication itself. I also need to inject an additional search filter for lookups after a successful bind. Using the LoggingProxy example as a start, I was able to proxy the connection. How can I override the authentication part? I also found "svcbindproxy" but it works entirely different, using Proxy instead of ProxyBase class. I was unable to use "handleBeforeForwardRequest" there. I'm working a … [View More]

1 0

Twisted 22.8.0 Final Release Announcement
by Adi Roiban Sept. 7, 2022

Sept. 7, 2022

Hi all, Twisted 22.8.0 was released It is available for download from PyPi https://pypi.org/project/Twisted/22.8.0/ Release notes on GitHub https://github.com/twisted/twisted/releases/tag/twisted-22.8.0 ----------- I plan to do the next release over the end of the year holiday. If required we can have another release at any other time. The release process is pretty much automated and anyone can pick up the role of the release manager and drive a new release. The process is documented … [View More]

2 2

Twisted 22.8.0 Pre-Release Announcement
by Adi Roiban Sept. 7, 2022

Sept. 7, 2022

On behalf of the Twisted contributors, I announce the release candidate of Twisted 22.8.0 This is the first release after we migrated from Trac Tickets to GitHub Issues. In this release, the API docs were updated to a newer pydoctor version and the RTD theme is enabled. The old Trac twistedmatrix.com website is now offline. Redirections were implemented on a best effort basis :) If you find any broken link you can report this via GitHub Issues https://github.com/twisted/twisted/issues/new/… [View More]

3 5

pydoctor: "source" links not working (html-viewsource-base)
by c.buhtz＠posteo.jp July 23, 2022

July 23, 2022

Hello, I run pydoctor for some months and it was working. But something changed on my site I think. But I am not sure about it. My repository is here https://codeberg.org/buhtz/buhtzology I assume this URL is the value I have to use for the "html-viewsource-base" argument when calling pydoctor. Am I right? For example the "landing page" is related to that __init__.py file in my repo https://codeberg.org/buhtz/buhtzology/src/branch/main/src/buhtzology/__init… But when I click on the "… [View More]

2 2

Migration of Trac Ticket to GitHub Issues
by Adi Roiban June 28, 2022

June 28, 2022

Hi, FYI, the process of migrating Trac Tickets to GitHub Issue has started. We expect to have the migration ready by tomorrow 28 of June 2022 at 13:00 UTC. Please don't create any PR or issues to the https://github.com/twisted/twisted repo. I will send an update over here when the migration is done. Thanks! -- Adi Roiban

2 2

Trac Wiki migration / archive
by Adi Roiban June 28, 2022

June 28, 2022

Hi, As part of the general effort to decommission our Trac website I have archived the wiki at the following repo https://github.com/twisted/trac-wiki-archive The plan is to mark the repo as "Archive" Any changes should be done in the twisted/twisted documentation or in the twisted.github.io website repo. The name of the repo can be renamed. Feel free to suggest better names or a better README file. ------- After we decommission the Trac instance we will implement a redirection for /trac/… [View More]

2 2

Preparing the migration from Trac tickets to GitHub Issues
by Adi Roiban June 20, 2022

June 20, 2022

Hi, In preparation for the Trac ticket migration to GitHub Issues a staging/testing repository was created You can find the list of migrated issues here https://github.com/twisted/twisted-trac-migration/issues Send any feedback at the following ticket and my colleague Dan will try to address all the comments: https://github.com/twisted/twisted-trac-migration/issues/1 A bit of hard work is left to find the mapping between Trac users and GitHub users Handling at: https://github.com/… [View More]

4 10