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
I cannot figure out how to report this minor bug of a minor upgrade
issue (https://github.com/twisted/twisted didn't have an issues
section) that I noticed since last week:
$ pip list --outdated DEPRECATION: Python 3.4 support has been deprecated. pip 19.1 will be the last one supporting it. Please upgrade your Python as Python 3.4 won't be maintained after March 2019 (cf PEP 429).
Package Version Latest Type
------- ------- ------ -----
Twisted 19.2.1 19.7.0 sdist
$ pip install --upgrade Twisted
DEPRECATION: Python 3.4 support has been deprecated. pip 19.1 will be the last one supporting it. Please upgrade your Python as Python 3.4 won't be maintained after March 2019 (cf PEP 429).
Using cached https://files.pythonhosted.org/packages/61/31/3855dcacd1d3b2e60c0b4ccc8e727…
ERROR: Complete output from command python setup.py egg_info:
ERROR: Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/tmp/pip-install-2h_su73e/Twisted/setup.py", line 20, in <module>
File "<string>", line 257, in getSetupArgs
File "<string>", line 208, in _checkPythonVersion
ImportError: Twisted on Python 3 requires Python 3.5 or later.
ERROR: Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-2h_su73e/Twisted/
That v19.7.0 shouldn't even be offered for my outdated setups. :(
Thank you for reading and hopefully answering soon. :)
What's a good way to use a simple dictionary as a cache in twisted
Basically, I have this callback chain where I ultimately make a rest call
(in non-blocking way using treq) to fetch some data. But before I make the
call, I am using a dictionary to see if the value is available or not.
But, I have noticed that the event loop gets pretty busy(sometimes, things
get stuck and twisted server stops) as soon as I add this logic.. Which is
if key in cache:
# else call back to treq to fetch value
cache[key] = value
This dict can grow to around 50k.. What's a good way to solve this issue?
I'm looking for someone to be my body double for Twisted releases,
taking over on alternate releases or when I'm busy (which seems to be
all the time???? when did I become an adult, why did I do that).
Ideally this person is up for this role on an ongoing basis, with a time
commitment of four or so hours every alternating release (so every 2
months or so, hopefully). Plus, you'll need to be known by the team,
since you then become the trust anchor for all the binaries we publish.
The release process is a bit buggy here and there, and I haven't been
the best at writing down workarounds/fixes for things, so also ideally
the first release would be a collaborative one. Plus, we need to update
it for the advent of built wheels, as well.
If you have the time to spare, care about release management, and don't
mind yelling at computers for a while, drop me a (private) email
expressing interest and I'll get in touch.
-----BEGIN PGP SIGNED MESSAGE-----
I'm pleased to announce txtorcon 19.1.0, containing the following
* TorControlProtocol.on_disconnect is deprecated in favour of
* introduce non_anonymous_mode= kwarg in txtorcon.launch()
enabling Tor options making Onion Services non-anonymous for the
server (but they use a single hop instead of three to the
Introduction Point so they're slightly faster).
* add an API to listen to individual circuit and stream events
(without subclassing anything). Can be used as decorators too.
See e.g. TorState.on_circuit_new()
* fixes to the CI setup to properly test Twisted versions
You can download the release from PyPI or GitHub (or of
course "pip install txtorcon"):
Releases are also available from the hidden service:
Or via a "version 3" service:
You can verify the sha256sum of both by running the following 4 lines
in a shell wherever you have the files downloaded:
cat <<EOF | sha256sum --check
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----