Mailman 3 April 2022 - Twisted

(no subject)
by Adi Roiban 11 May '22

11 May '22

Hi, With the latest release of cryptography 37.0 the Twisted tests suite fails. I have create a ticket here https://twistedmatrix.com/trac/ticket/10337 As part of another PR [1] and in order to have the CI checks pass, the cryptography dependency was defined as cryptography >= 2.6, < 37.0 So for now, Twisted is limited to cryptography up to 36.0.2 My hope is that we can find the volunteers to look into this issue and have Twisted working with latest cryptography and latest OpenSSL It might be the case that Twisted is OK and we only need to update the assertions in the test code. I guess that the main reason for the failure is OpenSSL 3.0.0. For Twisted CI we used the upstream cryptography wheels, and they are distributed with an embedded OpenSSL If you have time, try to run your Twisted TLS based apps together with cryptography 37.0 upstream wheels and see if you observe any failures. If you have custom wheels that link to OpenSSL 1.1.1, it would also help to test cryptography 37.0 and OpenSSL 1.1.1 Feel free to add any feedback here over email or over IRC / Gittter or over Trac. Thanks [1] https://github.com/twisted/twisted/pull/1724 -- Adi Roiban

2 2

pydoctor: Recommended markup language
by c.buhtz＠posteo.jp 20 Apr '22

20 Apr '22

Hello togehter, I am not sure this is the right place for pydoctor related discussions. The topic are pydoctor's different supported markup languages [1]. The question seems simple and maybe you can put it to the FAQ [2] of pydoctor. Which of the markup languages would you recommend for a new pydoctor user? I assume that you use "epydoc" for Twisted, right? But I also assume that you use it because of historical reasons because pydoctor was born out of epydoc, right? I know a bit Google and numpy style from sphinx. I also know Doxygen "style". But I haven't used one of them long enough to make a decision. I would say a docu style should... - be readable in source code - fit to Python concepts - support markup (bold text, code blocks, ...) - less complex for newbies, in the meaning of not to many options/possibilities So what is your opinion in that? Kind Christian [1] -- <https://github.com/twisted/pydoctor#markup> [2] -- <https://pydoctor.readthedocs.io/en/latest/faq.html>

2 1

Help needed for GitHub.com , Trac tickets to GitHub issues migration
by Adi Roiban 20 Apr '22

20 Apr '22

Hi, We plan to migrate all existing Trac tickets [0] to the existing twisted/twisted repo from GitHub [1] We need an insider/supporter/sponsor from GitHub.com to temporarily enable access to GitHub.com Enterprise Cloud Importer . Why is that: One of the issues is that by using the public GitHub REST API, all migrated issues and comments will be visible inside GitHub as being creating the a single user (the user triggering the REST API) We are aware that the Python Software Foundation has recently completed the migration for CPython to GitHub Issues [2], using a private GitHub.com Enterprise Cloud Importer (ECI) This is a tool that is not publicly available to open source projects. Thomas wrote to GitHub support last year asking for "best practices" for GitHub migration and the answer was to use the REST API. My colleague Dan, wrote again to GitHub support giving the CPythong and LLVM migration as an example and mentioning Enterprise Cloud Importer, and the answer was that we should use the REST API as we are not an enterprise. ---- What to do if we don't have access to GitHub.com Enterprise Cloud Importer (ECI) ? I plan to wait one week to see if somehow we can manage to get access to the private import tool. We will just use the public REST API and all the issues and comments will be created/authored by a single "trac-migration" robot account. Thanks [0] https://twistedmatrix.com/trac/report/1 [1] https://github.com/twisted/twisted/ [2] https://github.com/python/cpython [3] https://github.com/psf/gh-migration/issues/13 PS.0: In the case in which you are wondering why we want to migrate from Trac. The First reason is that we don't have any volunteers having time to manage, update, maintain, upgrade ...etc, our existing Trac website. PS.1: If you want to help with the GitHub migration or help with the existing Trac website, let us know via email or join our IRC or Gitter chat. -- Adi Roiban

2 1

Migrating the existing Trac Wiki pages
by Adi Roiban 20 Apr '22

20 Apr '22

