[Shiny new list address! This is exciting!]
So... IReactorTCP.connectTCP claims that 'host' should be a 'bytes':
PosixReactorBase.connectTCP doesn't tell us what type it should be, but,
via tcp.Connector, ends up using it to construct an IPv4Address, which
reckons it should be a 'str':
Connector also uses it to construct a tcp.Client, where it gets used as
part of tcp.Client.addr, which is again supposed to be a 'str'.
I think in practice, either works, but it looks like most things
*expect* it to be a 'str', with grudging support for 'bytes'. So my
impression is the definition of the interface is wrong. Any
(While we're at it, IReactorTCP also claims that 'timeout' and
'bindAddress' are required parameters, even though all the
implementations make them optional.)
hi there, folks:
I'd really like to release 0.7.0 but I would like it to be at least a
little bit tested before I do so. Could those of you with CVS trees check
everything out and see if it performs as advertised? Deeper bugs than
that will have to wait for the next release, but I'd at least like to know
if it works for someone other than me.
______ __ __ _____ _ _
| ____ | \_/ |_____] |_____|
|_____| |_____ | | | |
@ t w i s t e d m a t r i x . c o m
Sorry for all the operations-related noise folks, just wanted to send one final message to be sure that the list alias works for anyone who hasn't updated their addressbooks yet. After this I think we'll be back to normal operations, at least for the mailing list.
This mailing list will be shut down in a few minutes, and should be back online in about 12 hours at the latest. When it comes back, the preferred address will be twisted(a)python.org <mailto:email@example.com>.
Our venerable hosting provider, tummy.com <http://tummy.com/>, will be terminating their business operations on September 30, 2021.
>>> datetime.date(2021, 9, 30) - datetime.date.today()
In addition to being a bit personally sad - Tummy has been an avid supporter of the Twisted community since the very beginning - this means we have just about 60 days to fully migrate our website, mailing list, and DNS's hosting from Dornkirk, the machine where it's been running continuously since 2013, to ... something else.
There are 2 problems here:
We need a sponsor to help us find a new hosting or cloud provider where things can be hosted. We do pay tummy currently, and we can probably ask the SFC to pay a different hosting provider a similar price for equivalent services, but ideally we'd find someone willing to donate something so as not to put a drain on those resources.
I will need significant help with the operational aspects of the migration. I typically do a bunch of behind-the-scenes system administration for twistedmatrix.com <http://twistedmatrix.com/> to keep the whole thing clunking along, but after my brain has been fried by a year and a half's worth of pandemic stress, I simply don't have the time, energy, or mental capacity to do this. I know I've asked for help before and rarely received any, but if I have to do this entirely by myself, the most likely outcome is that I'll migrate DNS to some free cloud thing so at least my email address doesn't break (I migrated SMTP, and thereby everything associated with personal email addresses to Mailgun some years ago, so Tummy is not in that loop for that), and the website (and this mailing list) will simply stop working sometime between now and October. So if you'd like to keep www.twistedmatrix.com <http://www.twistedmatrix.com/>, speed.twistedmatrix.com <http://speed.twistedmatrix.com/>, our IRC bot (which is offline anyway right now due to Freenode shutting down), https://twistedmatrix.com/highscores/ <https://twistedmatrix.com/highscores/>, this mailing list, or our dogfooding instance for Twisted Names DNS, please volunteer so we can start to coordinate.
If you've been wanting to just use Github Issues and don't care about preserving any of the data in Trac, congratulations, you're about to win that argument by default ;-).
In the worst case scenario, I will download a backup image before things get turned off in case someone wants to deal with this
This is a quick message to let you know that the current mailing list service
will migrate from the Twisted own hosted services
to the mailing list service provided by the Python organization.
The migration is scheduled to start on the 5th of August, 2021
17:00 UTC time (10:00am PDT / 18:00 BST)
The following email address will no longer be available:
The new address will be:
The new archive will be hosted at the following link that will be
available after the migration:
All existing subscribers will be migrated.
If you only interact with the mailing list using your email
you only need to update your existing filters
and update your email contact address for the list.
The migration is expected to take about 3 hours.
After the migration, Glyph plans to implement an email redirection,
so even if you send emails to the old address we should still receive them.
Subject to availability :)
We also plan to redirect (via HTTP 308) the old mailing list pages and
archives to the new pages.
This will also happen after the migration.
Have a nice day... and talk to you soon on the new mailing list.
PS: while we do the migration you can still get in touch using
IRC on Libera #twisted channel
Matrix/Gitter at https://gitter.im/twisted/twisted
> Great news. I'd be happy to move the mailing lists over to let someone else maintain their infrastructure. Particularly if we could get off of Mailman 2, which has been no fun to maintain.
> Many personal email addresses of core team members (including, um, this one) are forwarded by our mail hosting provider, Mailgun, and so moving the MX records directly is a non-starter, but we could easily point lists.twistedmatrix.com <http://lists.twistedmatrix.com/> at python.org <http://python.org/>, or we could just use @python.org addresses and be quite happy. twisted at python.org <mailto:twisted at python.org> would be very cool. We could also maintain a forwarding alias for compatibility for a little while, but I'd kinda rather deprecate posting to twisted-python at twistedmatrix.com <mailto:twisted-python at twistedmatrix.com> for a couple of other reasons anyway.
A forwarding alias seems the best choice. twisted(a)python.org is indeed cool
> Do we have a way to get our pipermail archive URLs (which are linked in tickets, in source code, etc) to redirect to the fancy new hyperkitty interface, or should those just be static HTML? (I'm kinda fine with either, honestly, although the former would be nice if we can manage it easily.)
I think the redirects would be fairly easy as the URL structure is the same
> I am happy to coordinate off-list about a secure way to exchange these data files (or anyone with administrator access to Dornkirk can just do it directly). Please send the announcement of the new address here first so we know when to cut over posting, and so that folks aren't surprised to see a new list-id.
I can do magic wormhole
> (At this point I think I'm happy to just nuke twisted-web as part of this migration; we can keep the archive up as static HTML for posterity, but it's mostly unused at this point, and the distinction doesn't make sense.)
I actually think it's better to move twisted-web first and see what it
looks, then mess about there with redirects, then do the main mailing
list. I think the redirects would be fairly easy as the URL structure
is the same