Hi, As part of the plan to stop using Trac for Twisted project management, we need to find a way to migrate / archive the existing wiki pages from here https://twistedmatrix.com/trac/wiki I see 2 options ------------- Option 1 - Migrate to GitHub own Wiki pages I have already done a test migration. You can see an example here Page https://github.com/twisted/twisted/wiki/ReviewProcess History https://github.com/twisted/twisted/wiki/ReviewProcess/_history Pros: * The wiki page edit history is preserved * Wiki has a separate repo * The wiki can be now edited with Git * GitHub Wiki supports RST or Markdown format Cons: * GitHub Wiki has no support for Trac Wiki format.. so we need some sort of conversion * Continues to depend more on GitHub --------------- Option 2 - Migrate the latest Wiki snapshot to a Python Sphinx based website You can see an example here https://judgegregg.github.io/sphinxwiki/content/pages/ReviewProcess Code is at https://github.com/twisted/twisted.github.io/pull/10 Pros: * Uses Sphinx and we are already familiar with that Cons: * The revision history is not visible from the web page (still can be available via the source repo) --------- I am for using option 1, but only as an "archive". I am also able to allocate all the required resources in order to make this happen :) Any wiki page of value, should be migrated to our official documentation at https://docs.twistedmatrix.com For example, there is this PR to migrate the security wiki page to our official documentation https://github.com/twisted/twisted/pull/1712 And if that PR is reviewed, I plan to migrate the ReviewProcess wiki page next. I am against option 2. We already have https://docs.twistedmatrix.com using Sphinx, hence I am not happy with having 2 separate Sphinx sites for Twisted. ---------- What do **you** think? You can send your feedback over email or over IRC or Gitter. Thanks -- Adi Roiban

2 2

INCOMPATIBLE CHANGE: Towards the adoption of coroutines
by Jean-Paul Calderone 14 Apr '22

14 Apr '22

Hello, I've just written up an idea for an approach to getting many parts of Twisted and Twisted-based applications onto coroutines (ie `async def`). Details are given on https://twistedmatrix.com/trac/ticket/10327 The change involves the potential for some incompatibilities - though as I described on the ticket, I think these are likely to be very rare in practice and worth imposing for the resulting payoff. This thread represents the start of the process for making incompatible changes to Twisted as described at https://twistedmatrix.com/documents/current/core/development/policy/compati… There is not yet a branch but there is a patch in a comment on the issue (the change is extremely small) for anyone to try out or comment on. I will follow up when there is a version closer to what would be merged into trunk. Meanwhile, feedback is welcome. Jean-Paul

6 6

Twisted 22.4.0 Final Release Announcement
by Adi Roiban 11 Apr '22

11 Apr '22

On behalf of the Twisted contributors I announce the final release of Twisted 22.4.0 This is mainly a security bugfix release for the minor HTTP related issue https://github.com/twisted/twisted/security/advisories/GHSA-c2jg-hw38-jrqq There is also support in Conch SSH for RSA keys signed with SHA2, as well as support for Ed25519 via PyNaCl for older systems that don't have and up to date cryptography library. And t.python.failure.Failure makes it easier to integrate Twisted code with the Raven Sentry client. -------------- This release followed a new security release process. If you have time, send your feedback regarding the security process at PR https://github.com/twisted/twisted/pull/1712 -------------------- The release and NEWS file is available for review at https://github.com/twisted/twisted/blob/stable/NEWS.rst Release documentation is available at https://docs.twistedmatrix.com/en/stable/ Wheels for the release are available on PyPI https://pypi.org/project/Twisted/22.4.0/ python -m pip install Twisted==22.4.0 Many thanks to everyone who had a part in Twisted development, the supporters of the Twisted Software Foundation, the developers, and all the people testing and building great things with Twisted! Help is needed to push the development of Twisted, especially reviewer PRs submitted by other developers. If you have time, hang out over IRC and gitter and see how you can help. Slava Ukraini! -- Adi Roiban

1 0

Twisted 22.4.0 Pre-Release Announcement
by Adi Roiban 06 Apr '22

06 Apr '22

On behalf of the Twisted contributors I announce the release candidate of Twisted 22.4.0 This is mainly a security bugfix release for the minor HTTP related issue https://github.com/twisted/twisted/security/advisories/GHSA-c2jg-hw38-jrqq There is also support in Conch SSH for RSA keys signed with SHA2, as well as support for Ed25519 via PyNaCl for older systems that don't have and up to date cryptography library. And t.python.failure.Failure makes it easier to integrate Twisted code with the Raven Sentry client. -------------- This release follows a new security release process in which the security advisory is published for RC1 version and not for the final release. If you have time, send your feedback regarding the security process at PR https://github.com/twisted/twisted/pull/1712 ----------- We currently have the test twisted.words.test.test_domish.DomishExpatStreamTests.test_namespaceWithWhitespace failing on trunk and on the release branch. It looks like this is due to "environment" The tests were green at first and after a re-run without any code changes this tests fails. See Attempt #1 and #2 from here https://github.com/twisted/twisted/actions/runs/2082082584 If you can help with fixing this test that would be great :) -------------------- The release and NEWS file is available for review at https://github.com/twisted/twisted/pull/1714/files Release candidate documentation is available at https://twisted--1714.org.readthedocs.build/en/1714/ Wheels for the release candidate are available on PyPI https://pypi.org/project/Twisted/22.4.0rc1/ python -m pip install Twisted==22.4.0rc1 Please test it and report any issues. If nothing comes up in one week, 22.4.0 will be released based on the latest release candidate. Many thanks to everyone who had a part in Twisted development, the supporters of the Twisted Software Foundation, the developers, and all the people testing and building great things with Twisted! -- Adi Roiban

2 1